Android more stable than iPhone

Matthew Nuzum —  — 2 Comments

Today I saw two items come across my radar that were unrelated but connected when it comes to the concept of mobile device fragmentation as it relates to software developers’ API stability.

Grounding Software, an Apple advocate, recently got a vague phone call from Apple saying their three-times-accepted app for the iPad was being withdrawn from the App Store because it did not conform to new, unpublished standards that were unable to be described.

The developers of the app had invested real money and real time following Apple’s guidelines to create an app for the iPad. People liked it. They were making money. But Apple changed their policy on what kinds of apps were going to be allowed and removed the app. And to make matters worse, the only way they were finally able to get an “answer” to why they were rejected was after they emailed Steve Jobs himself.

People have argued for a while that Android is fragmented. They say it is inevitable when you have 60 different devices with different hardware and different capabilities that you’ll get fragmentation. I have to admit to thinking this very thing when I heard the goals for the platform.

A blog post today from Dan Morrill, Compatibility Manager for Google’s Android platform publicly addresses this concern. Each device that is given access to the Android Market is tested for compatibility through a suite of 20,000 tests. And software is forward-compatible, meaning apps designed for Android 1.5 are compatible with newer software releases.

Android’s compatibility guidelines are the same as Apples. In order to get the benefits of compatibility you have to write your app to adhere to the published SDK. No using secret or vendor specific API calls in your app. (and Android, with it’s open source platform, makes it a bit easier to discover)

The difference is that Android’s guidelines aren’t secretly changing.

If it helped, please share!Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+

Matthew Nuzum

Posts Twitter Facebook

Web guy, big thinker, loves to talk and write. Front end web, mobile and UX developer for John Deere ISG. My projects: @dsmwebgeeks @tekrs @squaretap ✝
  • Hugh

    “meaning apps designed for Android 1.5 are compatible with newer software releases.”

    hmmm, i wish I could believe that, if it were true then why is the Marketplace littered with comments “doesn’t work on xxxxx / stopped unexpectedly on launch” – either the developers have failed to follow SDK guidelines, or devices are in some way outside specification. Either way, consumers get a bum steer, and an impression that ‘not everything works on everything’ which is pretty much the definition of fragmentation?

    Part of the fault is in the extremely relaxed attitude of Marketplace approvals…. they may have copped some well deserved stick recently for their approval policies, but I don’t think Apple have ever approved a phishing app ( Are there any standard tests applied to software before it is approved for distribution? Right now the Marketplace is a soup, and it needs to be cleaned up.

  • Matt

    It’s a reasonable doubt, and is partially addressed in the android developer blog I linked to in the blog post. There are exceptions (implementation bugs) and he says “most” vendors try to fix this quickly. I know HTC has done stellar work with the Hero (sprint).

    However, also look at the platform vendor’s stated policy and their demonstrated policies. Apple has shown time and again through their actions and their changes to developer agreements that their guidelines are constantly shifting.

    How would you like to invest $100k of your own money developing a product with a vendor who changes their mind like the above example on a whim?

    That’s not the kind of stability good relationships are built on.