In my app, one of the main feature is to complete 'forms'. One form contains a lot of read-only information, described by the following mockup.
On this UI everything is read-only:
- descriptions which are dynamic for each form
- then a list of bullets of 'steps' of the specific form (maybe small icons would be displayed instead of circles)
- prop#Xes are additional information/properties for each list item
Submitting (entering values) of a form is done via the submit button, which displays a new UI for input-entering.
Almost everything is dynamic, so I'd display everything (besides the header/tabs and the buttons at the bottom) in a vertical scrollview.
Sometimes 1-3 special forms would be displayed to the user, this is reflected by the #1 concept.
Most of the time one form will be displayed for the user, so in those case there would be no header:
but, in the future, sometimes the forms would be assigned to days of the week, still allowing the user to complete any of them on any day:
As mentioned above I want the user to easily navigate between the forms, allowing him to quickly overview them and select the ones they want to complete.
There are quite some information which describes why the specific form has been given to the user. This is one of the selling points of the app that it provides this information, so the user understands what's happening behind the scenes. Of course without this info the form is still sensible and has value, but this part adds an extra value to the software. This information consist of the following type of data:
This information is form-dependent, so each form has been generated based on different reasons!
I'm thinking about how to 'merge' these things together (the form and the 'additional data' information).
If I put every information on the form, then it will be very long, nobody will scroll down, nobody will see the 'why did s/he got that form' part.
Then I thought of putting this info to ViewPager, but that's not good, because I want to use the ViewPaging/swipe-ing to navigate between the currently issued forms.
Then I thought that I have an extra tab-control inside the form with 3 pages (form, reasons, stuff-you-need), but
I don't like it
It's against all guidelines to have 2 tabcontrols on the same page
Any help and kind advice is really appreciated!