Most Shopify app projects don't fail on code — they fail on the parts nobody scoped: the App Store review loop, the GDPR webhooks, the bulk-data path that breaks on a 200k-order store. Knowing the full process up front is how you set a realistic timeline and avoid the month-four surprises. Here's what actually happens between "we want a Shopify app" and a live listing in 2026.
TL;DR
- The process is eight phases: discovery, architecture, UI (Polaris), backend, storefront integration, App Store review, QA/security, and launch.
- Public apps run all eight, including a review-and-resubmit loop that averages 3–7 cycles. Custom apps skip review entirely and launch in weeks.
- The phases that blow up timelines are review iteration and bulk-data/GDPR testing — not the feature build.
- Realistic end-to-end: 6–10 weeks for a non-trivial custom app; 3–6 months for a public app from idea to listing.
Before you start: pick your app type
The process differs depending on whether you're building a custom app (one merchant, no review) or a public app (App Store, full review). If you haven't made that call yet, read Custom vs Public Shopify Apps first — it changes which phases below apply to you.
The eight phases
Phase 1 — Discovery & spec
Clarify scope, review existing data and merchant flows, and write the spec. Two weeks for anything touching checkout, billing, or B2B; skippable for trivial extensions. This is where you decide what the app does and what it explicitly won't.
Phase 2 — Architecture & API mapping
The decisions that lock in cost for the rest of the build: GraphQL Admin vs REST, online vs offline access mode, Theme App Extension vs Storefront API, bulk operations vs paginated queries. Get this wrong and you rewrite the backend later.
Phase 3 — UI build with Polaris
Embedded admin UI in Shopify Polaris, Shopify's React design system. Polaris is mandatory for App Store apps — non-Polaris UIs are a leading first-pass rejection reason. Custom apps can deviate, but staying on Polaris keeps you portable to a public listing later.
Phase 4 — Backend & API integration
The actual logic: OAuth, session-token auth, App Bridge, GraphQL Admin queries, webhooks, Shopify Functions where applicable, and background jobs. This scales with how many Shopify surfaces you touch. Every app needs a backend you host yourself — see our hosting guide for where to run it.
Phase 5 — Storefront / theme integration
If the app renders anything on the storefront, you need a Theme App Extension (the modern, Online Store 2.0-compliant path) or a Storefront API integration. Script-tag injection is deprecated — don't build new apps on it.
Phase 6 — App Store review (public apps only)
The phase most plans underestimate. First-pass review takes 5–14 business days; each resubmission 5–10. Real public-app submissions average 3–7 cycles before listing. Common rejections: non-Polaris UI, missing GDPR webhooks (customers/data_request, customers/redact, shop/redact), billing-API errors, performance regressions, and unclear listing value-props. Budget calendar time and rework here — it's the single biggest timeline risk.
Phase 7 — QA, security & bulk-data testing
Apps that handle order data, PII, or financial calculations need explicit testing of bulk-operation paths and GDPR webhooks. The merchant who installs on a 200k-order store on day one surfaces bugs your 50-order dev store never will. Test at scale before launch, not after.
Phase 8 — Launch & listing
For public apps: listing copy, screenshots, demo video, and pricing-tier setup in the Partner Dashboard. Strong listings (good copy, 4+ screenshots) convert installs at a materially higher rate than bare-minimum ones. For custom apps: install-link handoff and merchant onboarding.
Realistic timelines
| App type | Idea → live | Where the time goes |
|---|---|---|
| Theme App Extension / simple custom | 2–4 weeks | Build + QA |
| Non-trivial custom app | 6–10 weeks | Build + bulk-data testing |
| Public app | 3–6 months | Build + 3–7 review cycles + listing |
The build itself is rarely the long pole. For public apps, review iteration is — which is why custom apps launch so much faster.
Where projects actually stall
- Underscoped review buffer — teams plan for one review pass and get blindsided by five.
- GDPR webhooks left to the end — they're a guaranteed rejection if missing or wrong; build them in Phase 4, not Phase 6.
- No bulk-operations plan — works on the dev store, falls over on a real catalog.
- Agency holds the Partners account — always own your own app credentials and source code.
What this connects to
- Budgets per phase and app type: Shopify App Development Cost 2026, or get an instant range from our Shopify App Cost Estimator.
- Choosing custom vs public before you start: Custom vs Public Shopify Apps.
- A real app we shipped through this process: Inside FirstBridge Analytics.
FAQ
How long does it take to build a Shopify app in 2026? 2–4 weeks for a simple Theme App Extension or custom app, 6–10 weeks for a non-trivial custom app, and 3–6 months for a public App Store app once you include 3–7 review cycles.
What's the hardest part of the process? App Store review for public apps — it's iterative, partly outside your control, and the leading cause of timeline overruns. GDPR-webhook compliance and bulk-data handling are the usual rejection triggers.
Do I need Polaris for a custom app? It's not required for custom apps, but using it keeps your code portable if you later productise into a public app, where Polaris effectively is required to pass review.
Can I skip App Store review? Yes — build a custom app. It installs via a direct link and isn't reviewed by Shopify, which is why custom apps launch in weeks rather than months.
Planning a Shopify app build? First Bridge Consulting runs the full process — discovery to App Store — for custom and public apps. Tell us what you're building →