MVP Development en New York
How we work in New York
The demo runs fine in the room where it was built
It gets shown from a laptop, with the local machine or a server one hop away, and everything answers instantly. Nobody has opened it over the connection of the person who has to decide. Half an hour of testing from that connection beats another week of features.
A maximum time written down in the first week
We put in writing how long each key screen may take for someone far away, and that goes in as an acceptance criterion. It is one line in the document and costs nothing. Turning it into a project six months later costs a lot more and always arrives in a hurry.
With twenty users there are no percentiles, there are sessions
A first version has no volume for a percentile to mean anything, and pretending otherwise is self-deception. You look at sessions one by one, which also gives you the detail. The aggregate starts to help once there are enough visits that one bad one does not drag the result.
Watch out for architecture that locks the distance in for good
Splitting the product into many pieces that talk over the network before you need to turns every operation into several internal round trips. For something still looking for its shape that is dead weight. You start simple and split when a number asks for it, not in advance and not out of habit.
Answering your questions
What people ask us about MVP Development in New York.
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