On Apr 12, 8:12 pm, ntwrkd <[email protected]> wrote:
> A Web Developer Perspective on iPhone Software
> Developmenthttp://www.thebitsource.com/2009/04/12/a-web-developer-perspective-on...
I couldn't agree more , I find myself in the same position. A long
time ago I used to program in smalltalk, some of the concepts in
objective-c remind me of that. I am a java developer, been for some
time. When I first started with Native Iphone applications I think I
made the same mistake many developers are making.
Started with the assumption that native apps were better than web
applications... But thats not really true.. saying you know how to do
native apps is merely like a status symbol but it has no merit.
The second mistake I made was to start all over from scratch. I big
mistake.
Some projects such as games can only be done correctly natively , so
you must start your development with xcode, but for enterprise style
web applications I fellow the following approach.
1)Determine my needs of course
2) Design the backend functionality
3) Code a test case webapplication with dashcode, that is if possible
I create a web only version of my application. This works for me
because most native apps I design are hybrids and make use of the
uiwebview functionality. Designing the app as a web application first
allows me to quickly see what my app will look like to the user, it
also lets me test my backend functionality. But one other benefit it
gives me is piece of mind. An app can take anywhere from a couple
hours to weeks to write, and if apple rejects it and you can't change
it to make it conform to the store policy your dead. At least if you
have a web version of the app you don't lose your whole time
investment. Also the web version of the app gives you a limited
functionality version the use can try for free before purchasing the
native app. win..win..
4) Now I take a notebook, and create a list with the following points.
1) What functionality would be better handled natively.
2) what functionality is better handled via the web eg. with a
uiwebview component.
3) What functionality will be in both native and web version but will
differ.
With this list, I start writting the native app. Its mostly a
translation effort, find the best sdk functions that duplicate your
web functionality.
And finally add additional native only functionality to enhance the
app, gps, google maps etc.
This approach works quite well......
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
