01

Web applications

Products people sign into. Records, roles, workflows, and an interface that still feels considered on a phone.

A web application here is the product itself: the objects people keep, the roles that decide who can change them, and the jobs they repeat. Screens come after that structure. The phone layout is designed first, then the desk layout expands it, because that is where the work actually happens. Empty, loading, error, and success states are part of the interface. Performance and accessibility are part of the feature, not a later audit.

• Product structure before screens — objects, roles, and the jobs people repeat
• Interfaces with clear states: empty, loading, error, and success
• Performance and accessibility treated as part of the feature, not a later audit