All 7 Named Routes & Navigator 2.0 (Router API) questions
More in Named Routes & Navigator 2.0 (Router API)
What are named routes in Flutter, and how do they let you navigate to a specific screen simply by referencing a genuinely simple string identifier rather than needing to directly construct that particular widget yourself? How do you actually properly pass arguments to a destination screen when using Navigator.pushNamed, and how does that destination screen then actually properly retrieve those particular passed arguments? What is Navigator 2.0, and how does its own declarative Router based approach genuinely differ from the earlier imperative push and pop based navigation approach used by Navigator 1.0? How does the go_router package provide a considerably higher level, considerably more genuinely convenient declarative routing API built directly on top of Flutter's own more complex, considerably more verbose lower level Navigator 2.0 APIs? How can you properly implement route guards using go_router's own redirect functionality to properly control access to specific protected routes based on a user's own current genuine authentication state? How do you properly test navigation logic, including verifying that a specific given route correctly and reliably navigates to its own expected screen and that a redirect properly and correctly occurs when genuinely expected?
Advertisement
Flutter › Named Routes & Navigator 2.0 (Router API)

How do you properly implement nested navigation using a considerably more complex router structure, such as one genuinely needed to properly support a bottom navigation bar where each individual tab genuinely maintains its own entirely separate independent navigation stack?

Intermediate

Answer

Implementing nested navigation typically involves defining a genuinely separate distinct Navigator specifically for each individual tab within a bottom navigation bar, each maintaining its own entirely separate independent stack of screens, while a single shared outer Navigator manages switching between those particular separate tabs themselves, and go_router genuinely supports this exact same particular pattern through its own dedicated StatefulShellRoute, letting each individual tab genuinely properly preserve its own separate specific navigation history even as a user actually switches back and forth between several genuinely different tabs.
StatefulShellRoute.indexedStack(
  builder: (context, state, navigationShell) => ScaffoldWithNavBar(navigationShell: navigationShell),
  branches: [homeBranch, searchBranch, profileBranch],
)
Real-world example A social media app uses go_router's StatefulShellRoute to properly maintain each individual bottom tab's own entirely separate navigation history, correctly ensuring a user who navigates deep into their profile tab and then briefly switches over to the home tab still finds their profile tab exactly where they had genuinely previously left it upon returning.

Common follow-ups: What genuinely happens to a specific tab's own navigation stack if the entire app itself is genuinely fully restarted from scratch?;How does this exact same nested navigation pattern genuinely relate more broadly to an app's overall chosen architecture?

Flutter App Architecture with Modular Feature Folders;Flutter Widgets Fundamentals (Stateless & Stateful)
All 7 Named Routes & Navigator 2.0 (Router API) questions