Component used: Fragment

Version used: 1.4.0

There are tools like toolargetool that let you explore what is taking up space in your saved instance state. However, it has no visibility into custom Parcelables like the FragmentManagerState used to store the entire FragmentManager's hierarchy of saved state.

This makes it hard to differentiate between the state of the FragmentManager itself and the state of each individual fragment, and, within a particular fragment, differentiating the view state, arguments, state provided by onSaveInstanceState(), and the fragment's SavedStateRegistry.

Therefore the focus should be on exposing the hierarchy of fragments - the bookkeeping associated with an individual Fragment and the FragmentManager specific state can and should remain as separate Parcelable instances that don't expose their internal fields.