All 7 Named Routes & Navigator 2.0 (Router API) questions
More in Named Routes & Navigator 2.0 (Router API)
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 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? 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)

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?

Beginner

Answer

Named routes let you register each individual screen within your app under a genuinely simple, memorable string identifier, such as slash profile or slash checkout, within a centralized routes table typically defined on your MaterialApp, letting you navigate to that particular specific screen elsewhere throughout your app simply by calling Navigator.pushNamed with that exact same matching string, rather than needing to directly construct and reference that particular destination widget's own class directly every single time, which can genuinely help keep your navigation related code considerably cleaner and more centrally organized.
MaterialApp(
  routes: {
    '/profile': (context) => ProfileScreen(),
    '/checkout': (context) => CheckoutScreen(),
  },
)

Navigator.pushNamed(context, '/profile');
Real-world example A large app registers each one of its own genuinely dozens of separate screens under a clearly named, centrally organized route table, letting any given developer navigate to a specific particular screen from anywhere else throughout the app simply by referencing its own simple, memorable route name.

Common follow-ups: How do you actually properly pass specific arguments to a screen when navigating using a named route?;What is the specific practical difference between named routes and the considerably newer Navigator 2.0 Router API?

Navigation & Routing in Flutter;Flutter App Architecture with Modular Feature Folders
All 7 Named Routes & Navigator 2.0 (Router API) questions