The document discusses the application lifecycle on mobile devices and how developers should handle interruptions, user expectations, and different lifecycle events. It covers topics like tombstoning, where the application is dead but some state is saved, and how restoring state is important for a good user experience. Code samples demonstrate saving state on deactivation and restoring it on activation. Managing resources properly during lifecycle events is required for apps to be published.

1. ApplicationLifecycleJason LeeEthos Technologies

2. AgendaInterruptions & User Expectations

3. Application Lifecycle

4. Tombstoning

5. Lifecycle Events

6. Resource Management

7. Play Time

8. Q & AInterruptionsInterruption comes from

9. A user action (i.e. press the start button)

10. An external event (an incoming phone call)

11. An internal action (i.e. taking a photo, choosing a contact)

12. Interruption characteristics

13. Interruptions are not predictable

14. Interruptions tend to happen frequently User ExpectationsPhone and Applications

15. Phone is resource-constrained device, therefore we need to consume resources carefully

16. Phone is different from Desktop OS, which can hold multiple windows running processes simultaneously

17. However…

18. A user expects the application to be able to remain in the state where it was left

19. Microsoft development guideline requires application to provide such illusions that it keeps running continuously until it is get killedApplication LifecycleRunningDormantTombstonedDeactivatedDeactivatedDead, and no longer lives in memory.But with somethingcarved on a TombstonePhone resources detachedThreads & Timers suspendedBut app instance remains in memoryActivatede.Preserved == trueFast App ResumeActivatede.Preserved == falseYou Will See Resuming Process Bar