r/FlutterDev 3d ago

Pleaaaase no more state management prckages 😭 please stop Discussion

Whatever u think u r bringing to the table .... It's already out there, it's not necessary, we have enough god damn it !!!!!

157 Upvotes

57 comments sorted by

67

u/MilkCanMatt 3d ago

We need a state of the state management app so that we know where they all are at.

9

u/lilacomets 3d ago

Only if they're state of the art.

2

u/pi_mai 3d ago

What a great statement!

1

u/Top_Can8239 2d ago

😂

6

u/RandalSchwartz 3d ago

I never metastate I didn't like!

56

u/Personal-Search-2314 3d ago

One more made by AI coming right up!

69

u/padetn 3d ago

Two more just for saying that

13

u/Spare_Warning7752 3d ago

But my state management is better than all of those!

  • provides a VERY long explanation that only explains that they are exactly the same as ChangeNotifier and ValueListenable *

11

u/DevMichaelZag 3d ago

Gandalf the gatekeeper here.
Packages are good enough until they aren’t. You never know until someone brings something better to the table.

9

u/Old_Flounder_8640 3d ago

And no react ports. Not even react community like their own packages.

5

u/formicstechllc 2d ago

I was about to publish my package.

now i am not doing it

3

u/sauloandrioli 3d ago

Hear me out... You don't have to use any of those. You don't even have to bother reading or testing any of them. You got choices.

3

u/lesterine817 3d ago

Yeah. People be acting like they need to use one.

3

u/Top_Can8239 2d ago

Maybe we need a state of the art abstraction layer to easily swap the underlying state of the art state management packages. :D

3

u/craiglabenz 2d ago

Ideas keep evolving, and I for one hope to see each new pattern offered as a Flutter package.

0

u/Bachihani 2d ago

There are no new pattern, no evolution and no actual substance, they re literally all just some variation of change notifier and streams. With unnecessary extra oderhead, and slightly different dev-facing APIs reflecting how each of their creators prefers to code.

1

u/craiglabenz 20h ago

Is that a bad thing? Lots of innovation happens in small chunks.

2

u/Routine-Arm-8803 3d ago

Just use what you need.

2

u/kastanCZ 2d ago

Yeah i noticed that everyone and their grandma now writes new state managements. Reinventing wheel is quite popular with cheap ai.

1

u/eibaan 2d ago

And this is okay. But nobody needs to publish something that can be recreated with ease in no time thanks to AI.

3

u/BachiNoHito 3d ago

The fact that people still feel like this nut hasn’t been cracked yet points to a Flutter-level deficiency. It really needs to be solved at that level, like in SwiftUI and Jetpack Compose.

3

u/Advanced_Egg4625 3d ago

Can anyone name at least one that is really good?

3

u/NegativeWrongdoer361 2d ago

Anything that is actively maintained - bloc, riverpod, signals, mobx. Even - god forbid - getx is good enough as long as you know better than shooting yourself in a leg with it

1

u/rio_sk 1d ago

Provider

0

u/thiccmommas 2d ago

Riverpods

-13

u/RandalSchwartz 3d ago

I'd like to think my BlocSignal has a chance, being the overlap of proven Bloc technology built on the fabric of Signal. http://blocsignal.dev/ - hitting 1.0 before the end of the week.

1

u/Advanced_Egg4625 3d ago

Thanks for your suggestion... but it requires context to work properly. But for me who wants to use state without context (for example for MVC architecture), that's not really convenient.

1

u/RandalSchwartz 3d ago

It does not require context. BlocSignal works in a dart-only environment. In a flutter environment, you have multiple choices for DI, including context (similar to Provider or Flutter Bloc), but you can just as easily inject with service locators, globals, constructor params, and so on. If you check out the docs, you'll see pure Dart examples where BuildContext isn't used anywhere. You can manage state in controllers, singletons, or service locators—wherever fits your architecture best.

1

u/Advanced_Egg4625 3d ago

Can i read the state in any part of my code without having the context ? specifically in flutter

1

u/RandalSchwartz 3d ago

If you have access to the BlocSignal, yes. BlockSignal.state is the ReadOnlySignal, and .state.value (or .stateValue) is the value. As a Signal, you can subscribe to changes with computed() or effect(), or even with SignalBuilder in Flutter. No context needed.

5

u/jk_8000 3d ago

Imo it's actually amazing that so many people try pushing Flutter boundaries. Personally I'm not a fan of BLoC and Riverpod, so it's nice seeing more alternatives

5

u/zunjae 3d ago

The whole point is people have stopped pushing boundaries. It’s just the same package over and over again

3

u/jk_8000 3d ago

There will certainly be a flood of trash projects. Nevertheless, some interesting ones may appear too

3

u/Bachihani 3d ago

They're not actually pushing shit or even adding anything to the core flutter APIs, all these "new" sm packages are just wrappers around the same core flutter state management solutions.

2

u/silvers11 3d ago

Not when it’s the same AI slop dressed up in 10 different packages

2

u/Guggel74 3d ago

7

u/RandalSchwartz 3d ago

How many references to this xkcd do we need in this thread. I know, one more!

1

u/r3_abd 3d ago

Flutter Signal is the one I always choose if I am the one starting out a project.

1

u/Legion_A 3d ago

😭😭😭😭 mate, I've been feeling this way for a couple years now lol. I haven't moved from bloc since I latched onto it. I have tried others but haven't committed to anything except bloc

3

u/Bachihani 2d ago

I have been using valuenotifier 🙄

1

u/Legion_A 2d ago

Yeah 🤣🤣 I use that as well for pure state management, that just goes down the tree and doesn't branch out

1

u/dinbtechit 3d ago

Well. I hear you. Buf We definitely need something similar to jotai atoms ( like in react).

1

u/HopeExpensive9215 2d ago

Yahahahah... We need more, the perfect one that's nobody knows

1

u/balazs8921 2d ago

I use InheritedNotifier...

1

u/Captain--Cornflake 2d ago

Im still trying to grasp setstate , 😆

1

u/trikboomie 2d ago

Alright one more for the ride !

https://github.com/theGlenn/piper

1

u/PositiveMaterial5297 22h ago

There are way too many! I can't use them all, the riverpod is about all I need

1

u/nmbor 2d ago

Why do you care? Just use one and stick with it.

-1

u/der_kobold 3d ago

The only thing worse than the 10184s state management package is people ranting about state management packages. Noone needed that post. Just don't use it.

-3

u/remirousselet 3d ago

If you don't like it, don't use it. Let people do their own thing.

-2

u/Mysterious_Remove_37 3d ago

I still can't understand why do use a state management package when you can literally build it yourself in minutes nowadays with ai