Method
Criteria instead of trophies
We have nothing on a shelf to boast about — and we don't invent anything. Instead, here is how we work and what we consider minimum quality.
- 01
Conversation
We clarify the goal, people and constraints. It ends with a short written summary you can correct.
- 02
Scope
We fix what goes into the first version and what doesn't. We recommend starting smaller.
- 03
Design
Flows and prototypes are tested before the main code is written.
- 04
Build
Short iterations with working builds you can open.
05 · Handover
Code, access, instructions and a list of known limitations.
Minimum quality
Eight checks we don't skip
- Readability
- Body text no smaller than 16px; contrast meets WCAG 2.2 AA.
- Touch
- Interactive targets at least 44×44 pixels.
- Keyboard
- Everything that works with a mouse works with a keyboard, with visible focus.
- Narrow screens
- We check 390px width without horizontal scrolling.
- Motion
- Animation is disabled when the system asks for reduced motion.
- Data
- We collect only what a feature needs, and explain it.
- Errors
- Error messages say what happened and what to do; entered data isn't lost.
- Honesty
- We don't call work 'done' until it has been checked against this list.
What we don't promise
- Zero bugs — instead we promise to acknowledge and fix them within the agreed terms.
- Specific business results: sales, downloads, ratings.
- Approval by app stores or search engines.
- Deadlines without an agreed scope.
How often do you show progress?
We agree the rhythm at the start; usually a working build after each iteration.
What if the scope changes?
We record the change, assess its effect on time and cost and continue only after you confirm.