Research-backed interface development

Build the interface in front of you, not a generic version of its category. Research how real products solve the same user problem, understand why their interfaces work, then make an original design whose controls, visible states, and underlying system agree.

Visual quality is a core deliverable. Aim for an interface that is immediately striking, coherent in every state, and recognisably specific to the product. A correct but generic interface is unfinished. Visual ambition never excuses unreadable information, inaccessible controls, poor performance, or unsafe behaviour.

This skill applies to any interface a person sees or controls. Websites, native apps, game HUDs, menus, touchscreens, command consoles, instrument panels, appliances, kiosks, OLED and LCD modules, and LED or button-driven devices are examples, not boundaries.

The normal sequence is:

1. Understand the medium, the user, and the job.
2. Research comparable interfaces online.
3. Synthesize the evidence.
4. Set an original interface direction.
5. Define the UI/system contract.
6. Build complete interaction slices.
7. Test behaviour and inspect the rendered interface.
8. Report the evidence, implementation, and verification.