An app you can still install next year.

Merchants and developers who have outgrown a generic app, or who are choosing between several that each solve a third of the problem. They can read an API version, and they can tell whether an app is still being looked after.

The visitor's actual question

"Is one of these the thing I need, and is it still maintained?" — a catalogue is judged on breadth first and on whether anything still ships second.

That is why every card carries a status, why each app gets a dated release history from its first release, and why there is a changelog page at all. An app without one is asking you to take it on faith, and there is no reason to.

What every app here has in common

• 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.
• A supported API version — Built against a supported version from the first commit, so a quarterly bump is a diff rather than a rebuild.
• 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.
• 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.

How an app gets made

1. Shape — One job per app. If a second problem needs solving, it becomes a second app.
2. Build — Against a supported API version from the first commit, so migration is never a rewrite.
3. Ship — Tested on a real dev store, then submitted with a listing a merchant can actually read.
4. Maintain — Each quarterly API version is a scheduled piece of work, not an incident.

What this site does not claim

No install counts, no store totals, no "trusted by" logos, and no testimonials. Nothing here has been verified, and a catalogue that pads itself with numbers makes the real ones harder to believe. Where an app is still in development, its card says so before you have read a word of it.