About
A small studio for small apps.
We build iOS apps that do one job extremely well. We are small on purpose: it keeps every app focused, every decision explicit, and every release something we are proud to put our name on.
The story
Tired of apps that want our attention.
We kept installing apps for simple jobs and getting a subscription prompt, an ad and a social feed instead. The job itself was always the least polished part.
So we built a studio around the opposite idea: pick one job people pay to get done, read every complaint about the existing apps, and build the version that simply works. No account, data on your device, a fair price on the page, and ads only in a free game, never in a utility app.
Our first round produced ten ideas. The best one, a receipt splitter called Fair Bite, was cut at gate one when our critic found four brand-new apps already doing the same thing. Round two produced Fillwise, a fuel log that checks every imported row. It passed the product-spec gate on October 30, 2026 and is in build now. That ratio is the point.
What we believe
Four rules we do not break.
One job per app
If a feature does not make the core job better, it goes on the “not doing” list. Most features end up there.
Ads only where they pay for a free game
Never in utility apps. Each app’s page says whether it shows ads and what it collects.
On-device first
Your data lives on your iPhone. When an app syncs, it uses your private iCloud, which we cannot read.
Honest pricing
Pay once, or subscribe only when an app has real ongoing costs. The price is on the page before you tap.
How we work
Five gates, one of them a critic.
Our workflow runs on AI agents with clearly separated jobs: research, product, design, engineering, review, QA and compliance. The agent that builds is never the one that grades it, and every major decision stops at a human.
Gate 01
Research
We read every competitor’s one-star reviews before we sketch a single screen. The complaints become the spec.
Gate 02
Critique
A dedicated devil’s advocate scores the idea and tries to kill it. Most ideas die here, which is the point.
Gate 03
Build
One user story per branch, tests written alongside, nothing outside the agreed scope sneaks in.
Gate 04
Review
A second reviewer reads every line, then a compliance pass checks privacy and App Review rules.
Gate 05
Ship
A human installs the TestFlight build, lives with it for days, and only then presses Submit.
Who’s behind it
The getShipKits team.
Questions, ideas, or a bug we should know about? Every email is read by a person.
hello@getshipkits.com