Fragments and Fragment Lifecycle

# CHAPTER 15

Fragments and Fragment Lifecycle #

1. Introduction #

2. Learning Objectives #

• Explain the architectural difference between an Activity and a Fragment.

• Understand the paradigm of Single-Activity Architecture (SAA).

• Create a reusable Fragment and its associated XML layout.

• Dynamically add, replace, and remove Fragments utilizing the FragmentManager.

• Navigate the complexities of the Fragment Lifecycle (specifically onCreateView).

3. Fragments vs Activities #

• Activity: The heavyweight Window. An app must have at least one Activity. It is an independent entity registered in the Manifest.

• Fragment: A lightweight UI module. It is NOT registered in the Manifest. It cannot exist on its own; it must be hosted inside an Activity.

*Analogy:* The Activity is the television set. The Fragments are the different channels you swap out on the screen.

4. Single-Activity Architecture (SAA) #

5. Creating a Fragment #

The XML (fragment_home.xml):

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:background="#E3F2FD">

    <TextView
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Welcome to the Home Fragment!"
        android:layout_gravity="center"
        android:textSize="24sp" />

</FrameLayout>

The Kotlin (HomeFragment.kt): Fragments do not use onCreate() to set their layout. They use a special lifecycle method called onCreateView.

package com.example.fragmentdemo

import android.os.Bundle
import android.view.LayoutInflater
import android.view.View
import android.view.ViewGroup
import androidx.fragment.app.Fragment

class HomeFragment : Fragment() {

    // This is where the Fragment inflates (draws) its XML layout!
    override fun onCreateView(
        inflater: LayoutInflater, container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View? {
        // Inflate the layout for this fragment
        return inflater.inflate(R.layout.fragment_home, container, false)
    }
}

6. The FragmentManager (Swapping Fragments) #

<FrameLayout
    android:id="@+id/fragmentContainer"
    android:layout_width="match_parent"
    android:layout_height="match_parent" />

Next, in MainActivity.kt, we use the supportFragmentManager to execute a Fragment Transaction.

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    // 1. Instantiate the Fragment
    val homeFragment = HomeFragment()

    // 2. Begin the Transaction!
    supportFragmentManager.beginTransaction()
        .replace(R.id.fragmentContainer, homeFragment) // Swap the container with the Fragment
        .commit() // Execute the command!
}

7. The Fragment Lifecycle #

• onAttach(): The Fragment attaches to the Activity.

• onCreate(): The Fragment is created (but not the UI).

• onCreateView(): The XML is inflated and the UI is drawn!

• onViewCreated(): The UI is ready. This is where you should put your findViewById logic!

• onResume(): The Fragment is actively running.

• onDestroyView(): The UI is destroyed (but the Fragment logic stays alive in memory).

• onDetach(): The Fragment is completely disconnected from the Activity.

8. Handling UI Logic in a Fragment (onViewCreated) #

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)

    // Notice we must call 'view.findViewById' because the view holds the components!
    val myButton = view.findViewById<Button>(R.id.actionButton)
    
    myButton.setOnClickListener {
        println("Fragment Button Clicked!")
    }
}

9. Common Mistakes #

• Crashing requireActivity(): Fragments often need to ask their host Activity for information. If you call requireActivity() while the Fragment is in the background or completely detached, the app will instantly crash with an IllegalStateException. Always ensure the Fragment is isAdded before communicating with the host Activity.

• Memory Leaks with ViewBinding: If you use modern ViewBinding in a Fragment, you MUST set the binding variable to null inside the onDestroyView() callback. Unlike Activities, Fragments can outlive their visual views. If you hold onto the visual references, you cause a massive memory leak!

10. Best Practices #

• Never Communicate Fragment to Fragment directly: If Fragment A needs to tell Fragment B something, do not try to link them directly. Fragment A should pass the data to the shared ViewModel (or the host Activity), and Fragment B should observe that shared ViewModel. This keeps modules perfectly decoupled.

11. Exercises #

1. 1. Create a blank Fragment class named ProfileFragment and its corresponding XML layout.

1. 2. Write the Kotlin transaction code in MainActivity to .replace() the fragment container with your new ProfileFragment.

12. Coding Challenges #

13. MCQ Quiz with Answers #

14. Interview Questions #

• Q: Explain the structural decoupling benefits of utilizing Fragments over monolithic Activities. How does this architecture specifically benefit tablet/foldable UI optimizations?

• Q: Describe the execution sequence of the FragmentManager. Why must a Fragment transition be finalized with the .commit() command?

• Q: Contrast onCreateView() with onViewCreated(). Why is executing findViewById operations strictly relegated to onViewCreated() rather than onCreateView()?

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #