cbiltcliffe writes:
Crittercism has performed testing on mobile platforms, and found that while Apple's release of iOS 7 is the most stable iOS release to date, reducing the crash rate to 1.7%, this still pales compared to Android versions 4.0+, which have a crash rate of only 0.7%.
Not surprisingly, gaming apps with complex graphics and sound crashed more often (4.4%) than other apps, with eCommerce apps getting the best rating of only 0.6%. Some pre-digested coverage from gantdaily.com can save having to dig through pages of research data slides, if you're not looking for the gritty details.
Is this consistent with your experience, or does your particular usage tell a different story?
(Score: 3, Informative) by BasilBrush on Monday March 31 2014, @10:30AM
A common cause of an app crashing on startup on iOS would be the main thread timeout of 20 seconds. If an app author does any lengthy initialisation on the main thread, particularly if it relies on a network connection, then that would cause a crash.
Does Android have a similar timeout, and if so what length is it?
(Score: 3, Informative) by mojo chan on Monday March 31 2014, @12:59PM
On Android if your main thread doesn't respond for 10 seconds it is killed off and an error displayed.
const int one = 65536; (Silvermoon, Texture.cs)
(Score: 1) by BasilBrush on Monday March 31 2014, @01:45PM
So this is ANR, is that right? If so then it displays a dialog, rather than crashing straight away. With the options to "Wait" or "OK" (to close).
And of you select OK to close from the ANR, does that count as a crash, or as a clean close of the app?
I'm just thinking that maybe this difference in behaviour could explain the measured crash on opening rates. iOS behaviour is always a crash when an app goes unresponsive for 20 secs.