flutter-routing-and-navigation

Navigate between screens, handle deep linking, and manage data passing in Flutter applications. Implements robust navigation and routing in Flutter applications. Evaluates application requirements to select the appropriate routing strategy (imperative Navigator , declarative Router , or nested navigation), handles deep linking, and manages data passing between routes while adhering to Flutter best practices. Evaluate the application's navigation requirements using the following decision tree: STOP AND ASK THE USER: "Based on your app's requirements, should we implement simple imperative navigation ( Navigator.push ), declarative routing ( Router / go_router for deep links/web), or a nested navigation flow?" If simple navigation is selected, use the Navigator widget to push and pop Route objects. Pushing a new route: Popping a route: Pass data to new screens using constructor arguments (preferred for imperative navigation) or RouteSettings (for named routes). Passing via Constructor: Passing via RouteSettings (Named Routes): If named routes are explicitly required, configure MaterialApp with initialRoute and routes or onGenerateRoute . For sub-flows, instantiate a new Navigator widget within the widget tree. You MUST assign a GlobalKey to manage the nested stack.