ROBOSISTEMS / Guide
Guide: words and preparation
A short glossary and an honest guide to preparing for a first conversation with any development team, not just us.

Glossary
- MVPThe smallest version already useful to real people.
- BacklogThe ordered list of product tasks.
- Range estimateA low and high bound explaining what drives the gap.
- WireframeA colourless screen sketch to discuss structure.
- PrototypeA clickable model of a flow with no real logic.
- Design systemComponents and rules that keep an interface consistent.
- APIAn agreement on how programs exchange data.
- Technical debtTemporary decisions that later slow change down.
- Release candidateA build tested as if final.
- Store listingThe app’s store page: name, description, screenshots.
- Store reviewThe store’s assessment before publishing.
- RegressionA bug in something that used to work, after a change.
Nothing found. Try another word.
How to prepare for a first conversation
Describe people, not features
“A technician wants to see today’s bookings” is more useful than “we need a calendar”.
Name what already exists
A site, spreadsheets, another system, a domain, store accounts — all shape the plan.
Separate “must” from “nice”
It makes the first version easier to define.
Be honest about timing
If there is an event or season to hit, that is the main constraint.
Do not send secrets
Passwords and confidential documents are shared separately, once agreed.