/method

How the work runs, and how we judge it.

Instead of a wall of achievements, here is the process we follow and the questions every piece of work has to pass.

Six steps

Listen
A first conversation about who uses the product, on which devices, and what must work on day one. No commitment.
Scope in writing
We write back what we understood: what is in, what is out, open questions and assumptions. You correct it.
Design at three widths
Key screens sketched at phone, tablet and desktop widths before polish, so layout problems surface early.
Build in visible steps
Work is shown in small pieces you can open on your own devices, not saved for one large reveal.
Check against the criteria
The quality questions below are asked of every page or screen before it is called done.
Release and hand over
We help with the release itself, then hand over notes, access and anything you need to carry on.

Plain tests anyone can repeat on their own device. If a page fails one, it is not finished.

Nothing scrolls sideways on a small phone; long email addresses and names wrap.

Ask: Can I use every page one-handed on a phone?

Every control can be reached and used without a mouse, with a visible focus outline.

Ask: Can I tab through and see where I am?

Menus and pop-ups close with Escape and return focus to where you were.

Ask: Does focus come back to the button I pressed?

A failed send never wipes what someone typed.

Ask: If the network drops, is my text still there?

Success is only shown when the server actually confirms it.

Ask: Does the screen claim something it cannot know?

Animation is optional and respects the reduced-motion setting.

Ask: Is anything moving that I did not ask for?