Kaisel – Routes as Values. Dart 3 Native Router for Flutter

kaisel.dev

58 points·TheWiggles··11 comments

Ignoring the claude-isms, this could be a godsend from the nightmare that is Go Router.

The biggest issue with Go Router is that they keep changing the damn API. I can't believe the release cadence of a Flutter navbar library is faster than entire JS frontend frameworks like Next.js

Very cool. Nav 2.0 should have been replaced by such a solution as soon as the sealed classes were introduced to dart.

I've read the quick guide and still don't understand what this is.

it's a router that uses classes instead of strings, what is there not to understand

I suppose what a router is, when it's not a tool or a network device. I assume classes as in object oriented?

Honestly if you don't understand it, it's not for you as you're not the target market, which is fine, not everything is for everyone's use cases. It's a router in the sense of navigating pages in a Flutter application like /page-a, /page-b etc and instead of having them as raw strings, the routes are defined as classes like PageA().

Hopefully not since I'm actively attempting to learn flutter for cross platform development. I'm not a professional developer and am only just starting out with flutter.

State management confuses me at the moment. Seems overly complicated with way too many options. Actually a reason I'm going with flutter I atead of a web framework was too many options with no clue which is best. Seems navigation is that way too...