iOS apps crash more than android

C

CHANG3D

Supreme [H]ardness
Joined
Jul 23, 2010
Messages
4,975
app-crashes1-1024x761.png


So what does this say about stability?

http://www.forbes.com/sites/tomiogeron/2012/02/02/does-ios-crash-more-than-android-a-data-dive/

If you ask me for my opinion on why this happens, I will tell you from my personal experience, Android developers are MUCH more talented than Apple developers. However, Android developers do severely lack creativity.

P.S. Is that also iOS fragmentation I see?!? Ha, I kid! I kid!

crashes-ios1.png
 
I have an android tablet and an android phone and an iPad 2. Android apps crash way, way more than the iOS apps do. Just IME.
 
I have browser crashes on my iPad at least once a day. My sgs2 has had no issues.
 
CHANG3D said:
If you ask me for my opinion on why this happens, I will tell you from my personal experience, Android developers are MUCH more talented than Apple developers. However, Android developers do severely lack creativity.
Click to expand...

lol. You have no freaking clue .... besides the fact that the study is comparing Apples and Oranges.
 
Lebowski said:
I have browser crashes on my iPad at least once a day. My sgs2 has had no issues.
Click to expand...
I have browser crashes on my TF101 every day. That's why I use Opera Mobile. Never had that crash. The iPad browser crashes because there's not enough memory. Honeycomb browser crashes because of bugs.
 
Interesting. And Windows is supposed to be the complex and buggy OS. IE on my Windows tablets crash once in a blue moon, and when it does it self recovers splendidly.
 
/rant/ said:
The iPad browser crashes because there's not enough memory. Honeycomb browser crashes because of bugs.
Click to expand...
I would consider a crash caused by low memory to be a bug. Low-memory alone should never cause an application to totally crash, especially in an environment like iOS.

If that's really the case, then it sounds like Safari's memory management and error handling need to be given a once-over. In a low-memory situation, it should be unloading resources from tabs that haven't been used in a while (save them to disk so they don't have to be re-downloaded from the internet). They might also consider temporarily halting a page-load if the browser runs out of RAM (resume after data has been paged to disk), rather than letting it crash-out.
 
Unknown-One said:
. In a low-memory situation, it should be unloading resources from tabs that haven't been used in a while (save them to disk so they don't have to be re-downloaded from the internet). They might also consider temporarily halting a page-load if the browser runs out of RAM (resume after data has been paged to disk), rather than letting it crash-out.
Click to expand...

It actually does that and most of the third party dev apps do so (and are encouraged) as well.

In my experience most of the app crashes are related to poor third party developer implementation of memory management on iOS.
 
I hope you all actually read the article linked. The report points out that this was found over a very limited time frame (less than a month, IIRC) and iOS 5.0.1 has been out that long and hasn't been updated much. OTHT, ICS is barely running on anything and GB has been out for a while and has been tweaked. All the results could easily change over time and over a longer sample period. Try to draw any kind of conclusions from this is a waste of time.
 
From my experience IOS does crash more often, but they do handle it better. Most people wouldn't even know an app crashed because ios hides it in screen freezing while it restarts. Whereas androids tend to be upfront about it with a notification.
 
CHANG3D said:
If you ask me for my opinion on why this happens, I will tell you from my personal experience, Android developers are MUCH more talented than Apple developers. However, Android developers do severely lack creativity.
Click to expand...

Android developers don't have to deal with memory management as much due to garbage collection, at the most they just need to make sure that the collections don't build up to the point that it causes issues with user experience (stutters, pauses, etc) Because of the garbage collection it's much easier for a programmer to be sloppier and not pay for it with crashes.

We are talking about a difference of around 1-2% anyways. And it should be noted that Crittercism was funded by Google Ventures along with other questions that are not completely answered.
 
From my experience iOS is way more stable than android. I bought the epic 4g when it first came out and it was a nice phone until I started messing with roms and it became exponentially unstable.
Got tired of it and bought a Nexus S4g and kept it completely stock. Stock browser kept timing out. Then I started getting force closes often. Did a full reset and couple months later kept getting weird random force closes.

I switch to the iPhone 4S in november and haven't had a single crash. Surprisingly I like it a lot more then the androids Ive had before. I use to be a hater, but now I am a believer.
 
Based off of the last 3 iPhones(3G, AT&T iP4, and Verizon iP4) and the last 3 Androids I had (HTC Incredible, Droid 1, and Droid 2) I'll question that study and stick with me iPhones
 
/rant/ said:
The iPad browser crashes because there's not enough memory. Honeycomb browser crashes because of bugs.
Click to expand...

No, they both crash because of bugs. Both are using WebKit, bugs in webkit will affect both of them. Combine that with both of them using bleeding edge hardware acceleration that even desktop browsers don't complicates things further.
 
You must log in or register to reply here.
Back
Top