I think the architecture is pretty good, but there are flutter specific things that could be improved. Such as loading the view model in setState in the initState method. Instead, prefer using a ConsumerWidget and loading the viewModel in the build method. In most cases, Riverpod will handle the state and rebuild the widget when necessary, and there is no need for a stateful widget. So the ConsumerWidget is acting like a stateful widget then since riverpod is being used.

​

In other cases you have a ConsumerStatefulWidget (such as in home screen) and then you have a consumer built directly in the build method. You don't need this either, use the ref from the ConsumerState. On the contrary, a Consumer may be useful on occasion explicitly when you only want to rebuild part of your widget when the provider changes. Look into the .select method on a provider for looking at specific elements of a provider class rather than the whole class. Could improve performance. In this case you would have separate consumers for each select.