What is the difference between a fragment's lifecycle and an Activity's lifecycle?

The lifecycle of a fragment is closely related to the lifecycle of its parent Activity. A fragment cannot exist without an Activity.

Key differences:

• onCreate(): The fragment has an additional method onAttach() before onCreate(), where it is linked to the Activity (obtaining the Activity context), and onCreateView(), where the fragment's View hierarchy is created.
• onDestroy(): The fragment has an additional method onDestroyView() before onDestroy(), where the View hierarchy is cleaned up, and onDetach() after onDestroy(), where it is detached from the Activity.
• State: A fragment can be added to the Activity's back stack, allowing its state to be restored upon return. The Activity is completely destroyed upon finishing.
• Nesting: Activities operate at the screen level, whereas fragments can be nested within each other and within Activities.

Comparison table of main lifecycle methods:

Activity Method	Fragment Method(s)	Description
onCreate()	onAttach(), onCreate(), onCreateView()	Creating an instance, binding, creating View
onStart()	onStart()	Becomes visible
onResume()	onResume()	Starts interacting with the user
onPause()	onPause()	Moves to the background or is partially hidden
onStop()	onStop()	Becomes invisible
onDestroy()	onDestroyView(), onDestroy(), onDetach()	Destroying View, instance, detaching

The fragment lifecycle is more granular, allowing more flexible management of UI component states and behaviors within a single Activity. For example, onCreateView() is called each time the View of the fragment is created, even if the fragment itself has already been created (e.g., during configuration changes). onCreate() is called only once during the fragment's lifecycle.