First, android has had a culture of "free, ad-sponsored" applications, whereas iOS apps have always been about paying for the stuff (not surprising if you understand a bit of apple and google businesses).
As a consequence (or because of the fact) iOS users are more likely to spend money than android users. This means that if you're doing a mobile shopping app, you expect iOS users to be much more likely to buy your products.
So it's not just about market share, it's about market share times purchasing power.
That's for the market, now on the other end, about developers, saying "android" has a large market share, is not relevant. You want to speak about android market share per OS/api version. I did start developing on android, but the minute you click on the "create new project" you need to ask yourself how many android users you want to ignore (in double digit percentages). If you want to have the maximum market share you need to develop with 3 years old apis, and you'll probably frustrate users that have brand new devices. In my experience, that's where project owner decide to postpone the decision to start the android version of their product.
Then, if you make it up to this point, you need to decide what screen size you want to support and how many different version of your UI you will need to design. Note that you still haven't started a single line of code yet !
Finally, you start coding and realize the toolchain sucks pretty much. Xcode is obviously much better than anything on the market and i won't even start talking about the simulator (which is important as soon as you need to test on different screen sizes).
All in all, most of the time android feels like developing for a second grade market, having second grade devices, with second grade tools, on 3 years old apis. No wonder developers don't rush for it..
First, android has had a culture of "free, ad-sponsored" applications, whereas iOS apps have always been about paying for the stuff (not surprising if you understand a bit of apple and google businesses).
As a consequence (or because of the fact) iOS users are more likely to spend money than android users. This means that if you're doing a mobile shopping app, you expect iOS users to be much more likely to buy your products. So it's not just about market share, it's about market share times purchasing power.
That's for the market, now on the other end, about developers, saying "android" has a large market share, is not relevant. You want to speak about android market share per OS/api version. I did start developing on android, but the minute you click on the "create new project" you need to ask yourself how many android users you want to ignore (in double digit percentages). If you want to have the maximum market share you need to develop with 3 years old apis, and you'll probably frustrate users that have brand new devices. In my experience, that's where project owner decide to postpone the decision to start the android version of their product.
Then, if you make it up to this point, you need to decide what screen size you want to support and how many different version of your UI you will need to design. Note that you still haven't started a single line of code yet !
Finally, you start coding and realize the toolchain sucks pretty much. Xcode is obviously much better than anything on the market and i won't even start talking about the simulator (which is important as soon as you need to test on different screen sizes).
All in all, most of the time android feels like developing for a second grade market, having second grade devices, with second grade tools, on 3 years old apis. No wonder developers don't rush for it..