I'm developing android applications for a while, and followed a lot of posts about activity life cycle, and application's life cycle.
finish() on an activity, the method
onDestroy() is executed this method can do things like:
onDestroy() isn't a destructor. It doesn't actually destroy the object. It's just a method that's called based on a certain state. So your instance is still alive and very well* after the superclass's
onDestroy() runs and returns.Android keeps processes around in case the user wants to restart the app, this makes the startup phase faster. The process will not be doing anything and if memory needs to be reclaimed, the process will be killed