Systems & app engineering lab · London

Software, put through proper experiment.

Bench diagramAn apparatus: a flask labelled idea feeds a condenser labelled build, which drips into a phone labelled release, with a return line labelled support. ST.01 BRIEFST.02 BUILDST.03 RELEASEST.04 SUPPORT

AMA OS Labs designs, builds, publishes and looks after mobile apps, web products and the systems behind them. We work like a lab: a stated hypothesis, controlled variables, written results — and nothing shipped on a hunch.

Book a bench sessionRun the release assay

Station 01Brief
Station 02Build
Station 03Release
Station 04Support
Observation01

Most software problems are measurement problems.

Apps rarely fail because a team could not write code. They fail because no one wrote down what “working” meant: how fast a screen should load on a five-year-old Android handset, which permissions a store reviewer will question, who answers when a payment provider changes an API on a Friday. Our first job on any engagement is to make those expectations explicit and testable.

That is what we mean by a lab. Not white coats — a habit of writing things down, isolating one change at a time and keeping the notebook open for whoever inherits the work.

Sv-1 · Mobile

iOS and Android applications

Native Swift and Kotlin where the hardware matters; a shared cross-platform codebase where it does not. We will tell you which, and why, before a line is written.

Sv-2 · Web

Web products & PWAs

Fast, accessible web applications and the APIs that feed both web and mobile clients.

Sv-3 · Interface

UI/UX design

Flows tested with paper and clickable prototypes before they are tested with budget.

Sv-4 · Release & care

App publishing and support

Store listings, privacy labels, review responses, signing keys, crash monitoring and dependency updates — the unglamorous part that keeps an app alive after launch day.

Specimen02
Mockups of a mobile app interface showing a map screen and a social feed
Illustrative stock image of mobile interface design — not AMA OS Labs work. Photo via Unsplash, Unsplash Licence. Credit details.
Hypothesis

A smaller first release learns faster.

We encourage clients to publish the narrowest version that answers a real question about their users, then iterate from evidence. It is cheaper, and the store review cycle becomes routine rather than an event.

Read the protocol
Conditions03
Working conditions

Who comes to the bench

Founders with a validated idea and no in-house engineers. Established organisations with an ageing app that needs re-platforming. Teams who have built something themselves and now need help getting it through App Store and Google Play review — or keeping it running afterwards. We work remotely across the UK, Monday to Friday, 09:00–18:00 UK time.

Describe your project