{"id":37003,"date":"2024-11-01T09:53:59","date_gmt":"2024-11-01T09:53:59","guid":{"rendered":"http:\/\/atmokpo.com\/w\/?p=37003"},"modified":"2024-11-01T11:42:39","modified_gmt":"2024-11-01T11:42:39","slug":"kotlin-android-app-development-course-activity-lifecycle","status":"publish","type":"post","link":"https:\/\/atmokpo.com\/w\/37003\/","title":{"rendered":"Kotlin Android App Development Course, Activity Lifecycle"},"content":{"rendered":"

<\/p>\n

Hello! In this article, we will take a closer look at one of the most important concepts in Android app development, the Activity Lifecycle<\/strong>. An Activity is a fundamental component that composes a screen where users interact, and its lifecycle defines how it changes as the app transitions between various states. As users use the app, the Activity goes through several states, and we will learn how to save or restore important information during this process.<\/p>\n

What is an Activity?<\/h2>\n

An Activity is the most basic component that represents a screen where users can interact in Android. Activities allow for various tasks to be performed through different UI components, and multiple Activities can be combined to build an app. For example, a photo gallery app may have an Activity for selecting photos, an Activity for viewing photos, and a settings Activity.<\/p>\n

Activity Lifecycle<\/h2>\n

The lifecycle of an Activity is managed through several callback methods such as onCreate()<\/strong>, onStart()<\/strong>, onResume()<\/strong>, onPause()<\/strong>, onStop()<\/strong>, and onDestroy()<\/strong>. Each method is called when the state of the Activity changes, allowing the developer to control the operation of the Activity as declared in the manifest.<\/p>\n

1. onCreate()<\/h3>\n

This method is called when the application is first launched and typically performs UI initialization tasks. It is called only once when the Activity is created for the first time. Here, the layout is set up and data binding is usually performed.<\/p>\n

\nclass MainActivity : AppCompatActivity() {\n    override fun onCreate(savedInstanceState: Bundle?) {\n        super.onCreate(savedInstanceState)\n        setContentView(R.layout.activity_main)\n    }\n}\n    <\/code><\/pre>\n
2. onStart()<\/h3>\n
This method is called when the Activity starts to become visible to the user. It is invoked just before the Activity begins to interact with the user, meaning the Activity is on the screen but has not yet gained focus.<\/p>\n
\noverride fun onStart() {\n    super.onStart()\n    \/\/ Prepare tasks for the Activity to be shown to the user.\n}\n    <\/code><\/pre>\n
3. onResume()<\/h3>\n
This method is called when the user can interact with the Activity. You can write code here to optimize the UI and user interactions.<\/p>\n
\noverride fun onResume() {\n    super.onResume()\n    \/\/ This is called when the Activity gains focus and performs UI update tasks.\n}\n    <\/code><\/pre>\n
4. onPause()<\/h3>\n
This method is called when another Activity begins to be shown to the user. It is mainly used for saving data or releasing resources.<\/p>\n
\noverride fun onPause() {\n    super.onPause()\n    \/\/ Save necessary data before leaving the Activity.\n}\n    <\/code><\/pre>\n
5. onStop()<\/h3>\n
This method is called when the Activity is no longer visible. For example, it is called when another Activity completely obscures the screen or when the app moves to the background. Necessary resources can be released here if required.<\/p>\n
\noverride fun onStop() {\n    super.onStop()\n    \/\/ Stop UI updates and release resources as needed.\n}\n    <\/code><\/pre>\n
6. onDestroy()<\/h3>\n
This is the last method called when the Activity is terminated. Necessary tasks for memory cleanup can be performed here, usually when the Activity is no longer in use. It cleans up all resources.<\/p>\n
\noverride fun onDestroy() {\n    super.onDestroy()\n    \/\/ Perform Activity cleanup and resource release tasks.\n}\n    <\/code><\/pre>\n
Activity Lifecycle Sequence<\/h2>\n
The lifecycle states when an Activity is created and terminated can be represented in the following diagram.<\/p>\n
\"Activity<\/p>\n
Example of Utilizing Lifecycle Methods<\/h2>\n
Now, let\u2019s demonstrate how to use Activity lifecycle methods with a practical example. Below is an example of a simple counter app that increments the count each time a button is clicked in the user interface, demonstrating how to save and restore data using lifecycle methods.<\/p>\n
\nclass CounterActivity : AppCompatActivity() {\n    private var counter = 0\n\n    override fun onCreate(savedInstanceState: Bundle?) {\n        super.onCreate(savedInstanceState)\n        setContentView(R.layout.activity_counter)\n        \n        \/\/ Restore previous state\n        savedInstanceState?.let {\n            counter = it.getInt(\"counter\", 0)\n        }\n\n        findViewById