First of all, thanks for the talk! I've been looking at your approach, so far so good!
A few things you can use to enhance the clean architecture is use commands (you already are familiar with them from Xamarin). Take a look at this case:
Using something similar to AsyncCommand (from mvvm helpers on Xamarin) would solve the problem of knowing if the button can be enabled or not, if it is executing, etc. Imaging having a bit more complex UI with more buttons, you where I'm going.
I recently started using rxcommands for this, take a look and see if you can make something similar, smaller and more compact without all the bells and whistles that the package comes with.
First of all, thanks for the talk! I've been looking at your approach, so far so good!
A few things you can use to enhance the clean architecture is use commands (you already are familiar with them from Xamarin). Take a look at this case:
beyond/beyond/lib/ui/login/login_view_model.dart
Line 27 in 7e362f9
Using something similar to AsyncCommand (from mvvm helpers on Xamarin) would solve the problem of knowing if the button can be enabled or not, if it is executing, etc. Imaging having a bit more complex UI with more buttons, you where I'm going.
I recently started using rxcommands for this, take a look and see if you can make something similar, smaller and more compact without all the bells and whistles that the package comes with.