Feed
I think it's also worth noting that this article's interpretation matches Compose architect Leland Richardson's intention. In his video explanations, Leland explains that Compose is designed to avoid a hidden coupling between ViewModel and View where the ViewModel starts to take on the shape of the View (e.g., by having a state called "ShowToast"). Great stuff!
What about Field validation for example for this Login screen?
I negotiated with my friends many time
They make a variable on view model and when the user input something updating it, whenever user click the login button they made a validation in view model, so if we have multiple fields we should make an error state for each one
What about surviving process death and you want the bottomsheet to still be up when the user returns?
Roger Colque Calcina
#android-dev #js-dev