Named Routes & Arguments

In previous lessons, we used MaterialPageRoute for navigation. While effective for simple apps, managing many routes this way can get messy.

• Each route requires a new MaterialPageRoute instance.
• Harder to identify screens by a unique name.
• Can lead to repetitive code.

Named routes offer a cleaner, more structured way to manage your app's navigation.

To use named routes, you define them in your MaterialApp widget. This is done using the routes property.

• The routes property takes a Map.
• The key is the route's name (a String, e.g., '/details').
• The value is a function that builds the widget for that route.

The '/' route is special; it's your app's initial route.