In Parts 1–2 we built a clean AppNavHost, passed only the ID to Detail, added deep links/notifications, and hardened error handling with SavedStateHandle.
Real apps don’t stop at two screens: they have tab bars, stacks inside each tab, and sometimes we navigate from a screen in one tab into a flow belonging to another tab (e.g., from an image’s author in Home to that author’s Profile).
This part puts those production concepts into place:
Bottom navigation with multiple back stacks (each tab “remembers” where we were).
Nested navigation graphs in the Profile tab: ProfileHome → Account Setting → ChangePassword.
Cross-graph navigation from Detail (Home graph) to Profile (Profile graph).
1) Concepts & Why They Matter in Production
A. Bottom Navigation with Multiple Back Stacks
What: Each tab has its own back stack. Switching tabs doesn’t lose the…
