Current register implementation requires extending BaseRegister Views (i.e.Activity & Fragment classes), Models and Presenter methods.

• This results in copying over implementations in whichever module a register is being introduced in.
• Overriding a specific register layout requires more effort in changing the base implementation because things like the ViewHolders are coupled as inner classes in a RegisterProvider

To allow building registers even faster, we should provide a generic implementation (with basic defaults) and have elements of the register configurable.
To allow for this the following are to be configurable:

• Common functionality in all the different register implementations e.g. Family/Child be defined in an Activity/Register contract. This would be things like startFormActivity or saveForm
• Support the following as configurations:
  • Register/ Module Metadata
  • Row options - Allow custom row layouts and columns population
  • ViewHolder - Not having it as an inner class and also provide a default
  • RegisterProvider - use row options to provide the row functionality
  • RegisterQueryProvider - Providing count, filter & sort queries etc
    These configs will be specified in a builder pattern and with defaults provided to render a generic register.
• Have a ModuleConfiguration class which will also include:
  • Register title
  • Enabling/disabling the bottom nav
  • Module form processor
  • ConfigurableViewsLibrary