MVP Development en Edinburgh
How we work in Edinburgh
What can wait and what cannot
Can wait: captions on the marketing videos, the full manual review, the conformance document. Cannot wait: headings in order, labelled fields, visible focus and contrast in the base colours. The first can be added the day it is needed. The second, if it is missing, gets fixed by touching every screen at once.
The component library decides for everything that comes after
The button, the field and the dialogue are written once and used two hundred times. If the dialogue returns focus properly from the start, it returns it properly on the next forty screens without anyone thinking about it again. If not, every new screen inherits the same fault and multiplies the cost of putting it right.
Validating with five people who all navigate alike validates little
If everyone testing your MVP uses a mouse, a big screen and good eyesight, you have validated for that profile. It is worth putting somebody who navigates by keyboard, or with the text enlarged, into the sample. It costs the same and tends to surface problems that are not about accessibility but about badly ordered screens.
The decisions get written down
What was decided, what was postponed and why, in the repository itself rather than in somebody’s memory. If the product carries on with another team, it inherits the reasoning along with the code. Without that, the first person in afterwards will undo half of it without knowing it was deliberate.
Answering your questions
What people ask us about MVP Development in Edinburgh.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
MVP Development: stack, process, use cases and FAQs