Now that iPhone OS 4.0 introduces multitasking, how do you actually quit an app (instead of allowing it to go "multitasking")?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to quit an app in OS 4.0?
- Thread starter nano8blazex
- Start date
- Sort by reaction score
"If you want to kill an app
you dont have to. We architected something so the user doesnt have to be the custodian of applications. Well give the apps in the foreground as needed. The user doesnt have to worry about that at all. The user just uses things.
In multitasking, if you see a task manager, they blew it. Users shouldnt have to ever, ever, ever think about that stuff."
In multitasking, if you see a task manager, they blew it. Users shouldnt have to ever, ever, ever think about that stuff."
So if a user wanted to use all of his/her apps in succession (lets say 100 apps)... they'll just all remain open in the multitasking bar thing? Won't that... sortof slow the device down?
I understand it to be the same as it currently is. Multitasking is only activated when you double tap the home button to launch the multitask "bar". Only then would you have a background app .
I read his response and kind of wondered the same thing. I think its one of those things that we will have to wait and see. I'm sure once the developers get their beta versions we will hear more about it.
I bet when that bar comes up with all your apps you can probably hold your finger on it until the X comes up then tap the X to close it.
I hope not, that would take too long. Imagine having to do that for every app that you open and want to close?
Hmmm... I was under the impression that multitasking would be activated as soon as you launched the app... probably im wrong.
When I read what they were doing with multitasking I don't think it is true mutlitasking at all. There are going to be a few apple apis that your updated app is going to be able to use. When you close your app the app can feed information thru the api to you. Its just a fancier version of push.
With the inclusion of better save states you'll be harder pressed to know whether multitasking is actually working or not.
Hense you don't need to close any app as there is no app to close. Because there is no real 3rd party multitasking in the first place.
Thats what I got out of it anyways...
With the inclusion of better save states you'll be harder pressed to know whether multitasking is actually working or not.
Hense you don't need to close any app as there is no app to close. Because there is no real 3rd party multitasking in the first place.
Thats what I got out of it anyways...
That just about seems right, actually. We'll have to watch the keynote video when it's released. The multi-tasking app bar could just be like your most recently run apps
I think Jobs is an idiot for comparing a task manager to a graphical system for choosing/closing an app.
It'll probably work like Safari. You know how it keeps 8 pages open? But if you run out of RAM it 'loses' the oldest pages and they have to re-load when you go back to them?
I bet the multitasking will keep the last few apps you used running, but if it needs to it'll just 'freeze' the app that's 5 or 6 down the line. The number will depend on how much of the resources your apps are using.
So some peole will get 8 apps running at once but some will only get 3 if they're really big things. Bottom line is, you don't have to worry about it.
That's my guess.
I bet the multitasking will keep the last few apps you used running, but if it needs to it'll just 'freeze' the app that's 5 or 6 down the line. The number will depend on how much of the resources your apps are using.
So some peole will get 8 apps running at once but some will only get 3 if they're really big things. Bottom line is, you don't have to worry about it.
That's my guess.
This is correct. The entire application does not continue running, only the relavent APIs that allow whatever the app's core background functionality is to continue. So Pandora (as an app) is put into a save state, but its audio API is allowed to keep running so you still get the audio.
It's quite a good idea, actually.
There's nothing to quit..
The apps state is remembered automatically, it's not actually running in the background.
Obviously if your pandora radio is playing in the background, to quit the app you'd just go back to pandora and hit pause/stop.
If something is tracking your location, you'd just go back to the app and tell it to stop tracking.
It's not "true multitasking" because it seems like some things are still going to be impossible - you can't receive a notification from an IM client while it's running in the background for example, you'd still have to rely on push notifications for that.
The apps state is remembered automatically, it's not actually running in the background.
Obviously if your pandora radio is playing in the background, to quit the app you'd just go back to pandora and hit pause/stop.
If something is tracking your location, you'd just go back to the app and tell it to stop tracking.
It's not "true multitasking" because it seems like some things are still going to be impossible - you can't receive a notification from an IM client while it's running in the background for example, you'd still have to rely on push notifications for that.
Yes, but I think it's fair to just label the 7 APIs as "multitasking."
My entire post is talking about those APIs and the fact that it's the APIs that will either keep or 'freeze' services depending on how busy they are.
But I think it's just a lot easier to say 'multitasking' to refer to all that.
Ugh, I hope not. What a swing and a miss.
Some apps are best if they don't save state.
Take the settings app, for example. Suppose the last time you went into settings it was to check your usage. You exit the app right from the usage screen. Somewhere down the line, you want to turn off WiFi. When you launch settings, you don't want to be back at the usage screen, making your have to navigate all the way back to the top of the hierarchy.
On the other hand, what if you are in the middle of setting up an email account and have to cross reference all your account information with Safari (ingoing/outgoing server info, port settings, account info)? In that case, you don't want to start at the beginning screen each time and lose your place.
Take the USAToday app. When you launch the app, it always starts at the front page so you can see all the updated news for the day. You don't want to have to navigate backwards each time from when you last quit the app within an article from three days ago.
But then again, what if you want to look up something from a story in Safari? You want to get back to your place in the article when you return.
I don't think Apple gets it.
A simple way to get around that would be to single tap an app you want to run from its saved state, then double tap or push and hold an app you want to run from its home page.
Whether or not they've thought about that, I don't know, but they'll probably address it in an update. I think most people would rather have a slightly annoying implementation than one that saps battery life.
I agree with you, but I was referring to the bar in particular. It has nothing to do with which apps are currently running in the background.
You bring up the task switcher, long press the icon of the app you wish to close, it starts shaking, you hit the minus icon, it closes.
It's not a myth. It's just often used in hyperbole. Controlled multitasking (either by the system or the user) may have limited impact on battery life. Out of control multitasking can kill battery life.
Did you just make that up?