The iPhone developers, the good ones (e.g. have been Featured in App Store) that I am fortunate to know personally, they're not even touching Android.
Reasons: Unfamiliarity and leaving the comfort zone.
iOS development is comfortable. When you do Android dev, you give up a lot of comfort for raw, unfettered access. It is a rule of thumb when you develop for Android that when you release you will get ANR (Application Not Responding) simply because of the fact that you can't test on more than a few actual devices. I get crash reports from the market site that I can't fathom how they even can happen (stuff like libraries that are statically linked not being found)
And, as an primarily Android dev now, can you imagine giving up Core Data (for all its faults, the latest iOS 5 [redacted] makes it better), Interface Builder (ADT 11 is getting closer but still not close) and even stuff like Objective-C Categories?
Reasons: Unfamiliarity and leaving the comfort zone.
iOS development is comfortable. When you do Android dev, you give up a lot of comfort for raw, unfettered access. It is a rule of thumb when you develop for Android that when you release you will get ANR (Application Not Responding) simply because of the fact that you can't test on more than a few actual devices. I get crash reports from the market site that I can't fathom how they even can happen (stuff like libraries that are statically linked not being found)
And, as an primarily Android dev now, can you imagine giving up Core Data (for all its faults, the latest iOS 5 [redacted] makes it better), Interface Builder (ADT 11 is getting closer but still not close) and even stuff like Objective-C Categories?