| I'm not sure I agree with the blog post then. The Android docs certainly do not detail this kind of information either. In fact, I've found the docs for Android to be of the "broad but shallow" variety. That is they cover everything (thanks to Javadoc) but they don't necessarily provide usage guides on the various APIs. My opinion on Android development vs. iPhone is: a. GC is convenient b. The developer docs on Android are not nearly as good as Apple's c. XCode (while not perfect) is less buggy than Eclipse for basic development activities. Eclipse just gets in the way most of the time and can't keep up with my typing speed which is really frustrating. d. I like ObjC's dynamism a lot more than Java. This is a personal preference. e. Its nice to be able to peer into the OS source on Android as the definitive answer for API questions but I suppose if the docs were better you wouldn't need to do that. f. The Android APIs are full of pattern inconsistencies with their implementation on the whole compared to UIKit which make them more difficult to learn. g. UI Layout on Android is abysmal compared to using Interface Builder. i. Again - this is more of a Java thing, but Android lacks the ability to do conditional compilation. You have to go through build system/scripting gymnastics to get what you would get from a simple #IF statement in C. |