3 ms·
I think there's some confusion over how Apple is implementing multitasking. Apps continue to run in the background, and when you re-open them you'll be back to
by cmelbye 16y ago
I think there's some confusion over how Apple is implementing multitasking. Apps continue to run in the background, and when you re-open them you'll be back to where you were. The operating system will begin to terminate the apps when it is low on resources. In addition, there are certain services that work a little bit differently, like VoIP, music in the background, tasks that need extra time to run, etc. As far as I'm aware, this is very similar to the way that Android implements it.
The wallpaper feature is there if you want to use it, but Apple has included some darker pattern wallpapers if you prefer a low key background behind the icons. Of course, one could always whip up a plain black background to use too.
- masklinn 16y ago> Apps continue to run in the background No they don't, that's the point. The first multitasking you talk about is basically app hibernation, it gets a CPU priority of 0 (no CPU at all but stays in memory), the rest are OS services the application subscribes to, and then the OS manages the rest. Apart from Task Completion (maybe) the application never runs. With some services (location, background streaming/music, local notifications) a callback may run (on a timer or all the time), but not the whole application, far from it. > As far as I'm aware, this is very similar to the way that Android implements it. Nope, the UI part is handled the same way (by freezing it on switch) but in android there are no OS services, instead a backgrounding application works as a server daemon (faceless) and the UI is a client communicating with the daemon. Faceless daemons don't get frozen, because you can't "switch off" from them.