Android: The Platform for Prototypes
robsandhu.tumblr.com
robsandhu.tumblr.com
Aside from slowing down iterations a lot, it means you want to REALLY test well before you push an iteration to them. Just heard about a top grossing iOS game that pushed out a new revision with a bug that affects 1% of their users ... causing THOUSANDS of tech support emails. And it's still another week or so before the fix will be published.
To say this causes a chilling effect on experimentation on iOS is an understatement.
(and could have used it at least once before! :-\ )
In which case I'd also like a link to the "expedited review" page. :)
iOS submissions reviewed in the last 5 business days:
New Apps: 96%
App Updates: 99%Another important metric is how quickly users start using the update. When you measure using this metric Android is anything but instant.
Web apps "check for updates and install" every time you use them. Users are forced to update and depending on the site within a matter of minutes nearly everybody will be using the new version.
Android apps don't go through a review process, but it still takes a few minutes for the servers to get the update. It will take an hour or two for every phone to get notified of the update (it's not pushed) and give the user a notification. It will then be even longer for the user to push the button and receive your beautiful new code. There are a few users with "automatic updating" but it's not enabled by default. The majority of your user base will take a while to finish migrating over. I would love if anybody here had real numbers on this, our app only just started reporting version numbers so we haven't been able to collect the data yet.
There are exceptions. The Facebook app renders webpages so most updates happen instantly, but when they update one of the native sections there's still a long wait before everyone has it.