A route is a string until you make it a type
String routes fail at runtime on a typo or a missing argument. Serializable types move both into the compiler.
navigation
6 posts
Shared navigation has no back stack owner, and that is the hard part
Android has a system back gesture with an owner. iOS has a navigation controller. A shared back stack answers to both.
A deep link is four platform integrations wearing one URL
Verified, registered and delivered differently; parsing is the easy part.
Shared navigation state and the one platform that kills your process
A back stack in memory is correct on desktop and loses the user's place on Android.
Back means four different things, and shared navigation has to pick
A hardware button, an edge swipe, a window close and a browser history entry are not the same event. One shared handler gets at least two of them wrong.
A screen nothing navigates to still compiles
A route with no caller compiles, registers and never runs. Reachability is a graph property, so no per-file check can see it and nothing fails.