jwill · August 29, 2015 14:02
diff --git a/gistfile1.txt b/gistfile1.txt
 As you were moving around between apps, you probably noticed that from a *user* perspective, Android doesn’t announce changes in app state, it doesn’t announce that it’s low in memory, or ask users to close apps to free up resources. In fact, it does everything it can to make the resource limitations of the device invisible to the user.
 That means keeping the foreground app running smoothly, and switching between apps seamless -- and that means killing apps in the background (remove background app layers) if it needs their resources to make that happen.
 So, we know that as soon as your app isn’t visible, it’s lifetime is as perilous as that of a Stark at the Red Wedding -- likely to die without notice (but ready to return from the dead). That tells us some very important things about how our apps should behave to be good citizens, and provide a great user experience.
 From a system perspective, onPause and onStop are signals that our app may be killed imminently, so we need to clean up any resources that need an orderly teardown -- such as closing any open connections or sockets.
	As you were moving around between apps, you probably noticed that from a user perspective, Android doesn’t announce changes in app state, it doesn’t announce that it’s low in memory, or ask users to close apps to free up resources. In fact, it does everything it can to make the resource limitations of the device invisible to the user.
	That means keeping the foreground app running smoothly, and switching between apps seamless -- and that means killing apps in the background (remove background app layers) if it needs their resources to make that happen.
	So, we know that as soon as your app isn’t visible, it’s lifetime is as perilous as that of a Stark at the Red Wedding -- likely to die without notice (but ready to return from the dead). That tells us some very important things about how our apps should behave to be good citizens, and provide a great user experience.
	From a system perspective, onPause and onStop are signals that our app may be killed imminently, so we need to clean up any resources that need an orderly teardown -- such as closing any open connections or sockets.