345 apps on the App Store, from one codebase
A pipeline that turns content into finished, published apps: built, screenshotted, listed, priced and submitted without anyone clicking through it.
- 345
- apps live on the App Store
- 36
- languages
- 1
- codebase
The problem
Publishing one app by hand is a day of work that has nothing to do with the app: builds, screenshots at every screen size, a store listing, a price in every country, a submission. Publishing three hundred that way is not possible for one person.
What I built
One iPhone app that becomes every app, driven by data. A story reader, a dictionary, a set of flashcards and an exercise book are the same program with different content. Around it, a pipeline builds each one, takes its screenshots, writes its listing, sets its price and submits it, and refuses to go on when a check fails.
What that means for you
If you have content (courses, a catalogue, a set of guides, a back list of books), the same approach gives you an app for each title or each market without a team to make them one at a time. And the part that is not about apps applies to anything: work that is repeated can be built once and run.
Other things I have built
-
Store submissions without the clicking
The App Store and Google Play both have steps no API covers. I automated them in the browser, with checks, so they are done the same way every time.
-
Sheet music engraved in the browser
A music player that draws its scores from data rather than showing pictures of them, and plays along. 95 pieces are on the site today.
Have something like this?
Say what you need in a sentence or two. You get a fixed price and a date within one working day.
Ask for a price