Thanks for this! It is really helpful to understand how to utilize Riverpod in general.
@TylerCodes6 ай бұрын
Happy to hear so!
@shiningzhang22886 ай бұрын
Excellent tutorial, love it. Thank you so much.
@TylerCodes6 ай бұрын
No problem! Eventually I have plans for a follow-up with a few more tips about riverpod. But until then, my latest WIP series uses riverpod to it's fullest potential so check it out!
@hospicehounfodji43786 ай бұрын
Thanks, make a tutorial about freezed
@TylerCodes6 ай бұрын
I use freezed all the time. I haven't done a dedicated video for it, but you'll see it covered in much of my content. I'd suggest looking here perhaps: kzbin.info/www/bejne/kIrHYoWXq6-pbZY&pp=gAQBiAQB
@amin_abdedaiem6 ай бұрын
pls a complete clean archetecture + riverpod + serverpod app video series from 0 to app store/ play store publishing, it will be the last thing any one planiing to be a mobile dev to watch or take, if u do it i will be soooooo appreciative.
@TylerCodes6 ай бұрын
I do love this idea but it's tricky because it's so specific. I worry every specific part of the tech stack will alienate viewers. ie, people who like bloc over riverpod + people who like firebase over serverpod. I fear it would take a lot of work with little viewership. Change my mind.
@amin_abdedaiem6 ай бұрын
@@TylerCodes tbh I agree with in regard to bloc but for serverpod I feel like they are two distinct approachs and allot of startups or small companies would prefer local hosting and that's serverpod, but for bloc I agree with everything u said.
@TylerCodes6 ай бұрын
I will consider this tho. I’d have to keep the app scope pretty minimal so it’s not a year long video haha. Any ideas?
@amin_abdedaiem6 ай бұрын
@@TylerCodes I guess a lil book sharing app can be good!? Since u have data that is being received from the server and since we are talking books, it can use external pdf libraries as well as u can retrieve the author name and likes as well as book title and cover, even if we made it as simple as possible it would still be interesting and cover everything from clean architecture and serverpod as well as Riverpod and this way we have covered 92% of app dev in flutter, the rest will be just optional stuff like animation and ux as well as mutiaping like using maps and local services like location and Connectivity. ❤️
@TylerCodes6 ай бұрын
@@amin_abdedaiem I like the idea. However, I have something in mind with similar challenges that is closer to something I've actually wanted to build. Gonna give it some thought. I'll also be prefacing the series with a "we are basically building this live" kinda thing because normally I prebuild whatever I teach but I defs don't have the time to build it twice haha.
@adil_ayoub_6 ай бұрын
wow 😊😲😮
@michaelamir256 ай бұрын
These global provider variables are what I hate the most about Riverpod 🤷🏻♂
@TylerCodes6 ай бұрын
The reference to the provider (service locator) is global (so that you can access it) but you can’t do anything with the service locator itself. You need ref to access it (for read, listen, watch, etc.). This is no different than using get_it with bloc. If you really didn’t want global (for some reason) you can instantiate the providernotifier in your local code but I don’t see any reason to do that. What state management library do you use that doesn’t have something global?