Lets face it native objective-c can be a pain. When you first start developing it seems really cool but after awhile it becomes a pain to have to keep coding the same type of basic views pretty much every screen needs.
We usually develop xcode templates and use those, but then every app seems to have the same look and feel. So some of us have started integrating javascript libs in our native apps , we always used some javascripts , but now some apps may be at least 30 or more percent client side javascript. Tried various toolkits.. Qcconnect, kind of cool but has too many hooks into xcode, so you need to be careful considering how many betas apple puts out. If your a developer that doesn't download every new beta you'll probably fine. PhoneGap is great, unfortunately the rejection rate is too high, not to consider. So some of us , especially like us whose first apps took forever to develop and are awaiting approval soon, have started looking at incorporating iwebkit and dashcode. iwebkit is really interesting because it is based on jquery. dashcode , you can be sure will be compatable with every release. I don't know personally anyone using iui in a native application, but I'm sure there may be some developers out there. The point is, use these toolkits which you talk about frequently here to build the simple stuff, and spend more time on buiding the functionality that makes your application unique in objective-c. One caveat, I don't know of anyone whose gotten an iwebkit app approved yet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
