Of course, this is a subjective matter, read the docs, draw a schema of those methods on the paper, then try to simplify the schema - so you'll use the methods in the simplest way possible. OnDestroy - similar to activity onDestroy A fragment defines and manages its own layout, has its own lifecycle, and can handle its own input events. OnCreateView - means fragment is first created and needs a view, here I do all initialization stuff A Fragment represents a reusable portion of your apps UI. I pretty much ignore other lifecycle methods for the sake of simplicity

OnBackPressed - user pressed back button, here I finish the activity or somthing else OnDestroy - activity is destroyed, system destroyed it or the user pressed back, here I dispose stuff linked to the activity context OnResume - activity is resumed, user turned on the screen or came back to the app after he minimized it with home button, here I do resume logic, say, resume the video OnPause - activity is paused, user presses home button or turned off the screen, here I do pause logic, say, if there's a running video, I pause it OnCreate - means activity is created and showed to the user for the first time, here I do initialization stuff

once you learn what each method does, you can build in your mind your own guide. Just read the documentation about each method.

Android studio fragment on resume