320 m the flight map
Most projects touch more than one of these services. A new app needs design before it needs code, and it needs publishing help and support after. You can join at any point — the filter below helps you find where you are.
i
Planning, building and testing apps for iPhone and Android, usually from one shared codebase with native modules where the platform demands it. We focus on offline behaviour, notifications that people do not mute, and sign-in that does not lose anyone.
ii
Marketing sites, customer portals and internal tools built on maintainable, well-documented foundations, with accessibility treated as a requirement.
iii
Discovery interviews, journey maps, wireframes, prototypes and a component library your developers can build from without guessing.
iv
Developer accounts, store listings, screenshots, privacy disclosures, review notes and the calm handling of rejections.
v
A monthly arrangement for dependency updates, uptime checks, backups, small changes and a clear way to report problems. Suitable for things we built and, after a review, things we did not.
Every engagement begins with a short scoping stage. It is usually a few working sessions spread over one or two weeks and ends with a written brief: goals, users, constraints, a first-release outline, risks and an estimate range. You can take that brief elsewhere if you choose — it is yours.
After scoping, design and development run in short cycles with a working build you can open on your own device. Publishing preparation begins alongside development rather than after it, because store requirements often shape features. Support starts the day you go live, if you want it to.
We quote in stages rather than as one large commitment, so you can stop, pause or change direction at sensible points without penalty.
That is a normal place to start. Describe the problem rather than the solution and we will suggest a route.