Technology architecture: 6 engineered systems for consumer-app growth experimentation

Nonio runs monetisation and retention experimentation for mid-size subscription apps and games — as a delivered service first, a self-serve platform later. The name comes from the vernier scale, the instrument that reads finer than its main scale. This page maps the 6 proprietary systems the delivery runs on.

System overview · 6 systems as one closed loop

02134566 SYSTEMSAS ONE CLOSED LOOP
  1. 0Client productApp / Web / Game
  2. 2Nonio SDKclean data
  3. 1Experiment orchestratorexperiments
  4. 3Monetisation enginedelivery surface
  5. 4Creative generatordelivery surface
  6. 5Journey runtimedelivery surface
  7. 6The datasetpriors feed back

Client consumer product → 2. The Nonio SDK turns events into clean data → 1. Experiment orchestrator turns clean data into experiments → shipped through three delivery surfaces with zero app releases (3. Monetisation engine, 4. Creative generator, 5. Journey runtime) → outcomes feed 6. The dataset → priors feed back into scoring and ranking, sharpening the next cycle.

The 6 systems

Select a dial position

Where defensibility accumulates

Run experimentsLog outcomesBuild priorsPick sharperCOMPOUNDING

Where defensibility accumulates

The dataset holds every experiment Nonio has run: what was tested, on which product, what it cost, and how conversion to paid, revenue per user and retention moved. Seeded on day 1 with the team's documented playbook, it feeds back into experiment scoring and variant ranking, so lessons learned at one client speed up the next. Building an equivalent record requires running the experiments; each year widens the gap, and the same records become the brain of the self-serve platform.

01 · Run experiments02 · Log outcomes03 · Build priors04 · Pick sharper

Demo video

[ VIDEO PLACEHOLDER ]

Demo not yet provided

The recorded walkthrough will be published at the stable URL /demo.

Product screenshots

Illustrative

Placeholder UI mocks — no client data, no measured results

Monetisation engine · request-time stateIllustrative
Price
€6.99
Paywall
Variant D
Offer
Annual −20%
Trial
7 days

Values shown are illustrative examples, not client data.

SDK · event dictionary + quality monitorsIllustrative
  • paywall_viewedschema ok
  • offer_presentedschema ok
  • checkout_startedschema ok
  • purchase_completedschema ok
  • refund_recordedschema ok

Illustrative event names and monitor states.

Journey runtime · two variants in parallelIllustrative
InstallDay 1Day 7LapseReturn
Variant A
Variant B

Illustrative lifecycle schematic — triggers, timing and content run as experiments.