Precision where the screen ends
We study the narrow edge of mobile utility — the moments when a small, deliberate tool changes a daily rhythm. Our studio keeps that edge sharp, unhurried, and quietly considered.
A working vocabulary.
Every discipline accumulates language that either clarifies or obscures. These are the terms that appear most often in our work — defined plainly, without the promotional gloss that tends to accumulate around them in product discourse.
Apple's primary distribution channel for iOS applications. Submission involves review against guidelines covering content, privacy, and technical standards. Placement and discoverability are shaped by metadata, ratings, and algorithmic curation.
Apple's pre-release testing platform, allowing developers to distribute builds to internal and external testers before public launch. Feedback loops here often determine whether a release is ready or needs another iteration.
Monthly Active Users — a count of unique accounts that engage with a product within a rolling 30-day window. A blunt instrument, but one that investors and platforms treat as a primary signal of product health.
The gate between a free experience and a paid one. Its placement, framing, and timing are among the most consequential design decisions in a utility product — too early and users leave, too late and revenue suffers.
A controlled experiment presenting two variants to separate user cohorts to measure differential outcomes. Useful for incremental decisions; less useful for questions that require qualitative judgment or longer time horizons.
The proportion of users who return to a product after their first session. Day-1, Day-7, and Day-30 retention are standard benchmarks. Retention is ultimately a proxy for whether the product delivers on its implicit promise.
App Tracking Transparency — Apple's framework requiring explicit user consent before an app may track activity across third-party apps and websites. Introduced in iOS 14.5, it reshaped mobile advertising and attribution practices.
The percentage of sessions that complete without a fatal error. A figure below 99.5% is generally considered a signal requiring immediate attention. Stability is not a feature — it is the baseline expectation.
How we work.
Research before form. We begin every engagement by spending time with the problem rather than the solution. That means reading, interviewing, mapping existing behaviour, and sitting with ambiguity long enough to understand what is actually being asked. The temptation to reach for a wireframe too early is one we aim to resist — the shape of a thing should follow from its purpose, not precede it.
Iteration with restraint. Design at our scale is not about generating volume — it is about making considered choices and testing them against real use. We work in short cycles, but we are deliberate about what we change and why. Each iteration is a question, not a guess. We document what we learn and carry it forward, so that the product accumulates intelligence rather than just features.
Release with intention. Shipping is not the end of the process — it is the beginning of a different kind of listening. We treat each release as a hypothesis about what users need, and we stay close to the data and the feedback that follows. A product that is released and forgotten is not a product we aim to make; we are built so that the work continues after the build.
What we hold to be true.
The people in the room.
Responsible for the structural decisions that determine how a product behaves under real conditions — performance, reliability, and the invisible architecture users never see but always feel.
Works at the intersection of perception and behaviour, shaping the moments of contact between a person and a product so that each interaction feels considered rather than incidental.
Holds the thread between what users need, what the team can build, and what the product is designed to become — translating ambiguity into decisions and decisions into direction.
Brings rigour to the questions that precede every design choice, ensuring that the studio's understanding of user behaviour is grounded in observation rather than assumption.