00 FA · The studio
A small studio,deep in the stack.
FATHOMSTACK is a remote-first team of designers and engineers who build mobile products end to end. Small enough that the people who scope your project are the people who write it.
01 FA · Where the name comes from
Six feetat a time.
Fathom — a nautical measure of depth, six feet of it, taken by dropping a weighted line until it finds the bottom. To fathom is to understand a thing all the way down.
Stack — every layer a product is made of: the interface, the state, the API, the data, the release pipeline, the store listing.
Put the two together and you have our brief: understand the whole stack to the bottom, then build it so it holds.
1 fathom = 6 ft = 1.8288 m
- 00Interface
- 01State
- 02API
- 03Data
- 04Release
02 FA · How we operate
Four rules we donot trade away.
01
Measure before you build
Every engagement opens with a sounding: the real constraints, the real users, the systems already in play. Assumptions are the most expensive thing on a project.
02
The whole stack, or none of it
An app is only as good as its slowest query and its worst error state. We take responsibility from the pixel to the pipeline.
03
Ship on a rhythm
Two-week cycles and a build on your device at the end of each one. Progress you can hold beats progress you are told about.
04
Leave it maintainable
Typed, tested, documented and yours. If you take the codebase in-house next year, that should be a Tuesday, not a migration.
03 FA · The route
Sound, chart, build,harden, ship.
The same five phases on every engagement. The durations move with scope; the order does not.
- 01
Sound
We drop the line. Goals, users, constraints and the systems you already run, measured before anything is drawn.
Week 1 - 02
Chart
Flows, architecture and a scoped release plan. You approve a map, not a mood board.
Weeks 2 to 3 - 03
Build
Two-week cycles, a real build on your device at the end of each one. No demo-ware, no surprise integration month.
Weeks 4 to 10 - 04
Harden
Device-matrix QA, accessibility passes, crash and cold-start budgets enforced before we go near a store.
Weeks 11 to 12 - 05
Ship
Submission, phased rollout and monitoring on day one. Then we plan the next version with the data the launch gave us.
Release
- Coverage
- Remote-first · Working across GMT-8 → GMT+5
- Cadence
- Two-week cycles, a build on your device at the end of each one.
- Communication
- One shared channel, a written weekly note, no status theatre.
- Ownership
- Your repository, your accounts, your store listings, from day one.