Riverpod Tutorial 02 - Reading providers best practices

[@wesleybarnes5376]

What I really like from what you showed is the ability to pass a reference (read: ref.read) and use it in other provider classes, changes everything for me, thanks! Good to hear some locals on the topic here too!

[@FunwithFlutter]

Awesome

[@tadaspetra]

He's BACK!!! Great video 😊

[@FunwithFlutter]

☺️

[@TechWithDnes]

This is awesome. More on Riverpod... ))

[@joachimstokke2288]

Thank you for taking the time to make these videos!

[@FunwithFlutter]

You're welcome 🙂

[@hasan_eke]

You are great, thank you !

[@FunwithFlutter]

Happy to help!

[@TheBadFred]

That clarifies some problems that I had with riverpod. Thanks. The whole provider variety is more confusing than helpful, I think. A universal provider would be nice. The structure of the documentation is even more confusing.

[@dimitristotsios2292]

You may be right for the documentation, but after watching this series it is obvious how you can use some of the providers.

[@awlad]

At 13:35 you mentioned not use ref.watch inside your provider but what if you want state to be updated based on for example firestore document stream? How would you deal with that? Thanks

[@TheGaoNan]

Awsome as always, Thank you!

[@alfredschilken6154]

Thank you very much for your tutorials and especially for the two Riverpod tutorials. How about a tutorial about unit testing apps that use Riverpod?

[@FunwithFlutter]

Have a couple of videos lined up before getting to testing :). Next one is FutureProvider and AsyncValue. This will probs be my favourite one. And a must watch to learn some cool tricks

[@banglafactsteller6780]

plz upload video regular

[@FunwithFlutter]

Will do!

[@techzone2009]

why you stop the series of riverpord ? please continue ....

[@FunwithFlutter]

👀

[@xeliani.7809]

Could you make a video about a secure login method that should stop most hackers?

[@FunwithFlutter]

I could! But security behind login is mostly on the backend! Some tips for login on a mobile app. 1) Don't store any credentials, 2) Be sure to use HTTPS (extra bonus do Certificate Pinning), 3) Only use biometrics to store a long lived session token, not a username and password. 4) be sure to use the correct text views (for example hide the password with *****).

[@TheGaoNan]

Hey There, i would like to know how can i close a streamProvider? Lets say i have a stream that returns an int, and the stream is Stream.periodic with 1 second as duration. The int is incrementing by 1 from 0 - 5 and once reached 5 i wish to close the listening to the stream so the UI won't rebuild again and again. How can i implement it? this is something im having alot of trubles with lately and didn't found any good explanation suprisingly. Thank you!

[@FunwithFlutter]

Hey there. Take a look at autoDispose on providers. You can dispose a provider with the ProviderReference (ref)

[@TheGaoNan]

@@FunwithFlutter Hi, i've looked at it, can you provide a code example of what it should look like, i've really struggeled with it for a long time. Thank you once again!

[@FunwithFlutter]

@@TheGaoNan pub.dev/documentation/riverpod/latest/all/StreamProvider-class.html

[@abdallahhussein5997]

When you type and explain can be much better understanding than to explain the written code already. That is my suggestion

[@FunwithFlutter]

Good suggestion!

[@_birdy_birdy]

The music, in the beginning, was kinda annoying it was hard to understand what you were saying.

[@FunwithFlutter]

Oh no, sorry. 😨