How we build

Every app follows the same written process from idea to release, with independent checks at each stage. Nothing reaches the public without Rob's own approval.

1. A short brief first. Every change starts with a one-page brief: what is changing, who it affects and how much checking it needs. Small fixes get a light check. Anything involving personal data, children, payments or going live gets the full set of checks.
2. Previews, not live changes. Work happens on a separate copy of the code and a private preview link. Only made-up test data is used, never real children's names or photos.
3. Automated tests. Before an app goes to Apple, it must pass its automated tests and a security check of the code libraries it uses.
4. Independent checks. Whoever built a change never signs it off. Separate reviewers check the code, the design and the wording.
5. Privacy and child safety. Before release, we check the app's privacy notice, the data it stores and how long it's kept, and anything that could affect young users, such as names, photos and contact between users. We collect as little personal data as we can.
6. Testing on a real phone. iPhone builds are installed through Apple's TestFlight and checked on a real device before they go to Apple.
7. Checkpoints with evidence. Each stage has a checklist, and an item only passes with evidence such as a test log, a screenshot or a link. Missing evidence counts as not done.
8. Rob approves every release. Merging, publishing, sending to Apple and releasing to the public are separate steps. Each needs Rob's own yes, recorded with the date and the exact version.

If something goes wrong, we take the change down first, then put it right and write up what happened.

For the people using our apps, that means fair, simple tools that keep as little data as possible, get a child-safety check before release where young people may use them, and are tested on a real phone or in a browser before release.