Slashdot Mirror
iOS Vs. Android: Which Has the Crashiest Apps?
First time accepted submitter creativeHavoc writes "Forbes author Tomio Geron takes a look at data accrued by mobile app monitoring startup Crittercism. After looking at normalized data of crashes over the various mobile operating system versions he compares crash rates of apps on the two platforms. He also breaks it down further to look how the top apps compare across the competing mobile operating systems. The results may not be what you expect."
iOS crashes more than Android (for those who don't feel like trawling through the (not brilliantly formatted) article.
You can learn a lot about a person if you just take the time to inject them with sodium pentathol
I was expecting android to outdo iOS in the crash department due to all the variables in the android world hat iOS just doesnt suffer from. Namely, android has a wider range of handset support.
The $600 device's main purpose is NOT to make calls. It's an internet communications device that just happens to make phone calls. The people who insist that basic phones are just fine need to figure out this slight, but important, distinction. Buy an internet device if you want internet, but don't compare it to a phone.
I'll probably opt for a BASIC voice-and-text flip-phone of some kind
What is the command in BASIC for calling someone?
The closest I can think of is GOSUB, but I'm afraid that's not going to pull the trick.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
I would be very interest to see the impact of jailbreaking in this analysis. Do apps crash more often on jailbroken devices? How does it compare between Android and iOS?
One of the main argument for closed down system, putting aside the money factor which no one gives as an official reason, is stability. I do not believe stability is considerably affected by jailbreaking or by the subsequent modification one could do to the OS, but it would be nice to have statistics and some analysis on this.
It's more than just bad apps. I got an iPad a couple weeks ago and safari has crashed several times. I never have more than 5 tabs open. I have also had Skype crash as well, but I don't know how well that code is written.
Sorry, just not true. Before the iPhone, an unlocked Treo 650 cost about USD 650 (without contract). Some fashionable dumb or feature phones - like the Matrix Nokia chromed slider - retailed up to USD 1000 at the time - with contract and all.
In the short term, I'll probably opt for a BASIC voice-and-text flip-phone of some kind, because I can't afford (nor stomach!) spending $600 on a PHONE whose MAIN purpose is to MAKE CALLS when I can get a $70 model that will take care of that primary function just fine for now.
Its a common perspective, but first of all most people (at least in the US) buy their phone subsidized with a contract renewal, so the price for even a top-tier phone is $200-$300. Second, for me personally after using smartphones for a few years, I view it as the most significant personal (non-work) computing device I use daily. I definitely use it more than my home PC and tablet combined, and can therefore justify spending top dollar on a quality "phone". I won't make assumptions about you, but I know many people who found, when they get a smartphone, that its main purpose is NOT to make calls.
You have nobody to thank for this but a: the carriers and b: apple.
It is they, who in collusion, raised the price of buying a phone to astronomical levels. Remember when the highest price for an unlocked phone was usually $200? What phone broke that trend? Iphone.
Well, either that, or you didn't notice expensive phones before the iPhone, since unlocked Treos were $600 in 2006. But sure, you dislike Apple so it's probably Apple's fault.
What? There have been >$1000 unlocked phones as long as I can remember. Hell, I remember the Nokia 8 and 9 series phones cost over a thousand bucks way back in 1997 or so...
I was bored this morning, so for those interested, since the article makes it hard to extract this information:
All iOS versions total 84.36% of crashes; all Android versions total 15.49% of crashes. The worst offenders for iOS are version 5.0.1 at 28.64% and 4.2.10 at 12.64% (with seven other version listed at above 1% of crashes). The worst offenders for Android are versions 2.3.3 at 3.86% and 2.3.4 at 3.65%, with 4 other versions listed at above 1%.
Loose things are easy to lose. You're getting your hair cut. They're going there to see their aunt.
What is the command in BASIC for calling someone?
The closest I can think of is GOSUB, but I'm afraid that's not going to pull the trick.
I think if you want to be pulling tricks, then you need to get people to be calling you. So you'll need to advertise your number with something like a "PRINT". And then repeat that lots of times to try and get past all the people flagging you on CL
I am Slashdot. Are you Slashdot as well?
but I know many people who found, when they get a smartphone, that its main purpose is NOT to make calls.
That is so true. And let's not forget that, at least in Android's case, there's a built-in SIP stack so you can make cheap data calls. Of course, you could also run Skype on Android and iOS. There are a couple of VoIP providers (I understand that VOIPO is one) that let you use your SIP credential on your phone. In any event, even if your main thing is making voice calls, a smartphone can help save you money there.
The higher the technology, the sharper that two-edged sword.
but the most popular phone leading up to iphone was the RAZR (2004). initial price in the states was $600 bucks.
http://gizmodo.com/270353/the-razr-taught-us-that-the-iphone-is-priced-juuust-right
It was 2004 when the RAZR launched in the US as a high-end design clamshell. It was $600, with a $100 dollar rebate from Cingular. yes, soon after launch the price dropped precipitously much like smart phones now. today you can get an android or ios phone (NEW) for just about every price point from free to 800 bucks.
oh, and don't forget the venerable StarTAC. 1996 - ONE THOUSAND DOLLARS (http://en.wikipedia.org/wiki/Motorola_StarTAC).. a primary selling point of which was support for OMG.. wait for it.. SMS. ...a free iphone 3GS is as capable as a laptop of the StarTAC era. Apple didn't set the bar, Motorola did - TWICE. Together the StarTAC and RAZR sold over 100M units.
so poett, you either forgot or are too young to have ever known ;)
I don't think this has as much to do with Android and iOS as it does with the state of software quality in general. The current state of software quality is abysmal, since the shift to scripting languages and web apps as the primary platform about ten years, the science and art of writing robust and reliable software for OO, event driven, asynchronous platforms like iOS or Android has become an almost lost skill. Unfortunately failure modes for these platforms are more dramatic than for web apps, in that you'll likely get a crash rather than 'error on page' message. The situation has been further exacerbated by management's insistence an always hiring the lowest quality developers they can find, outsourcing, H1 B's etc. If you use low quality and inexperienced devs, you'll likely get an unstable and and unreliable application on these types of platforms. This should be a wake up call to the industry in general in that we need to focus and engineering, quality and reliability, and not just minimizing cost.
I don't think the prices are unreasonable -- it's an extremely compact device with a lot of FLASH memory, a screen resolution better than many laptops, and better battery life than most laptops. The Apple devices sold by SaskTel are marginally cheaper in many cases, more expensive in others, depending on which model you get.
But for me, the main purpose is to develop for the phone, not to use it as a phone, so when you add in the cost of a Mac and software to program for iOS devices, the Android platform wins by a HUGE margin.
I do not fail; I succeed at finding out what does not work.
This graphic is worse than useless. Here is a good debunking of it from a stats focused blog I first saw it on.
http://junkcharts.typepad.com/junk_charts/2012/02/a-data-mess-outduels-the-pie-chart-disaster-for-our-attention.html
Bureaucracy expands to meet the needs of the expanding bureaucracy.-Oscar Wilde
Bad apps crash -- sure. But *worse* apps may appear to keep working while storing up later trouble for the user.
Whenever I see a list of software fault types with "crash bug" at the apex, I cringe. When I led a software team, I had to de-program developers who were trained that crashing is the worst possible thing an app can do. It isn't. There are many worse ones, such as leading a user to trust false data, exposing sensitive information, and losing or corrupting a user's work. The worse thing about a crash in the absence of data loss or long recovery time is that it undermines user confidence. It's often possible for a well-architected app to crash (due to programming faults of course) with no serious implications for the user.
Crashing per se isn't a problem. It's a *symptom*. This is important! I've caught developers "fixing crash bugs" without addressing the real problems: failure to program defensively around unexpected conditions like bad input or inability to secure resources like memory or file references. I've seen super-general exception handlers buried way down on the stack which catch every possible exception and quietly attempt to restore the semblance of operation, even though they can't possibly know whether the application is in a consistent state, or whether it is holding orphaned resources. Programmers do this because they've been inculcated with the false notion that crashes per se are terrible things. This leads to hiding the symptoms errors rather than fixing the errors themselves. Hiding the cause of a crash increases the probability of faulty information, loss of data, and shipping a release with serious defects.
So don't treat crashing as a problem, but as an alert signal. A crash in itself is benign, an honest recognition of failure if you will.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
No, informative.
There is no "I disagree" mod for a reason. Flamebait, Troll, and Overrated are not substitutes.
I wouldn't call that iOS' "fault". Mobile devices have very limited resources. This isn't like a desktop machine where you've got several gigabytes of memory to play with. If an application is badly behaved and it uses too much memory, that has an effect on the rest of the system. There's only so much memory to go around. Also, if using lots of memory becomes normalised, there's pressure to add more memory to newer models, which will result in lower battery life.
I'm an app developer, and if I ever see that one of my projects is killed for not responding fast enough, I know that there's something very, very wrong somewhere. Usually it's a sign that a junior developer decided to do something processor or network intensive synchronously on the main thread, which is a big mistake. You do what is necessary to get an interface up, and you push everything expensive into the background and update the UI when it finishes. There's no excuse for an application not responding quickly enough, it's easy to do.
If you really think Skype is not at fault, how do you explain the fact that it crashes all the time on other platforms as well?
Bogtha Bogtha Bogtha