About the studio
We design and ship mobile utilities — carefully, slowly, with the kind of patience that lets a tool age without rotting. The studio runs lean on purpose, picks fewer projects than it could, and stays in conversation with what we shipped long after the launch is over.
What we stand for
Every screen we don't add is a regression we don't ship. Scope gets measured by what we removed, not what we shipped — and the ratio gets stricter as a tool matures, not looser.
Every permission gets a sentence of plain copy explaining what it unlocks. If we can't justify it to a user with no patience for jargon, we don't request it — and a feature that needs an unjustifiable permission gets cut, not rationalised.
Utilities are designed to keep working through OS upgrades, locale changes, and category drift. Three-year code is the brief on every project we accept — not three-month code that ships fast and rots quietly.
Crashes, performance regressions, and store rankings get written down in clear language. Stakeholders read prose, not dashboards — and the writing tightens, not spreads, as a release stabilises.
Working principles
The studio is distributed. Work happens in writing first, calls second, and only the calls that needed a call. That makes the team forgiving of timezones, and the codebase forgiving of memory.
Decisions get drafted, posted, and read at the reader's own pace. We trust good prose to do what bad meetings used to — and trust people to interrupt only when interruption is the cheapest option.
One project per engineer at a time. One category per quarter for the studio. We move sideways when context-switching is genuinely free, and we admit when it isn't.
Changelogs read like notes from someone who knows the user, not marketing from someone selling to them. Bug fixes get named honestly. Features get explained in plain sentences without exclamation marks.