Working methodand the criteria we accept being measured against

Agree the edge
A short written scope: what is in, what is out, which devices and browsers, and what “done” looks like. Unknowns are listed as unknowns.
Shape before polish
Flows and rough screens before visual detail. It is cheaper to move a box than to rebuild a finished screen.
Build in readable layers
Small pieces with clear names, notes where behaviour is not obvious, and build steps written down as we go.
Check, then release
A release checklist used every time, including a rollback plan, store or hosting details and a post-release check.
Hand over properly
Source, credentials handled securely, written notes and a walkthrough, so you are not dependent on us to keep going.

Honest quality criteria

Another competent developer can build and release it from our notes.

Keyboard use, visible focus, readable contrast and sensible touch targets on key journeys.

Checked at phone, tablet and desktop widths, without sideways scrolling.

Errors, empty states and success messages say what actually happened.

Accounts, domains and store listings are in your name where possible.

These are aims we work towards and discuss openly; they are not certifications or guarantees.