
Neil McAllister
delves into the Android and iPhone SDKs to help sort out which will be the best bet for developers now that
technical details of the
first Android smartphone have been announced. Whereas the iPhone requires an Intel-based Mac running OS X 10.5.4 or later, ADC membership, and familiarity with proprietary Mac OS X dev tools, the standard IDE for Android is Eclipse. And because most tasks can be performed with command-line tools, you can expect third parties to develop Android SDK plug-ins for other IDEs. 'By just about any measure, Google's Android is more open and developer-friendly than the iPhone,' McAllister writes. This openness is
essential to Android's prospects. 'Based on raw market share alone, the iPhone seems likely to remain the smartphone developer's platform of choice â" especially when ISVs can translate that market share into application sales,' McAllister writes. 'In this race, Apple is taking a page from Microsoft's book, while Google looks suspiciously like Linux.'
Member since:
2005-07-06
***
This is just an article about someone who doens't like obj-c and the NDA. Nothing about the SDKs and nothing that will help sort out which one is the best.
Indeed, but how exactly can you have a shootout when both Apple and Google throw NDAs everywhere?
Language politics aside (as quite frankly they all look the same to me), the APIs behind the iPhone are FAR superior to those behind Android. You can chalk it up to opinion if you want, but I am an order of magnitude more productive on the iPhone than I am on Android, and I'm not the only one.
I'd tell you more, but then they'd have to kill me.