User interfaces and frontend
We design and implement interfaces for web applications. We connect screens to data and application logic, covering mobile use, permissions, forms and situations where saving or connectivity fails.
An interface built around a task
We build interfaces for new applications and extend existing ones. We start with user actions: finding information, completing a form, approving a change or checking a status. We establish the views, data and permissions needed, then connect interaction design with implementation.
For each important action, we define waiting, success, empty and error states. Messages should explain the outcome and the available next step. We confirm a save after receiving a reliable result, and show when a longer operation is still in progress.
We agree on the devices and browsers to check. Clear labels, visible focus, keyboard operation and errors linked to their fields help people use forms. We define these requirements before acceptance rather than judging an interface solely by its appearance.
A save the user can follow
Example form states after submission.
- Form
The user enters data and saves.
- Waiting
The view shows the operation is in progress.
- Confirmation
Success appears after a reliable response.
A message identifies the problem and next step.
An unconfirmed save
A form after a connection loss
The example distinguishes entered values from a confirmed save.
- Entered values
Values can remain in the form.
- Unconfirmed
The interface shows that the save is unconfirmed.
- Retry
After reconnection, the previous attempt is checked before retrying.
For example, an employee could lose the connection just before saving a completed job form. The interface can retain the entered values, clearly show that the save is unconfirmed and allow a retry. Once the connection returns, it needs to establish whether the previous attempt reached the server.
Draft storage requires decisions about where data is kept, for how long and when it is removed. Not every form should leave its contents on a shared device. We choose how to preserve work according to the information involved, access rules and actual application use.
Selected operations can be queued for later execution. This requires backend support, protection against repeating the same effect and rules for resolving changes made in the meantime. For other operations, retaining the form and asking the user to approve the current data again is more appropriate.
The interface as part of the system
We control the amount of code and data downloaded by the browser. We split larger views, retrieve the information needed and coordinate data refreshes with the backend. Reducing unnecessary requests helps, but response times also depend on the network, server and database.
Dividing the interface into modules makes related features easier to develop. We use shared components where behaviour needs to remain consistent. Screen descriptions and process rules should reflect the terminology used in the business, including when people with different permissions use the system.
We check key journeys in the browser, covering saves, errors, permissions and the agreed screen sizes. At handover, we document how to run and deploy the application. The interface can be part of a custom application; our fullstack page explains the choice of tools.