A demo of how to use Jetpack architecture and lifecycle component to implement a form. This includes validation and submit.
Since this project uses Jetpack, you're going to need Android Studio 3.2 (currently in RC1) or newer.
There are 2 methods used that can be found on branch method1 and method2.
method1 pushed some of the form state and logic to the ViewModel where as
with method2 the fields have their own model and the form has it's own model
and the ViewModel only handles the bindings and exposing fields to the View.
Which method is better is up to you, while some argue that the ViewModel should
contain the state of the screen/form (i.e. method1), others would argue that the ViewModel is
more of an orchestration layer and should not contain anything to do with the state.
Instead the ViewModel should only expose public properties and commands (i.e. method2).
Personally I think both are fine, but the actual answer may depends on the size of your app, and the need for reuse of the logic and models.
More discussion on this code can be found on my Medium blog post Android — Form input and validation using MVVM with DataBinding