Autumn desk · Beeswing & remote GB

A sceptical engineer should be able to read your experiment without a translator.

Appstreamgrid is a small school for people who already ship app features and still watch lift evaporate in the next release. We treat A/B Test Analytics for Apps as a writing and measurement craft, not a dashboard tour.

Open the flagship syllabus →

Notes from people who already had an experimentation tool

These are not launch quotes. They name the module that actually changed a weekly ritual.

The assignment lecture in Readout Craft made me reopen three iOS tests we had treated as gospel. Two of them had leaked users through a shared paywall. The readout template is now on our wiki; it is slower to fill, which is the point.

Priya N., product analytics, Manchester

I still dislike CUPED. The guardrail module, though, stopped us shipping a checkout change that looked fine on conversion and ugly on refunds.

Client in grocery delivery, Leeds

Desks you can sit at this year

Short programmes. One flagship with a full module list. Fees on the pricing page are informational; nothing here is a checkout.

Laptop showing analytics charts on a wooden desk

Readout Craft

Flagship. Six modules on metric trees, peeking, variance reduction, and a readout a staff engineer will actually argue with.

Smartphone resting beside printed product sketches

What we refuse to romanticise

A/B Test Analytics for Apps is mostly unglamorous: bucketing bugs, metric definitions that drift after a rename in the event taxonomy, and stakeholders who want a number by Friday. Our teaching starts there.

You will write a pre-analysis plan, name the primary metric before looking, and practice saying “this test is inconclusive” in a room that wanted a ship decision. That sentence is a skill, not a personality trait.

How the school is run

From the journal

Longer pieces, not recaps of the syllabus.

All journal pieces