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.
In the books example, you have a navigation rail down the left side of the page. I am trying to replicate this functionality with permanent sidebar navigation and was using this example as a reference. I have realised in testing however that this rail is not persistent and is built again on every page load (not the expected behaviour). As a result, if you pay close attention to the InkWell effect on the navigation buttons, when you click them they start the animation however cancel early when the page is loaded and the new version of the navigation rail loads.
In the books example, you have a navigation rail down the left side of the page. I am trying to replicate this functionality with permanent sidebar navigation and was using this example as a reference. I have realised in testing however that this rail is not persistent and is built again on every page load (not the expected behaviour). As a result, if you pay close attention to the InkWell effect on the navigation buttons, when you click them they start the animation however cancel early when the page is loaded and the new version of the navigation rail loads.