Public & Custom Apps
Apps for the Shopify App Store, and private apps built for one merchant.
- Apps through App Store review
- 2Apps through App Store review
- Review outcome on both
- First passReview outcome on both
- Infrastructure we build on
- GadgetInfrastructure we build on
Apps we've built and run
We've taken our own apps through Shopify's review process twice, so we know what passes. We proudly build and host on Gadget — it handles OAuth, webhooks, data and infrastructure out of the box, so our time goes into the product rather than the plumbing. Embedded admin UI in Polaris, billing done properly, webhooks that survive replays.
- Public App Store apps, from submission to approval
- Custom and private apps for a single store or Plus org
- Embedded admin UI with Polaris and App Bridge
- Billing API, usage charges and subscription plans
- Webhook processing with idempotent, replay-safe handlers
- GDPR mandatory compliance webhooks
Built with
Public or private, the same four stages
- 01
Scope & data model
What the app owns, what Shopify owns, and where the two sync. Most app problems are data model problems that surfaced six months late.
- 02
Build on Gadget
OAuth, webhooks, storage and scaling handled by the platform, so the budget goes into the product rather than the plumbing.
- 03
Review & billing
Polaris admin UI, the Billing API done properly and the GDPR mandatory webhooks — the three things App Store review rejects most often.
- 04
Operate
Replay-safe webhook handlers, rate-limit backoff and alerting on sync failures, so a broken integration is visible before a merchant tells you.
The private admin app they built replaced three spreadsheets and a nightly cron job. It has been running for a year and I have never had to think about it.
Theo Barnes — Founder
Shopify apps, answered
Custom if it serves one merchant or one Plus org — no review process, no listing, no billing API. Public if you intend to sell it. We build both, and the decision changes the architecture, so it is worth making early.
Usually one to three weeks once submitted, assuming it passes. We build against the review checklist from day one, which is why both of our own apps went through on the first submission.
Because OAuth, webhook delivery, data storage and scaling are solved problems, and paying to re-solve them is budget that could have gone into the product. When a build genuinely needs custom infrastructure, we say so.
Yes. Client work ships to your repository under your ownership, with no licensing strings. Our own public apps are the only exception — those stay ours.
Tell us what you're building
You'll hear back from an engineer, not an account manager, within one business day. Scope, timeline and price come in writing before anything starts.