Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature/question] Why not Riverpod #9

Open
holzgeist opened this issue Dec 17, 2024 · 2 comments
Open

[feature/question] Why not Riverpod #9

holzgeist opened this issue Dec 17, 2024 · 2 comments

Comments

@holzgeist
Copy link
Contributor

Is your feature request related to a problem? Please describe.

This is more of a comment than a real request for change. Before I stumbled upon components-flutter, I implemented a similar set of widgets for our flutter app (though not as flexible). I used Riverpod for state management. On its website it says, that it is meant to be the successor of the provider package used in this repo. It was written by the same author(s?).

Describe the solution you'd like

Given that 1.0 is out already it might be too late, but would you consider switching provider for riverpod? Some advantages:

  • listening to changes without redrawing the widget (e.g. listen to microphone/camera mute state and store it in local storage for persistence)
  • listening to changes outsite the widget tree (in our case to communicate with global services injected by injectable)
  • easily combine providers (allows splitting up providers in smaller chunks)
  • and more

Describe alternatives you've considered

I'll stick to riverpod for our app as both riverpod and provider can coexist to allow for incremental transitioning

Additional context

Thanks for this awesome library/ecosystem and for keeping improving it 🚀 🙏

@cloudwebrtc
Copy link
Contributor

Hi, I am trying to read Riverpod docs. Since components should not have too many users at present, if Riverpod can simplify the amount of code and improve performance, I can try to migrate without changing too much code structure.

@holzgeist
Copy link
Contributor Author

Hi @cloudwebrtc

thanks for your response and for considering riverpod.
However, after trying to switch to these components in our app, I realized that it's really hard to customize e.g. the device buttons without reimplementing the whole hierarchy of widgets to actually use the customized version. This is not a problem with this repo, but with how flutter works IMHO. I'll stay with our current widget implementations for now

Feel free to close this issue unless you want to have it around if you plan to switch to riverpod at some point 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants