The purpose of the go_router for Flutter is to use declarative routes to reduce complexity, regardless of the platform you're targeting (mobile, web, desktop), handling deep linking from Android, iOS and the web while still allowing an easy-to-use developer experience.
Using Material Design's Bottom Navigation behaviour description I would like to use go_router for "an Android app that requires frequent switching between sections [that] can preserve each section’s state". Would like to be able to use go_router for deep linking and navigation between sections and the creation of individual page stacks where required.
The CupertinoTabView implementation currently uses a Navigator v1 component internally for each bottom navigation item and probably isn't a candidate for use with go_router.
Using Material Design's Bottom Navigation behaviour description I would like to use go_router for "an Android app that requires frequent switching between sections [that] can preserve each section’s state". Would like to be able to use go_router for deep linking and navigation between sections and the creation of individual page stacks where required.
The CupertinoTabView implementation currently uses a Navigator v1 component internally for each bottom navigation item and probably isn't a candidate for use with go_router.