Web Application Design
Design the application as a system of tasks, not a stack of screens.
Interface design for products people use weekly: roles, forms, tables, states and dashboards that stay consistent when the work is messy.
Daily-use interfaces
Consistency matters more than a single hero screen.
Web applications fail in production when every feature invents its own table, form and empty state. We design the product as a set of tasks, permissions and objects, then specify the patterns so new surfaces inherit the same behaviour instead of drifting week by week.
Typical constraints
The product grew faster than its interface language.
- 01The same action is labelled differently on three screens.
- 02Forms are long, unforgiving and silent when something fails.
- 03Tables cannot be filtered, sorted or understood by the people who live in them.
- 04Role differences are hidden until a permission error appears.
- 05Empty, loading and error states were never designed, so engineering invented them.
- 06Dashboards were added as an afterthought and now carry the whole product.
What you receive
Patterns for the work, not a tour of mock screens.
The file is organised around objects, roles and recurring UI so a later feature does not require a new visual dialect.
01
Task and role map
Who does what, how often, and which screens are actually load-bearing.
02
Object and permission model
The entities the UI is about, plus what each role can see, edit or approve.
03
Workflow designs
The critical paths drawn with branches, interruptions and recovery, not only the happy path.
04
Form, table and state library
Reusable patterns for input, density, validation, empty, loading and error.
05
Application chrome
Navigation, search, notifications and settings specified as a system.
06
Engineering notes
Behaviour, edge cases and component intent written so development does not reinterpret the file.
How the product UI is designed
Objects and tasks first. Screens second.
A web application is a workplace. We design the work, then the interface that makes that work repeatable.
01
Inventory tasks and roles
Frequency, consequence and who is blocked when the flow is wrong.
02
Model objects and permissions
The nouns and access rules the UI must tell the truth about.
03
Design the core workflows
Create, review, assign, export and recover paths, including the ugly branches.
04
Specify forms, tables and states
Density, validation and feedback are designed as shared patterns, not one-off screens.
05
Align patterns across surfaces
Chrome, dashboards and settings inherit the same language so features stop freelancing.
06
Hand off interaction notes
Tokens, components and behaviour so the next sprint does not invent a new table.
Useful when
This is the brief when people live inside the product.
- An internal tool has become the company's actual operating system.
- A B2B product has more roles than the original designer planned for.
- Data-heavy screens are unreadable and support tickets keep explaining the UI.
- A redesign is needed without throwing away the object model the team already knows.
- Engineering is shipping features faster than design can keep patterns aligned.
- The marketing site is fine and the application is where customers get stuck.
What we judge
The product should feel like one workplace.
Repeatable task patterns
Users learn a table or a form once and meet it again on the next feature.
Honest role behaviour
Permissions are visible in the interface, not discovered as an error message.
Fewer one-off screens
New work inherits chrome, states and density rules instead of inventing them.
A handoff engineering can keep
Notes cover behaviour, not only the default populated view.
Related work
Selected application interface work will appear here.
Product studies are published when clients clear them. Nothing here is invented to fill the section. Start from the Work index for what is already approved.
Published case studies will appear here when they are cleared.
Related services
Work that usually sits beside this.
Questions
Buying questions, answered directly.
The method is similar: tasks, structure, interaction, handoff. The artefacts are not. Applications need roles, states and density that a marketing site never has to carry.
Next move
If people use the product every week, design it like a workplace.
Tell us the workflow that keeps failing and the roles involved. We will say whether a pattern system, a single-flow redesign or a dashboard pass is the useful start.