Building a Shopify Mobile App in 2026: Builder or Custom?
Most Shopify merchants who ask about a mobile app are really asking two questions. Will an app make more money than my mobile site? And if yes, should I rent one from a monthly app builder or have one built? The answer to the first depends on your repeat customers. The answer to the second depends on how different you need the app to be.
We build and run our own Shopify products (Store Workers, StoreBlog, Rank Collections), have shipped a 150,000-SKU catalog engine, and build native iOS and Android apps on React Native and Expo. This guide covers both routes honestly, what drives cost, how push notifications and app store review work, and when a builder is the better buy.
Do you need an app at all?
An app pays off when customers come back often: consumables, replenishment, drops, subscriptions, or a loyal community that buys several times a year. For those stores, an icon on the home screen and push notifications are a direct channel you do not pay per click for.
If most of your customers buy once a year from an ad, an app will not change that. They will not install it, and the money is better spent on your mobile site's speed and checkout. Look at your repeat purchase rate and how many orders come from returning customers before you spend anything on an app.
Option 1: a monthly app builder
Several app builders exist that turn a Shopify store into an iOS and Android app for a monthly subscription. You pick a template, connect your store, arrange screens with a visual editor, and they handle builds and store submission. For many merchants this is a sensible choice.
What you get is speed and low upfront cost. What you accept is the builder's limits: their screen types, their integrations, their roadmap, and a subscription that continues as long as the app exists. If you stop paying, the app usually goes away.
A builder is enough when your app is essentially your store in app form: browse, search, cart, checkout, account, and push campaigns. If that describes your plan, try a builder first and come back to custom only if you outgrow it.
Option 2: a custom app on the Storefront API
A custom app is code you own, built for your store. We build with React Native and Expo, so one codebase ships to both iOS and Android. Products, collections, search, and cart come from the Shopify Storefront API. Customer login, order history, and addresses come from the Customer Account API. Checkout runs through Shopify's own checkout, so payments, discounts, and taxes behave exactly as they do on your site.
Custom pays off when the app needs things a template cannot do: a product configurator, a subscription management flow tied to your subscription app, a loyalty experience, store-specific content, gated drops, or integration with your own backend. It also pays off when you would rather pay once and own the code than pay monthly indefinitely.
Our price for a custom Shopify mobile app starts at $9,500, delivered in 4 to 6 weeks, including app store submission and push notifications. Care after launch is optional.
Want your own Shopify app?
Native iOS and Android on the Storefront API. From $9,500, 4 to 6 weeks.
What drives the cost of a custom app
The biggest cost driver is how far the app departs from a standard store. Browse, product page, cart, checkout handoff, and account are well-understood screens. Each custom flow on top (bundles, configurators, a custom loyalty screen) adds design, build, and test time.
The second driver is integrations. Every third-party app your store depends on (reviews, subscriptions, loyalty, search) needs its data in the mobile app, and each one has its own API quality. The third is content: whether merchandising screens are driven by Shopify data and metaobjects you already maintain, or need a new content setup.
Things that do not drive cost much: supporting both platforms (one codebase), and basic push notifications. Things people forget to budget for: the Apple Developer Program fee, the Google Play developer fee, and the time someone on your team spends answering reviewer questions during submission.
Push notifications that people do not turn off
Push is the main reason to have an app, and the fastest way to get uninstalled. On iOS, users must grant permission, so ask at a moment that makes sense (after a first order, or when they follow a product) rather than on first launch. Expo's notifications tooling handles the plumbing to Apple's and Google's push services.
Useful pushes are specific to the person: back in stock for something they viewed, shipping updates for their order, a drop they signed up for. Broadcast promotions every day will train people to disable notifications. We set up transactional and segmented pushes first, and campaigns second.
App store review: what to expect
Apple and Google both review apps before they go live, and Apple is the stricter of the two. Apple's guidelines push back on apps that are just a website wrapped in an app shell, so a store app should use native screens and offer things the website does not, such as push and saved account state. If your app lets people create an account, Apple also requires a way to delete the account from inside the app.
Plan for at least one round of reviewer questions. Common reasons for rejection include broken links, placeholder content, missing privacy details, and a login the reviewer cannot test. We prepare a demo account, privacy disclosures, and screenshots before submission so the first review has the best chance of passing.
Updates are easier once you are live. Content and product changes come from Shopify instantly, and many code fixes can ship as over-the-air updates through Expo without waiting for a full store review, within the stores' rules.
Builder or custom: a quick decision guide
Choose a builder if your app is your store in app form, you want to test whether customers install it before investing more, and a monthly subscription fits your margins.
Choose custom if you need flows a template cannot express, you depend on integrations a builder does not support, you want to own the code outright, or you have already outgrown a builder. Either way, measure installs, repeat orders from the app, and push opt-in rates for the first 90 days. Those three numbers tell you whether the app is earning its place.
Key takeaways
- An app pays off for stores with repeat buyers. For one-time buyers, improve the mobile site first.
- Monthly app builders are a sensible start when the app is your store in app form.
- A custom React Native and Expo app on the Storefront and Customer Account APIs fits custom flows, deep integrations, and code ownership.
- Ask for push permission at a meaningful moment and lead with personal, transactional pushes.
- Our custom Shopify mobile app starts at $9,500, in 4 to 6 weeks, including store submission.
Frequently asked questions
Yes. We hand off to Shopify's checkout, so payments, discounts, shipping rates, and taxes match your online store.
It varies. Often a day or two, sometimes longer if the reviewer has questions. We build buffer for at least one round of questions into the 4 to 6 week timeline.
Yes. Your products, customers, and orders live in Shopify, not the builder, so a custom app reads the same data. Plan the switch so existing users get the new app as an update under the same store listing where possible.
No, care is optional. Apps do need occasional updates for new iOS and Android versions, so either we handle it or we hand over the code and build setup to your developer.
The 15-Day AI MVP Playbook
Day-by-day plan, a starter CLAUDE.md, the Lovable-to-production checklist, eval and cost worksheets, and 10 prompts. Pure value, no pitch.
Book 20 minutes, or send a brief
A former CTO replies. You leave with a written plan and a fixed estimate.
Prefer LinkedIn? Connect with Harish.