Observable Flutter: Diving into Riverpod, with Rémi Rousselet

[@flutterdev]

Subscribe for the latest → goo.gle/FlutterYT

[@jaweene]

Really liked 30:32 hearing the design steps that led from Provider to Riverpod. It was also cool to have the internals of Riverpod explained at a high level by the creator, without having to read the source. Glad the interviewer was able to stay switched on to ask interesting questions throughout

[@remirousselet6867]

There are more explanations near the end too. Taking about why I couldn't use Inheritedwidgets

[@jaweene]

@@remirousselet6867 definitely, valuable insights throughout, and thanks for your hard work

[@kingpinkent]

Fun fact: Riverpod is an anagram of Provider

[@Vindolin]

@@kingpinkent 🤯

[@mdmarcaassport]

Thank you for providing subtitles haha. And thank you Remi for such a piece of art

[@ekremkenter]

I must say, it was an incredibly insightful and engaging deep dive that left me with a wealth of knowledge and a genuine sense of enjoyment throughout. Thank you so much!

[@conceptcoder]

Indeed. Thanks Remi

[@conceptcoder]

Thanks Craig

[@_dinesh]

Thank you so much guys. This was very help. My only feedback on Riverpod is terminologies are a bit confusing. In comparison, the Store, Action, and state terminology used in the Redux pattern is very straightforward and clear.

[@verticrow]

This was awesome. Thanks for both of you giving the time to do this. But man I felt dumb trying to follow along.

[@AntonAverin]

I would love to see a similar length follow-up on the topic of chaining providers together, especially when provider is async or future.

[@conceptcoder]

50 times watched this video, and I'm getting more understand and impressed..., awesome....

[@dwylhq874]

Perfect timing. We were just debating adopting Riverpod or Bloc for our Flutter project. 👌

[@mlazebny]

Please, do not even touch riverpod.

[@_underscore]

@@mlazebny But why though?

[@nagarajalagusundaram5704]

@@mlazebny Can you please share the reasons for not using Riverpod?

[@brandon-butler]

Please explain

[@mlazebny]

@@brandon-butler ream my another comment here

[@heezhong9549]

52:31 seems there is a scrolling bug whit return null.

[@etiennetheodore]

It was a master class thanks !

[@akaneritsuki]

My head is bleeding too 😂 I love the way he used generics to get the notifier's instance instead of making another method on the Ref, so clever.

[@conceptcoder]

at 47:32 it's about infinite scroll right ?

[@arunkashyap3527]

yup

[@sentrycod2373]

Why is the item coutn property of List view builder not set? I tried to replicate that part of the video and I'm getting errors

[@arunkashyap3527]

Bro you should need to watch chapter 18

[@acavals8080]

At 6:00, to be convinced about the main advantage of Riverpod, just put some temporary log or print statements before building every widget, and you will see how it's unnecessary when we use setState.

[@harishprasadrajeurs2771]

Thanks

[@ra3eddy]

Great video, thanks! In the counter eg, the dev declares the counter provider by typing "count", but then its read or watched by using "countProvider". The dev has to remember that the second one is generated, and for a new dev, they will always be thinking where did this come from.. I think that is where the feeling of "Magic" comes from. Once you do it once its all good, but that first time feels uncomfortable

[@remirousselet6867]

I view annotations as custom language keywords. Using that logic, the annotation is all the context clues you need to know where the "countProvider" comes from. That's similar to the often requested "data classes". Where doing "data class..." make the class offer already implemented methods. They aren't user defined, but the "data" keyword is enough to know where they come from. Or how the upcoming Records have a copyWith/==/hashCode implementation

[@Dohman]

I know this is only 5 hours old, but when will the captions be available?

[@AnthonyDev]

Great talk, nice to watch after the flutter vikings talk.

[@alexmichels5182]

If you use freezed and riverpod annotation for larger Projects directly manage your build_runner. It will take ages if you have to many imports or a single package project. Also commit generated code to version control. Hope Meta programming comes soon.

[@1ManStartup]

Wow awesome video 🎉

[@KrunalShrimali-wy7tn]

What's the best way to handle token based authentication in flutter using riverpod?

[@ВалерийГаврилов-ъ9х]

Great explanation

[@王新-f3x]

I hope to have more Chinese subtitles, which can help me learn more easily

[@hadirahmani7943]

how can we separate riverpod business logic? such as mvvm

[@williambryant1672]

tbh the new generator makes it more confusing for me lol. I prefer just working with the old providers.

[@akashgkrishnan9596]

I feel jealous that these guys are so super smart and I don't think ill ever be this smart.

[@beamlakaschalew5786]

Let's goooo! 🚀

[@1234matthewjohnson]

after using a bunch of state management packages, still dont understand why it wasnt just made and defined as part of flutter. tried bloc, tried provider, tried shareprefs, tried get...landed on get in the end cos it works and its so darn simple.

[@MoAdel92]

I think such video should be done with Plain flutter_riverpod package Without riverpod annotations

[@Counter_Hour]

Yup it’s complicating the logic without apparent reason, annotations are an optional feature and this makes it look like they’re required

[@BooleanDev]

its the new preferred syntax and is easier to understand. itll become the default in the future with static meta programming

[@llamacoder]

Plz improve flutter web

[@martinbalverde]

Why is he using light theme 😬😬

[@danvilela]

Looks like you're programming on notepad.. with some blue-ish.. Just horrible

[@arjunsharma9481]

that's VS code