Can anyone clarify exactly why a backgrounded application would become suspended? Obviously, it's supposed to occur when the OS becomes low on memory, but does the App's icon actually leave the -- for lack of a better name -- double-tap-dock area?
I've never seen that happen, and nearly every app in my full Springboard is also in the double-tap app switcher.
They want to make the idea of "running" irrelevant: to the user, it's active or inactive. No need to manage a list of running programs if what is actually running is made invisible and unimportant. Makes it simpler.
Sounds like they may be headed that way with Lion, too - what's seen so far doesn't have the little lights under dock icons that indicate whether the application is actually "open" or not.
Cute..., and a good start to a UIKit visualization.
By the way, the methods you see in the diagram are to be implemented by a UIApplicationDelegate. Your UIApplicationDelegate class is usually laid out by default in new XCode projects. There are the methods currently documented by Apple.
11 comments
[ 2.5 ms ] story [ 36.3 ms ] threadI've never seen that happen, and nearly every app in my full Springboard is also in the double-tap app switcher.
By the way, the methods you see in the diagram are to be implemented by a UIApplicationDelegate. Your UIApplicationDelegate class is usually laid out by default in new XCode projects. There are the methods currently documented by Apple.
Monitoring Application State Changes
– application:didFinishLaunchingWithOptions:
– applicationDidBecomeActive:
– applicationWillResignActive:
– applicationDidEnterBackground:
– applicationWillEnterForeground:
– applicationWillTerminate:
– applicationDidFinishLaunching:
Docs here (http://developer.apple.com/library/ios/#documentation/UIKit/...)
http://developer.android.com/reference/android/app/Activity....