[brennenHN]

I love the point about iteration here, but I think this post is a little bit disingenuous.

The problem with developing for Android as a startup is that baseline reliability is incredibly resource intensive.

If you want your app to work on the most popular few devices, you will still have to spend a considerable amount of time and money testing the different configurations and fixing bugs that have nothing to do with your core functionality.

If you want broad support to address most of the market, you're going to be spending a huge amount of development time tweaking little details of your code. When you fix a bug for the Galaxy S4, it'll start crashing on the HTC One X, and the Galaxy Note will never look quite right.

Iteration is valuable, but iOS lets you build one product and iterate on it, to build for Android, you have to start by building 15.

[jordanthoms]

Any specifics on that? Unless you are doing something really weird, there shouldn't be compatibility issues between recent devices like that. Generally the issues are with older devices that have very little ram etc, which are becoming less and less common.

[general_failure]

There we go with this fragmentation bullshit. Say something concrete.

BTW I had the same problem - what works on iPad 3 didn't work on iPhone 4 and I fixes something that didn't work on touch.