Androidology - Part 2 of 3 - Application Lifecycle
Why Stack Overflow recommends it
Stack Overflow users link it when explaining why Android apps and activities can be killed, restarted or recreated (for example on orientation change) and why state must be saved.
Recommended by 3 people across 3 different months, 2010 to 2013.
What it is
An 8-minute segment from the Androidology series by the Android Developers channel, in which Mike explains how Android manages application and process lifecycles as a user moves between apps. It is the second of three parts giving an early overview of the platform.
What people said
Strong rec Varun · 2013-08 · Stack Overflow · on “Is my class safe on Android if it's not an Activity?”
You might want to take a look at this excellent video. [this video] THis might probably help you understand application lifecycle in a much better way.
Recommends Andreas · 2010-01 · Stack Overflow · on “Android Run application from last Activity”
so there are a few things to consider when developing Apps in Android. And one of the big things is the Application Lifecyle, if you haven't yet then I would suggest this video [this video] . What happens is that an application can be killed and reset at any point in time and you need to save the state of your application so that you can restore it at any time. If you open your App from the Launcher you will always go into the Activity that starts the app, if you want to skip to the next Activity you need to store that information and then jump to the Activity in your code. Also have a look at this documentation about SavingPersistentState [LINK]
Recommends Tristan · 2012-10 · Stack Overflow · on “AlertDialogue is getting destroyed when the screen orientation changed”
When orientation changes, the activity is destroyed and created again. To understand the lifetimes of activity's check this video: [this video] -Android basic video 2. Then you should figure out how you are gonna save the information package and reinitialize it when the create of the activity is called. Which can all be found in the documentation.