"Also, why are people still developing exclusively for iPhone? Last quarter there were four times as many Android phones sold as iPhones."

Have you ever been in a 2-3 person startup? You have to make a choice and do something exclusively. iPhone is the right choice if you want to get to market and start talking to users sooner. It's also the right choice if you want to raise money and get tech press in the Valley (it turns out virtually no investors or bloggers have anything but an iPhone).

You're not going to develop for both platforms simultaneously because that is a recipe for headaches and higher costs - especially if you're still figuring out your product-market fit.

Let's not even talk about Android device fragmentation, which I can only imagine is a serious problem. The difference lies in that while Androids may dwarf iOS installs in terms of units sold, the iOS platform dwarfs the Android in terms of the size of the market of people willing to buy apps.

>> Also, why are people still developing exclusively for iPhone? Last quarter there were four times as many Android phones sold as iPhones.

I can only speak for myself, but developing for Android is a nightmare compared to developing software for iOS. Different behaviour amongst different Android devices makes it really hard to provide a consistent user experience.

I'm not disagreeing with the sentiment, but is "consistent user experience" necessarily something that should be a goal?

There's more to it, but when I hear that I'm reminded of web site "designers" that only use photoshop and focus/obsess over pixel-perfect layouts and font-sizings, to get everything to match exactly what their original photoshop 'design' looks like on their monitor, ignoring the variety of browsers/devices that may also visit the site.

We do want to develop for Android, just didn't have enough time and resources to do them both at the same time. Sorry for that, we'll bring it to Android soon!