Intro to Activity and Its Lifecycle

Activity is one of the four components of Android and it provides an interface to the user so that they can interact with the views.

Simply, activity is a single screen in an app. It could be a maps screen in the Google Maps app or user profiles in the Facebook app or contacts list screen in the Contacts app and settings screen in the Settings app. Most apps contain multiple screens and inside these screens, you have buttons, edit texts, check boxes, list items and more with which you can interact.

Activities should be declared in the manifest file and of all the activities in an app, only one activity will be the launcher activity.

How to create an Activity:

1) Right click on the app module, hover over New option and then on the Activity.

Create Basic Activity

2) Now, select the Basic Activity and change the activity name to Second Activity.

Create Basic Activity

3) Click Finish to create the Second Activity.

You'll see one method is overridden it's named onCreate. The activity is automatically added to the AndroidManifest.xml file during the creation. (Something like below.)
    <activity
             android:name=".SecondActivity"
             android:label="@string/title_activity_second"
             android:theme="@style/AppTheme.NoActionBar">
The activity tag is added to the AndroidManifest.xml file under the application tag. It has attributes like name, label, and theme. name is the package name, theme is the activity theme and label is the title of the activity which is visible on the toolbar when the activity is launched.

The lifecycle of an Activity:

The lifecycle of activity helps you understand when the activity gets created, destroyed and how you need to manage the states so that the app is less likely to suffer unexpected behavior, reduce the consumption of battery and the user will have better experience.

Similar to the existing overridden method in the Second Activity, we can override a few methods like onResume, onPause, onStart, onStop, onDestroy, onRestart (shown below).
override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_second)
    setSupportActionBar(toolbar)

    Log.d("SecondActivity", "Activity Created")
}

override fun onRestart() {
    super.onRestart()
    Log.d("SecondActivity", "Activity Restarted")
}

override fun onStart() {
    super.onStart()
    Log.d("SecondActivity", "Activity Started")
}

override fun onResume() {
    super.onResume()
    Log.d("SecondActivity", "Activity Resumed")
}

override fun onPause() {
    super.onPause()
    Log.d("SecondActivity", "Activity Paused")
}

override fun onStop() {
    super.onStop()
    Log.d("SecondActivity", "Activity Stopped")
}

override fun onDestroy() {
    super.onDestroy()
    Log.d("SecondActivity", "Activity Destroyed")
}
These overridden methods are part of the Activity lifecycle and we will discuss them below in detail.

onCreate():

Called when the activity is created. The is the first callback ever triggered before the UI elements are drawn and their positions are calculated. You can attach a layout to the activity using setContentView() and start initializing the UI elements or variables as this is the initial state.

onDestroy():

Called when the activity is destroyed. Final callback an activity receives before it is torn down and eventually removed from the memory.

The activity is getting destroyed because of the back button click or finish is called or the orientation of the device changed or the screen size is scaled for multi-window.

Also, any resources (like the database instances) or listeners (like broadcast listeners) that is not cleared in onStop should be removed in the onDestroy.

onResume():

Called when the activity is resumed. The activity is visible to the user and they can start interacting with it. This is where you start the camera preview or other system resources that only one application on the device can use at a time.

onPause():

Called when the activity is paused. In this case, the activity is partially visible to the user but they can't interact with the elements on it.

This method is executed for a very short period of time, so, heavy running tasks like saving data to the storage or database or network calls or heavy shutdowns should be performed in onStop instead.

onStart():

Called when the activity is started. In this state, the activity is visible to the user and ready to become interactive. This method is shortlived.

onStop():

Called when the activity is stopped. Stopped meaning the activity is no longer visible to the user. This could be because the app is closed or different activity is opened.

This method is the ideal place to release system resources, remove location listeners and stop animations. Removing location listeners in onStop and not in onPause makes sure that the location information and its related UI is updated even when the app is multi-window.

onRestart():

Called when the activity is restarted after it is stopped.
Let's take a look at multiple scenarios to understand when these methods are called.

Sc1: Activity is launched for the first time.

For the activity to launch, the activity needs to created, the layouts need to be attached, the UI elements need to be placed at the right position and the user should be able to interact with them. So, in this case, onCreate, onStart and onStop are called.

Sc2: A dialog is shown on top of an activity.

The activity becomes partially blurred by the dialog and this calls the onPause method. Once the dialog is dismissed, onResume is called. No other lifecycle methods are called.

Sc3: A phone call is received or home button clicked.

In both the scenarios, the activity is hidden completely triggering the onPause and onStop methods. When you get back to the activity by ending the call or opening the application, the onRestart, onStart and onResume methods are called.

The second half of the flow is only disrupted when the system is need of resources and it decides to kill the app. In this case, the flow mostly remains the same with small change. When the app is minimized by clicking the home button, the onPause, onStop is called subsequently. Now, the system kills the application and when launched again, instead of calling onRestart and onStart, the onCreate and onStart is called followed by onResume.

Sc4: Back button is clicked or called finish().

When the back button is clicked or finish() then the activity gets destroyed. The activity will go to onPause state then onStop state and finally onDestroy callback is called.

Sc5: Screen is rotated

Screen rotation event makes the system to tear down the visible screen and re-create it. In this case, onPause, onStop, onDestroy are called during the teardown process and during the re-creation process onCreate, onStart, onResume are called.

This is the reason why, when the screen is rotated, you lose the data stored in the variables and the information on the screen is lost.

Sc6: Different activity is opened from the current activity

First, the current activity goes to pause state calling onPause. When the current activity is in the pause state, the different activity is created, started and resumed triggering onCreate, onStart and onResume in succession. Now, the current activity is completely covered, its onStop is called.

Sc7: Scaled to multi-window

Similar to screen rotation, the system tears down the activity and recreates it. Along with both the actions. the system takes the focus away from the app. So, during the teardown, onPause, onStop, onDestroy is called and during the recreation onCreate, onStart, onResume is called as usual. Since the app loses focus onPause is also called.

For better understanding, build a sample application and log the overridden lifecycle methods then perform the above scenarios and verify the logs.

Popular posts from this blog

How to Read Metadata from AndriodManifest File

Metadata tags are key-value pairs and one of the decent ways to access the API keys from the libraries. They are added to the AndroidManifest.xml under the application tag and are available through the PackageManager . If you have worked with third-party libraries or even with App shortcuts, Downloadable Fonts, Firebase MLKit, you may have come across metadata tags. In the article, let’s add the metadata tags to the app module’s Manifest file and read the metadata key-values and the key-resource from a library module both in kotlin and java. Add meta-data: Add metadata to the app module's AndroidManifest.xml file under the application tag. You can add as many metadata elements as you want and you can also add metadata under the activity, service, broadcast receiver, content provider tags. <meta-data android:name= "com.gsrikar.library.LIBRARY_ACCESS_KEY" android:value= "masndfiu4er9funwikesd" /> <meta-data and
Read more

Mr Phone - Find The Next Best Phone You Want To Buy

Image
Want to buy a phone and not sure which phone to choose? Mr Phone is a phone search application and is here to help you find the best phone. The application was built by acidandrage and is available in the Google Play Store with In-app purchases. Search for your device and detailed specs gets loaded along with the image. You can tap the image for more pics or save the phone specs to view later. You can compare specs of any two phones or choose to use the Best Fit option. The Best Fit option of the app will show you the list of best-matched phones based on the preferred specs you've selected. Sections like New Releases and Popular shows the newly released phones and the phones that became most popular recently. While Stories section gives you to the Top Stories about smartphones, apps, and the Events section notifies you about the launch events of the smartphones. Great Day Readers! To give us more insights into the application development, Ashish Hooda, Head of
Read more

Add Spacing to Recycler View Linear Layout Manager Using Item Decoration

Image
In this article we will learn about, item decoration in Android and how we can use it to add even spacing between the child items. A RecyclerView without spacing will look like the image below but in most cases, we want to add spacing between the items. [You can see there are no margins between the views and only elevation] A more traditional option is adding margins in the list item xml file. If we take this route, we will soon end up with uneven spacing issues with vertical margins. [There are even left, right, top, bottom margins for all the rows except the last item in the first image and in the subsequent image, the top margin for the first item is half of the other items] The best way is to add the ItemDecoration to the RecyclerView as it affects the individual items and you can have more control over them. Kotlin: /** * Add vertical, horizontal spacing to the recycler view */ class DefaultItemDecorator(private val horizontalSpacing: Int,
Read more

Add Options Menu to Activity and Fragment

Image
Options Menu contains a set of primary menu items that are accessible to the user. In this article, we will take a look at how to implement the options menu in an Android Activity or a Fragment. Right click on the res directory in Android Studio and select Android Resource File option. It opens the Resource File creation modal where we need to enter the file name and select Resource Type as Menu. Clicking on OK button creates main_menu.xml under menu directory. Now add the following items to the XML file. <menu xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto"> <item android:id="@+id/search" android:icon="@drawable/ic_search_white" android:orderInCategory="100" android:title="@string/action_title_search" app:actionViewClass="androidx.appcompat.widget.SearchView" app:showAsAction="ifRoo
Read more

Create Assets Folder, Add Files and Read Data From It

Image
Sometimes, we need to read the data stored in the files during runtime and want to make sure the data is not tampered by the Android build system. In this article, we will take a look at how to create the assets folder using Android Studio and read the stored data from it. First, Right-click on the module name or the package name. This opens an option window where we need to select the Assets Folder option by hovering over New and then on the Folder option. Now, we will see a window where we change the folder location and the source set. Change the values if necessary otherwise keep the defaults and click Finish. It may trigger a Gradle Sync. Irrespective of the sync, the Assets folder is created and is visible in the module. Now, Right-click on the Assets folder and click on the File option by hovering over the New option. Enter the name of the file name and click Enter to create the file. The file with the name user_details.json is created under the assets folder. Add some JSON
Read more