The router widget is pretty complex because it solved a whole range of issues. We should think about how do we make it easier for developers to use it.

Here are some ideas:

• 1. Add more sample code on how to implement different delegates for different use cases.
• 2. Add more opinionated delegates with a simpler API for common use cases Decided to go with https://github.com/flutter/uxr/wiki/Navigator-2.0-API-Usability-Research
• 3. Add some guidelines on how to manage app state.
  • stock app rewrite (stock app rewrite using router #63424)

Documentation:

• 1. Add deeplinking documentation to MaterialApp/WidgetsApp. https://flutter.dev/docs/development/ui/navigation/deep-linking
• 2. Add more explanation around SystemNavigator.routeUpdate and SystemNavigator.routeInformationUpdate, we should mention how web browser react to these method.
• 3. Add more explanation around how web browser interact with the flutter framework. For example, web browser calls didPushRouteInformation when user click backward and forward button.