I always thought the usability/ergonomics of the Flutter framework was slightly poor, but the Dart language itself is pretty darn awesome!

I also rolled my own reactivity interfaces, and made many shorthand functional wrappers for standard things I use frequently to debloat the GUI boilerplate.

My stuff isn't robust enough to consistently live seamlessly alongside regular flutter code or to release for anyone elses use.

I am super stoked to see that I'm not the only one to find the stock flutter framework something that can be improved, and that others more confident than me (and more experienced with other frameworks) are putting things like this out there.

Congratulations and thank you.

I even dream that someone would reimagine the entire flutter framework, maybe just reuse some of the low level rendering and eventing but rebuild everything else on top of that.

Apologies to anyone on the flutter team if I sound too critical, you've put something very useful and difficult out there, but a lot of design choices seem to be mutually inconsistent or just have so many counterintuitive aspects to them, usually justified in the name of performance.

I often find myself thinking I am just not smart enough to figure out the right way to do something with flutter. A lot of abstractions that are hard to get them to work how I want or run into weird corner cases. Many simple things I just ask AI to solve it, and after seeing the solution I can see it is right, still don't understand why my attempt was not.... so I welcome alternative interfaces and approaches.

Thanks for the kind words! I came up with this library based on my own experiences — I had a few insights while using these patterns, and decided to turn them into a library.

Flutter chose to design its framework around an approach similar to React, which I think was a deliberate trade-off.

However, I feel that the Dart language itself lacks several important features. For example, we can’t implement JavaScript-like Proxy objects or getters/setters in the same way. This makes it impossible to achieve deeply reactive behavior like what Vue provides.

In addition to Dart being pretty neat, Flutter itself has been a pretty first class citizen then it comes to documentation and developer tooling/experience.

Mobile remains a big surface to integrate and evolve well.

> I always thought the usability/ergonomics of the Flutter framework was slightly poor, but the Dart language itself is pretty darn awesome!

I think a lot of ergonomics issues of the Flutter are because of Dart language lacking in some areas. Flutter team even demonstrated how Flutter is expected to improve when certain features land in Dart. (Not sure if/how cancelation of macros will affects this.)

I'm (im)patiently waiting for augmentations and declaring constructors to be completed. Augmentations alone will help with so many things.