Always put super.initState() first, and super.dispose() last.

I use and highly recommend the very_good_analysis package. It's quite aggressive, but the rules definitely get you thinking about how to write cleaner code, especially for teams.

You're most welcome. You should also be aware that there's now a StreamNotifier[Provider] as well, completing the set of replacements for the legacy providers. [Async|Stream]Notifier[Provider], nicely organized. And all of those with family and keepalive strategies. Mix-n-match.

Nikki Eke Even Remi suggests that these legacy providers are confusing to the newcomer, and we should stick with just Provider, [Async]Notifier[Provider], and for now, StreamProvider, and move quickly to using the generator. Keep it simple but fully functional for the beginners.

This article really should have been updated for riverpod 2.0, and only covered Provider, StreamProvider, and the various combinations of Notifier and AsyncNotifier. The legacy providers are still supported, but moving everything to the modern notifier/provider and generated providers makes riverpod so much easier to deal with.

You missed out on one of the most important YAML details: YAML is also a superset of JSON. Any valid JSON file is also a YAML file. But even better, it's relaxed JSON where most of the keys and values don't need to be quoted! And you get comments! It's the best of both worlds.

You seem to have missed the whole riverpod 2.x rollout, because you're talking only about the legacy providers. Yes, those providers still work, but the whole [Async]Notifier[Provider] ecosystem is far more expressive and easy to use, especially when you start using generated providers. I suggest you update your knowledge, and write an updated article. Here's my take and Andrea's details on that: https://youtu.be/tfB_dSJa9Oc https://codewithandrea.com/articles/flutter-state-management-riverpod/ https://codewithandrea.com/articles/flutter-riverpod-generator/ https://codewithandrea.com/articles/flutter-riverpod-async-notifier/

I'm a big fan of using Very Good Analysis . The only thing I change is turning off "all public api is documented" when I'm not building a package for inclusion in other projects. But everything else makes my code much more bulletproof.

Or simply install puro (puro.dev), get it working for stable, then "puro create master master", and you'll be able to say "puro use master" in any flutter project to see how it works.

I presume a part 3 and 4 are coming to cover Notifier and AsyncNotifier and their respective Providers, as well as generated code. You covered so far only the parts of Riverpod 1, not Riverpod 2.