Mobile app for your Shopify store.
Native or hybrid, builder or custom, when it pays off. The five decisions every Shopify brand faces before commissioning a mobile app.
Five decisions. USD 5M revenue threshold.
A Shopify brand commissioning a mobile app makes five decisions: do you actually need one (USD 5M revenue threshold + retention-positive customer base); native or hybrid (hybrid wins for 80 percent of Shopify cases); builder or custom (Tapcart / Vajro for standard ecommerce, custom for differentiated UX); the launch checklist (12 items including ASO, deep links, analytics, push); and the push notification strategy (five healthy categories, avoid generic broadcasts). Get all five right, the app pays back in 12 to 24 months and compounds. Get them wrong, the app becomes a maintenance burden that produces no incremental revenue. Published by Prasun Anand.
When does a Shopify store actually need an app?
Three conditions must hold. USD 5M-plus annual revenue (the customer base needs to be large enough that per-user retention lift justifies build cost). Repeat-purchase rate at category benchmark or higher (the app's value is retention; without it, no app fixes a one-time-purchase brand). Engagement value beyond purchase moments — content, community, loyalty, exclusive launches the customer wants to experience between purchases. Missing any one of those three usually means the app does not pay back.
The math. A USD 50K hybrid app build at 1,000 active app users, converting 30 to 60 percent better than mobile web on a USD 100 monthly LTV, produces USD 30K to 60K annual incremental revenue from the app cohort alone. Recovery in 12 to 18 months, compounding thereafter. Below 1,000 active app users, the build cost amortizes too slowly. The threshold for considering an app: 5,000 monthly active mobile customers, retention metrics at or above category benchmark, and a content or loyalty story that gives users reason to open the app between purchases.
Categories where apps work well in 2026. Subscription brands (recurring engagement, predictable user behavior). Beauty and skincare (regimen tracking, restock reminders, content). Apparel with frequent drops (limited-edition launches, push notifications for new arrivals). Pet and food brands with subscription components (delivery tracking, reorder flows). Fitness and wellness with content alongside commerce. Categories where apps usually do not pay off: low-frequency one-time purchases (furniture, mattresses, single-purchase consumer goods), niche B2B with limited customer count, and any brand where repeat purchase rate is below 20 percent at 12 months.
The deeper "should you build" framework, including the cohort-modeling spreadsheet, is in the cluster post on retention economics; the build-cost depth is in the dedicated mobile development services pages.
Native or hybrid?
Native (separate iOS Swift and Android Kotlin codebases) for apps needing deep platform integration — Apple Wallet, HealthKit, hardware sensors, advanced AR, near-perfect platform UI fidelity. Hybrid (React Native or Flutter, single codebase to both platforms) for time-to-market, cost efficiency, and the 80 percent of cases where the app is content plus commerce.
Native advantages. Best possible performance on platform-specific UI patterns. Direct access to platform APIs as they ship (some Apple APIs lag in React Native and Flutter wrappers by months or years). Zero cross-platform abstraction overhead. The right path when the platform-specific experience IS the differentiator — fitness apps with HealthKit deep integration, AR shopping experiences using ARKit, wallet-based loyalty programs using Apple Wallet passes.
Hybrid advantages. Single codebase across iOS and Android cuts engineering cost roughly in half. Faster shipping cadence — fixes and features deploy to both platforms simultaneously. Smaller team — one mobile team can own both apps. React Native and Flutter both produce apps that 95 percent of users cannot distinguish from native; the gap is narrower in 2026 than it has ever been. For ecommerce content + cart + checkout + browse + loyalty experiences, the gap is functionally zero.
The choice for Shopify-store apps. Hybrid wins for 80 percent of cases. Use the Shopify Storefront API to power product catalog, cart, and checkout from either Flutter or React Native. The deeper native-vs-hybrid breakdown is in Native vs hybrid mobile app.
Mobile app builder or custom build?
Builders (Tapcart, Vajro, Shopney) for standard ecommerce — catalog, cart, checkout, push, basic loyalty — at USD 200 to 1,500 per month. Custom when you need brand-specific UX, custom workflows builders cannot represent (configurators, B2B portals, content-heavy experiences), or unusual data integrations.
Builder advantages. Time-to-market: a builder app can launch in two to four weeks. Cost: monthly subscription instead of upfront build investment. Maintenance: updates, OS-version compatibility, App Store policy compliance handled by the platform. Reasonable templates for standard ecommerce. The right path for brands testing whether an app is justified before investing in custom.
Builder constraints. UX templates limit how far you can differentiate. Custom workflows often impossible (or possible only via the platform's specific extension API). Branding constraints — the app feels like a brand on the builder's template, not a brand-native experience. Performance and bundle size determined by the platform, not by your team. App Store optimization shaped by the builder's defaults.
Custom advantages. Total UX freedom — every screen, every interaction designed for the brand. Custom workflows possible (configurators, B2B account portals, content-heavy experiences). Better performance and smaller bundle from purpose-built code. Differentiated app store presence. The right path for brands at scale where the app is a strategic surface, not just a mobile-optimized store.
The detailed comparison of Tapcart, Vajro, and the other major Shopify mobile app builders is in Shopify mobile app builders comparison.
Twelve items on the launch checklist.
App Store Optimization assets, App Store Connect and Google Play Console setup, App Review submissions, crash reporting, analytics, push notification provider, deep link strategy, ASO keyword research, beta testing, install attribution, retention monitoring, and update strategy. Each one ships before launch or you ship a hobbled app.
The non-negotiables. App icon designed at 1024x1024 with optical sharpness at 32x32. Screenshots in every required size for every device class — iPhone 6.7", 6.1", 5.5", iPad 12.9", iPad 11", plus Google Play phone and tablet sizes. App Store description tested against ASO best practices (first 25 words are critical, keywords in title where allowed). App Review submissions: Apple takes two to four weeks for first approval, Google one to three days; budget for two review rounds.
The infrastructure. Crash reporting via Firebase Crashlytics or Sentry — without it, you ship blind to crashes that cost you 5-plus percent of users in the first week. Analytics via Firebase Analytics or Amplitude for behavior. Push notification provider — APNs for iOS, FCM for Android, abstracted through a service like OneSignal, Braze, or your own backend.
The retention layer. Deep links mapping web URLs to app screens (a customer clicking a product email should land on the product in the app, not the homepage). Install attribution — Branch, Adjust, AppsFlyer, or Firebase Dynamic Links — so you know which acquisition channel produced each install. Beta testing through TestFlight and Google Play internal testing tracks before public launch. The detailed checklist with sample deliverables is in Mobile app launch checklist.
Healthy push notification categories for DTC.
Five categories of healthy push: order updates, restock alerts, subscription renewals, price drops, and brand moments tied to launches. Avoid generic broadcasts more than once per week — that drives opt-out and tanks the long-term value of the channel. Healthy 90-day push opt-in retention runs 60 to 75 percent.
Order updates. Shipped, out for delivery, delivered. High engagement, low opt-out, expected by users. Always link directly to the order tracking screen via deep link.
Restock alerts. Customer indicated interest (via wishlist, watch button, or back-in-stock signup) and the product is now available. High intent, high conversion — typical conversion rates 15 to 25 percent on a restock notification, dramatically higher than any other push category.
Subscription renewals. One to three days before charge, friendly reminder with skip / pause / modify links. Reduces involuntary churn substantially — the customers who would have churned without the reminder still churn, but the customers who forgot they were on subscription get the chance to confirm continuation rather than experiencing it as a surprise charge.
Price drops. Items in cart or wishlist that have dropped below the threshold the customer set or below the price at which they viewed. Strong commercial signal; conversion rates 8 to 15 percent typical.
Brand moments. New launches, limited drops, exclusive collections. Cadence-controlled — once or twice per month maximum. Building anticipation through scarcity rather than overwhelming with broadcasts. The full healthy-push playbook including cadence rules and segmentation is in Push notifications ecommerce guide.
Six answers.
Does my Shopify store need a mobile app?
Probably not below USD 5M annual revenue. The math: a mobile app makes economic sense when you have a customer base that purchases multiple times per year and engages with the brand outside of purchase moments — content, community, loyalty, exclusive launches. Below USD 5M revenue, the customer base is usually too small for the app's per-user retention lift to justify the build cost (USD 30K to 200K) plus ongoing maintenance (USD 1K to 5K per month). Above that, the app becomes a retention multiplier — repeat purchase rates 30 to 60 percent higher than mobile web for matched customer cohorts.
Should I build native or hybrid?
Native (separate iOS and Android codebases in Swift / Kotlin) when the app needs deep platform integration — Apple Wallet, HealthKit, hardware sensors, advanced AR, near-perfect performance on platform-specific UI patterns. Hybrid via React Native or Flutter (single codebase compiled to both platforms) when you want time-to-market and cost efficiency, the app is mostly content and commerce, and platform-specific differentiation is not the value proposition. For 80 percent of Shopify-store apps, hybrid wins — React Native and Flutter both produce production-quality apps at half the cost of native.
Should I use a Shopify mobile app builder or commission custom?
Builder (Tapcart, Vajro, Shopney) when scope is standard ecommerce — product catalog, cart, checkout, push notifications, basic loyalty. Cost USD 200 to 1,500 per month depending on tier and customization. Custom when you need brand-specific UX, custom workflows the builder cannot represent (configurators, B2B portal, content-heavy experience), or unusual data integrations. Cost USD 30K to 200K to build plus maintenance. Most brands at the right size benefit from starting with a builder and graduating to custom only when the builder's constraints become genuinely costly.
What is in a mobile app launch checklist?
Twelve items. App Store Optimization assets (icon, screenshots, description, keyword research). Apple App Store Connect and Google Play Console accounts set up. App Review submissions (two to four weeks for Apple, one to three days for Google). Crash reporting (Firebase Crashlytics or Sentry). Analytics (Firebase Analytics or Amplitude). Push notification provider configured (APNs for iOS, FCM for Android). Deep link strategy mapping web URLs to app screens. ASO keyword research per market. Pre-launch beta testing through TestFlight and Google Play internal testing. Day-1 install attribution wired (Branch, Adjust, AppsFlyer, or Firebase Dynamic Links). Post-launch retention monitoring. App version update strategy.
How should DTC brands use push notifications?
Five categories of healthy push: order updates (shipped, out for delivery, delivered) — high engagement, low opt-out; restock alerts on watched products — high intent, high conversion; subscription renewals one to three days before charge — reduces involuntary churn; price drops on items in cart or wishlist — strong commercial signal; brand moments tied to launches or limited drops — cadence-controlled. Avoid: generic promotional broadcasts more than once per week (drives opt-out), notifications without deep links to specific screens (lower conversion), and any push that does not respect the user's stated preferences. Healthy push opt-in retention runs 60 to 75 percent at 90 days; below 50 percent means you are notifying too aggressively.
What is the ROI window for a mobile app investment?
12 to 24 months for hybrid builds at scale, 18 to 36 months for native. The math: a USD 50K hybrid build at 1,000 active app users converting 30 to 60 percent better than mobile web on a USD 100 monthly LTV produces USD 30K to 60K annual incremental revenue from the app cohort alone. That recovers build cost in 12 to 18 months and continues compounding. Below 1,000 active app users, the math does not work. The threshold for considering an app: 5,000 monthly active mobile customers and a brand with retention metrics at or above category benchmark.
Hybrid by default. Native when it matters.
More from Ezra.
Senior Brand Designer · APAC · Sydney · 2 posts on the site
Published .