Shopify apps, built to be maintained.
A working catalogue of apps for Shopify — the ones I have built, what each one actually does, and how it stays alive across quarterly API versions.
- Nothing marked live until it can be installed
- Status shown on every entry, including in development
- One developer, not a marketplace
Or pick a problem and read the catalogueThe apps
Start with three.
The lead app, two more, and a door to the rest. Every card says what it is before it says what it does.
Or browse by problem
1 more in the catalogue
What every app here has in common
Four rules, applied before anything is listed.
- 01
One job per app
An app that does four things badly gets uninstalled for one of them. This is the most expensive mistake I have watched someone make.
- 02
A supported API version
Built against a supported version from the first commit, so a quarterly bump is a diff rather than a rebuild.
- 03
Webhooks that survive duplicates
Delivery is at-least-once. Anything that writes to a merchant’s data is idempotent, because the same event will arrive twice.
- 04
No dark patterns
No forced flows, no hard-to-cancel subscriptions, no data sold onward. An app that traps a merchant is not worth listing.
Shopify retires an API version every quarter. Every app here migrates on a schedule — and the schedule leaves a paper trail.Read the changelog
The questions a catalogue raises.
Including how to tell whether an app is still being maintained.
Are these on the Shopify App Store?
Not yet. Every app here is marked In development, and none of them offers an install button until it has a public listing. When one does, its card will say Live.
Browse the catalogueDo you build custom apps as well?
Yes, and it is usually the better answer when a merchant needs something none of these cover. The difference is that a custom app is yours alone, and you own the code — the catalogue exists so you can start from something that already works.
What happens when Shopify retires an API version?
Every app here is migrated forward on a schedule rather than when something breaks. That work is planned, and it is the single most common reason a store ends up on a dead app.
Read the changelogHow do I tell whether an app is still maintained?
Check its release history. An app with a version dated within the last few months is being maintained by someone who still has to answer for it. This site publishes release notes for that reason.
Read the changelogDo you work with other developers?
If you have an app on the store and want help staying current across API versions, that is a conversation worth having.
Looking for something that isn't here?
The catalogue covers the recurring problems. If your requirement is the unusual one, that is the interesting part of the job.
Or email hello@sproutcart.co


