Hey everyone 👋
After years of building production Flutter apps, I kept running into the same problem: as projects grew, state management got messy.
What started as clean architecture would eventually turn into a tangled web of dependencies. Business logic leaking into widgets, tightly coupled components, and tests that were painful to maintain.
I tried everything: Provider, Riverpod, BLoC, GetX, etc. All great in their own ways, but none gave me the modularity and scalability I was looking for.
So, I built something new: Event–Component–System.
A Flutter package for radical separation of concerns:
- Components: Pure data, no logic
- Systems: Pure logic, no data
- Events: Communication without coupling
It’s not just another state management library. it’s a new way to structure your app.
If you’re curious about the reasoning and the journey behind it, checkout my detailed article here:
Top comments (0)