I checked out Java ME years back and it appeared too narrow to allow development of apps that impress. Symbiant has a hellish reputation, while overnight iPhone has ratcheted up user expectations a couple of notches or three. You want to be able to develop to meet those expectations p.e.r.i.o.d. However... if you embark on iPhone app dev you need to check it out in detail and still have to brace yourself wondering if the iPhone SDK limitations won't stop you from doing exactly that. And on top of that, you still need to make it through the velvet rope. After checking out the Android SDK, it became quickly apparent that it offers what I'm interested in - no-excuses support for the development of map based apps. Thumbs up to MapView. With lacking support for that line of work on the iPhone SDK (as far as I've seen), I wasn't too interested in it. Having to rely on shaky convolutions of JavaScript and Cocoa ain't cutting it for me. Joa
On Jul 1, 2:09 pm, hitsu_g <[EMAIL PROTECTED]> wrote: > Thought it was relevant to a lot of what's been discussed here > recently:http://www.thestandard.com/news/2008/07/01/how-does-developer-decide-... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
