3 ms·

The iPhone doesn't have to deal with this because it doesn't support multitaskeng, hence an app becoming "unresponsive" isn't such a problem. To be honest, I wo

The iPhone doesn't have to deal with this because it doesn't support multitaskeng, hence an app becoming "unresponsive" isn't such a problem. To be honest, I would be rather angry if the OS shut down my browser process just because some image-heavy website slowed it down for a few seconds. One of the reasons I like Android is that I got more control over stuff and I know I'm not alone. Some people don't like the Apple "we know what's right for you" mentality. My point is, people are different, there's no "average phone user". This is not a question of technical skill as there's really nothing technical in "wait" and "force quit". Some people like to be in charge, some people don't, personally I do.

allenbrunson 17y ago
actually, the iPhone OS does support multitasking, and it's used quite heavily. you can start a call, then the phone app continues to run in the background while you start something else. the iPod app runs in the background playing music while you're running other apps. and so on. even if iPhone didn't allow multiple apps to run at once, it would still have to deal with crashes. it handles them by unceremoniously quitting the dead app and sending you back to the home screen. claiming that an average user should be able to know what to do with a dialog box that gives the options 'wait' or 'force quit' ... man, that sort of thinking by competitors is exactly why apple keeps winning all the time, isn't it.
- DrJokepu 17y ago
  If an app crashes on Android, of course there are no questions asked. We're talking about unresponsive apps, not crashes. And as far as I know, the iPhone only allows "system" apps to be background apps. You can't listen to Spotify while browsing. About the other issue: I think Apple "keeps winning all the time" because of the combination of the consistent experience they deliver bundled with a competitive line of auxiliary services (such as iTunes or the App Store) and very strong branding. There's nothing wrong with that, but I don't think that artificially limiting the choices available to the user is a huge contributing factor.
  - potatolicious 17y ago
    Actually, iPhone will kill -9 unresponsive apps also. Try writing an app that sticks itself into a tight loop, then start giving the phone inputs (home button, touches, etc)... the OS will soon realize your app is out to lunch and kill it. This is the correct way to do it.

allenbrunson 17y ago

actually, the iPhone OS does support multitasking, and it's used quite heavily. you can start a call, then the phone app continues to run in the background while you start something else. the iPod app runs in the background playing music while you're running other apps. and so on. even if iPhone didn't allow multiple apps to run at once, it would still have to deal with crashes. it handles them by unceremoniously quitting the dead app and sending you back to the home screen. claiming that an average user should be able to know what to do with a dialog box that gives the options 'wait' or 'force quit' ... man, that sort of thinking by competitors is exactly why apple keeps winning all the time, isn't it.

DrJokepu 17y ago
If an app crashes on Android, of course there are no questions asked. We're talking about unresponsive apps, not crashes. And as far as I know, the iPhone only allows "system" apps to be background apps. You can't listen to Spotify while browsing. About the other issue: I think Apple "keeps winning all the time" because of the combination of the consistent experience they deliver bundled with a competitive line of auxiliary services (such as iTunes or the App Store) and very strong branding. There's nothing wrong with that, but I don't think that artificially limiting the choices available to the user is a huge contributing factor.
- potatolicious 17y ago
  Actually, iPhone will kill -9 unresponsive apps also. Try writing an app that sticks itself into a tight loop, then start giving the phone inputs (home button, touches, etc)... the OS will soon realize your app is out to lunch and kill it. This is the correct way to do it.