Hi, I'm Adam. Email me about: CTOs, Mobile/iOS, Project Management, and Development

Jon Blow: “almost no certification process for iOS”. LOLz.

Jon just published an interesting letter about the current state of cert processes for game consoles / platforms.

There are some real problems with certification today. Unfortunately, Jon’s post doesn’t really touch upon them, and seems to go instead after the IMHO untrue and unhelpful claim that iOS is better for having “almost no certification”. No, really:

“The certification processes of all these platform holders were based on the idea that all these steps they test are absolutely necessary for software to run robustly, and that software robustness is super-important for the health of their platform and its perception by customers.

But, look at iOS. There is almost no certification process for iOS, so by the Microsoft/Sony/Nintendo theory, the apps should be crashing all the time, everyone should think of iOS as sucky, etc. But in fact this is not what is happening. There is no public outcry for more testing and robustness of iOS software.”

Personally, I’d say that iOS has a certification process of comparable length to console cert, given the comparitive size/complexity/many-years of development in the apps, and for a couple of years it was considerably nastier than TRC’s because *it had no documentation*.

(my first hand experience: I created and maintained a large site that documented the app rejections by Apple, and interviewed the developers on what got rejected, why, what happened after the rejection, etc.)

Even with the nightmare of never knowing what the rules were, there was a positive net effect: many apps were forced to resubmit until they hit a minimum barrier of quality. Again – I know this for a fact, I had many conversations and interviews with developers about this, often getting to read their conversations with Apple. Even today, there are many apps being rejected every week for failing on basic quality / functionality / crashing / etc.

For me, that rather undermines his argument. Which is a pity, because there ARE major problems with cert – on all platforms, Apple included – and we should be focussing on them. But it’s not the idea of cert that’s at fault, it’s either the choice of items (e.g. Sony, where some of the rules come from PlayStation 1 era and are barely relevant today) or it’s the poor implementation of the process (e.g. Apple until 2011), or it’s the big chunks of stuff that SHOULD be part of cert but isn’t (…everyone…).

4 thoughts on “Jon Blow: “almost no certification process for iOS”. LOLz.”

Comments are closed.