· the getShipKits team
Why getShipKits ships small apps
One job, done properly, beats ten tabs that almost work. Here is why we build small, and what we refuse to build.
Open the App Store and search for almost anything. You will find an app that does what you want, plus nine things you did not ask for, behind a subscription, after an ad. We started getShipKits because we were tired of that trade.
The problem with big apps
Big apps are not evil. They just drift. Every release needs a headline, so every release adds a feature. A tab here, a social feed there. After two years the thing you opened the app for is buried three taps deep, and it still has the bug you reported in version 1.2.
Then the business model drifts too. Features that used to be free move behind a paywall. A one-star review we read while researching says it better than we can: “40 bucks just to tell the app that I drank milk.”
What “small” means here
Small does not mean cheap or thin. It means one job, done so well that you stop thinking about it.
- One job per app. If a feature does not make that job better, it goes on the “not doing” list. Most features end up there.
- No account. If an app can work without knowing who you are, it should.
- On your device. Your data stays on your iPhone. When an app syncs, it uses your private iCloud.
- Honest pricing. Pay once, or subscribe only when an app has real ongoing costs. The price is on the page before you tap.
- Ads only where they pay for a free game. Utility apps are paid for, not ad-supported. Each app’s page says whether it shows ads.
Why small is harder
Saying no is the hard part. Every idea at getShipKits goes through five gates: research, critique, build, review and ship. At the critique gate, a dedicated devil’s advocate scores the idea and tries to kill it. For our first app we evaluated ten ideas. Six were rejected outright, mostly because someone already does them well or because Apple already ships the feature in iOS.
The winner was Fair Bite: split a restaurant check by what each person actually ate, with tax and tip shared in proportion, down to the last cent. We wrote the spec, built a working prototype and sent it to the critic.
The critic found four apps released in the last few months that already did the same thing: on-device scanning, no account, one-time price, some of them for less than half of what we planned to charge. Our idea was not wrong. It was late. So we cut it at gate one, before a single line of production code. That is not a failure of the process. That is the process.
Round two is different. Our next idea, Fillwise, is a fuel log for people who want to move their history out of another app. It has passed the spec gate and is in build. It is not on the App Store yet.
What you can expect from us
Apps that open fast, do their one job, respect your privacy and do not nag. Release notes that tell you what changed. A real person behind hello@getshipkits.com.
And when a feature request would turn a small app into a big one, a polite “no, but thank you”. That no is the product.