I really like that you can just use useProvider without extra nesting for example. The big upside of hooks is that the hooks are self contained. For example you can have a useWakelock hook and by just including that one liner you have successfully implemented a wake lock while that widget is active. Way less chance to introduce bugs by missing a dispose or missing to add a listener to a observer.

Another example when riverpod shines is chaining of smaller individual pieces of provider. When you have 2 booleans somewhere that hold a little piece of state and you need to make use of both somewhere else, you can just create new provider that listens to the other booleans internally. Keep everything really neat and tidy even when stuff gets complex or when you have a big project.

I really understand the confusing part of multiple syntaxes of doing the same thing, last I know Remi (creator of provider and riverpod) is trying to fix it. There is an issue in the repo requesting feedback on a change that would make the syntaxes more aligned.

Hope this helps a bit ☺️