wizard_router
1.4.1, released a year ago by canonical.com
Routing for linear wizards with central route definitions and no page dependencies.
What it does
Provides linear wizard routing that eliminates tight coupling between individual wizard pages. Pages can request the next or previous step without knowing what comes before or after them, while routes and transition conditions are defined centrally.
AI-written summary of version 1.4.1, based on the package's README and metadata. Report an inaccuracy
Use it when
- You are building a multi-step wizard or onboarding flow
- You want to decouple wizard pages so they don't depend on each other's order
Skip it when
- You need complex non-linear navigation graphs or standard application routing
Strengths
- Eliminates dependencies between wizard pages
- Centralized route and condition definitions
- Supports conditional step skipping and passing arguments
Weaknesses
- Limited to linear wizard flows
- Not a general-purpose application router
Setup
- Kind
- Flutter widgets
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 3
MaterialApp(
home: Scaffold(
body: Wizard(
routes: {
'/foo': WizardRoute(builder: (context) => FooPage()),
'/bar': WizardRoute(builder: (context) => BarPage()),
'/baz': WizardRoute(builder: (context) => BazPage()),
},
),
),
)Alternatives
Packages that do the same job and could replace wizard_router.
- go_router
If you need a general-purpose declarative router for full application navigation and deep linking.
98Compare - auto_route
If you prefer code-generation-based routing with strong typing for complex navigation.
87Compare
Works with
Packages commonly used together with wizard_router: ones it builds on, ones built on it, and its own family.