Linked by David Adams on Thu 25th Sep 2008 18:03 UTC, submitted by snydeq
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.'
Thread beginning with comment 331596
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-11-16
"Could you give some examples of what you see as clear strengths of the iPhone SDK as opposed to the GPhone one"
Well,
- Cocoa Touch
- Interface Builder (that's a big deal)
- Instruments
- Core Animation
- Quartz
- Core Audio
- Core Foundation
- Core Data
If you developed for Mac OS X, you should get the idea....
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-03
I've spent some time looking at both API's and doing a small project in each just to get a feel for the lay of the land. Yet I don't see the clear superiority of the iPhone SDK that you mention. The one thing I do see on the Google side is a lack of documentation, not that it's terrible, just that the iPhone SDK docs are a lot better.
I don't have enough experience in either to say one way or another but to me both appear to have strengths and weaknesses. Of course it may have something to do with the fact that I'm much more experienced as a Java developer than a Obj-C one. Could you give some examples of what you see as clear strengths of the iPhone SDK as opposed to the GPhone one?