Notes from running the studio.
How we choose what to build, what we refuse to ship, and what actually transferred when we built the same pipeline a second time. Written by the people doing the work, about work that has shipped.
- The studio model
- Product principles
- Engineering
- Distribution
What a consumer software studio is, and what it is not
Axiom Trinity Labs takes no client work. Here is what that model changes about how the products get designed, funded, and maintained.
We do not score you out of ten
A number is the easiest output to build and the least useful thing you can hand a user. Why our coaching apps name the fault instead.
Building the same pipeline twice
How the video and pose infrastructure built for Disc Golf Form Analyzer became the foundation for Dinklix, and what did not transfer.
How a product gets into the register
The studio's filter for what to build next: an acute problem, a visible artifact, a reason to pay, and infrastructure we already own.
The store listing is the product
Most of a consumer app's conversion is decided before install, on a page you get roughly one second to win. How we treat that page.
What we mean by owning the stack
Not that we build everything from scratch. That we own every point where our product can fail in front of a user.