I need some advice with designing a view of a system with the following characteristics:
- Lots of possible data ('label: information')
- Data is quite loosely coupled, but there is some grouping
- Only show data that is filled in
Aim: Show the filled-in information about the customer in a uncluttered/clean view.
The data: We have a customer object with a lot of fields. It holds all kinds of information that is loosely grouped together. 25 fields of general information, 10 fields of banking information, 5 fields of personal interests where there are a few lists, and 20 other fields that don't really group anywhere. Almost none of the fields are mandatory, and the customer can have 2 or +50 fields filled in. Some customers only have the banking information filled in, and one of the general fields.
The problem: How do you keep a nice UI/UX if you can show only the filled in information? Because you don't really want the page to appear very empty for customers that only filled in a few fields. You don't want to show a information group with a header if it only has a single field, etc, etc. You can't put things in a grid, because there a lists as information fields, etc.
Anyone has experience designing such a system?