There's a number most ecommerce founders can recite from memory: roughly three out of four visits to their store come from a phone.
There's a second number far fewer of them look at: what share of revenue those phone visits actually produce.
That gap (big traffic, smaller revenue) is the single most expensive unresolved problem in online retail right now. Industry data puts mobile at around 75-78% of ecommerce traffic but only about 60% of revenue. You are paying full price to acquire mobile shoppers and then handing them an experience that converts at roughly half the rate of desktop.
Most brands respond by optimising the mobile site harder. Faster theme, sticky add-to-cart, Apple Pay at checkout. All worth doing. But there's a structural limit to how much a browser tab can be improved, and there's a reason the brands pulling away from the pack stopped trying to fix the browser and built somewhere else entirely.
This piece makes the case for a branded mobile app, with the real numbers, the counterarguments, and a framework for deciding whether it's your move right now or a distraction.
Key Takeaways
- ✓ Mobile drives 75-78% of ecommerce traffic but only ~60% of revenue — a structural gap a branded app can close.
- ✓ App users convert roughly 2x better than mobile web users, with 20-30% higher average order values.
- ✓ Push notifications are the only free owned channel with zero marginal cost per message after opt-in.
- ✓ App users show 2.8x-5x higher customer lifetime value — retention, not conversion, is the real argument.
- ✓ The realistic ROI threshold is ~$500K in annual online revenue with a natural repeat-purchase cycle.
- ✓ Your website is the acquisition layer. Your app is the retention layer. They do different jobs.
Quick Answer
A branded mobile app is a retention asset, not a replacement for your website. For ecommerce brands above roughly $500K in annual online revenue with a natural repeat-purchase cycle, a well-built app converts engaged mobile shoppers roughly 2x better than mobile web, delivers push notifications at zero marginal cost, and generates 2.8x-5x higher customer lifetime value. Below that threshold, fix mobile site speed and checkout first. The app is the second move, not the first.
1. The Behavioural Fact Underneath Everything
Start with where attention actually goes.
Sensor Tower's State of Mobile 2026 reporting puts browser and search usage at under 6% of total smartphone time. The other 90%+ sits inside apps. This isn't a marginal preference. That's how the device is used.
So when your entire mobile strategy lives in a browser, you're competing for a sliver of screen time against everything else a person does on their phone. You're a bookmark in a stack of thirty tabs, or a link in an email they'll open a median of six hours later.
The engagement numbers follow directly. Comparative data across ecommerce puts time-in-app at roughly 200 minutes per month versus around 11 minutes on mobile web. Criteo's long-running research found app users viewing dramatically more products per session. One dataset puts it at 9.15 minutes per app session versus 1.26 minutes on the mobile site.
That's not a UX difference. That's a different relationship with the customer.
2. Conversion: The Real Number, Not the Marketing Number
You will see "apps convert 3x better than mobile web" repeated everywhere. It deserves scrutiny, because the honest version is more useful than the inflated one.
Where the 3x comes from. The figure traces to Criteo's Global Commerce Review, which compared thousands of retailers across dozens of countries. The catch is methodological: Criteo measured conversion as buyers divided by product-page viewers, not buyers divided by sessions. That definition inflates the ratio, because app users arrive with higher intent in the first place.
What session-based comparisons show. More recent same-brand data lands lower and is more trustworthy. Tapcart, which has every incentive to publish the biggest number available, now cites a 2.3x in-app conversion advantage, revised down from an earlier 3.2x claim. Poq's platform data across 21 brands with both app and mobile-web analytics for the same period found a median conversion lift of 1.8x.
The honest framing: a well-built app converts your engaged mobile shoppers roughly 2x better than mobile web. Not 3x, not magic. But 2x on your most valuable segment is an enormous number, and it compounds with everything in the next section.
Alongside conversion, two secondary effects show up consistently:
- Average order value runs 20-30% higher in-app across most reported datasets, driven by saved payment details, personalised merchandising, and lower friction on add-to-cart.
- Cart completion improves materially. Mobile web abandonment sits around 80-86% versus roughly 69% on desktop. Apps close a meaningful chunk of that gap by eliminating the two biggest structural causes: repeated logins and checkout forms built for a mouse.
3. The Actual Reason to Build One: Retention
If conversion were the whole argument, an app would be a nice-to-have. Retention is what makes it a strategic asset.
The retention data is the most consistent finding across every source:
| Metric | App users vs web-only |
|---|---|
| Purchase frequency | ~33% more often |
| Customers making a repeat purchase | ~60% vs ~40% |
| Customer lifetime value | 2.8x-5x higher |
| Repeat purchase rate (brands with apps) | Up to 50% higher |
MobiLoud's benchmark data finds that 60% of first-time app buyers make at least one additional purchase. Set that against the industry baseline: average ecommerce retention hovers around 30%, with repeat purchase rates typically between 15% and 30%.
Why this matters more than conversion: customer acquisition costs have risen roughly 60% over the last five years, and the classic Reichheld and Sasser finding (a 5% improvement in retention driving 25-95% profit gains) has only become more relevant as paid acquisition gets more expensive. A 10-point improvement in repeat purchase rate typically corresponds to a 25-40% increase in average CLV, because the customer who buys a second time is disproportionately likely to buy a third and fourth.
An app doesn't win you new customers. It stops you losing the ones you already paid for.
4. Push Notifications: The Only Free Owned Channel Left
This is the specific mechanism behind the retention numbers, and it deserves its own section because it's the feature that structurally cannot be replicated on the web.
Consider what you're currently working with:
- Email. Inboxes are saturated. Ecommerce open rates sit around 21%, and Apple's Mail Privacy Protection has made even that number unreliable. Median time-to-open is roughly 6.4 hours.
- SMS. Excellent engagement, but every single message carries a per-send cost that scales linearly with your list. That's fine for 5,000 high-value carts; it's brutal at volume.
- Paid retargeting. You're renting access to your own customers, at rates set by an auction you don't control.
Push notifications sit outside all three constraints. They arrive on the lock screen in seconds, there's no algorithm gatekeeping delivery, no spam folder, and after opt-in there's zero marginal cost per message.
The performance data:
- Push open rates typically run 45-60% against 20-25% for email.
- Cart-abandonment pushes sent within the first hour recover roughly 14% of abandoned sessions, a rate that collapses to single digits if you wait longer.
- Automated cart-recovery pushes average around 5% click-through, well above any broadcast campaign.
- Dormant users are reportedly 88% more likely to re-engage from a well-targeted reactivation push than from an email or in-app message alone.
- Behaviourally-triggered pushes have hit CTRs above 10% versus under 1% for basic demographic blasts.
For most mid-sized stores, the abandoned-cart push flow alone covers the cost of running the app. Everything else is upside: back-in-stock alerts, drop announcements, replenishment reminders, order tracking.
One caveat worth internalising: push is a privilege, not an entitlement. The consensus cadence is 2-3 promotional pushes per week maximum, with behavioural triggers spaced out. Over-messaging is the fastest way to convert a hard-won install into an uninstall.
5. Speed, and Why It's Not a Small Thing
Native apps store assets locally, pre-load content, and don't renegotiate a connection every time someone taps a category. Well-built retail apps load product pages in under a second against 3-5 seconds for mobile web.
The conversion sensitivity here is well documented and slightly absurd:
- Google's retail research found a 0.1-second improvement in load time lifted conversion by 8.4% and add-to-cart by 9.1%.
- Each additional second of delay costs roughly 7% in conversion.
- 53% of mobile visitors abandon a page taking longer than three seconds.
- At a 2-second load, mobile shoppers view about 8.9 pages per session. At 8 seconds, that drops to 3.3.
An app doesn't just make the store faster. It removes the entire class of problems that come from being at the mercy of browser engines, patchy networks, and tab clutter.
6. Home Screen Real Estate and the Discovery Loop
There's a qualitative argument that the metrics understate.
A website requires intent. Someone has to decide to visit you, then type, search, or click through. Your app icon sits on the home screen next to WhatsApp and the banking app, visible dozens of times a day. That passive presence generates spontaneous browsing sessions that would simply never have happened.
Data on in-store behaviour makes the point sharply: around 74% of consumers report using a retailer's app while physically inside a store. Your app isn't just an online channel. It's a presence in moments you'd otherwise have no access to.
7. First-Party Data, in a World That Keeps Restricting It
Third-party cookies are functionally dead. Apple's App Tracking Transparency has stabilised at roughly 29% opt-in globally, and iOS CPMs have compressed around 24% relative to Android since 2021 as attribution accuracy degraded. In the EU, cookie consent rates average about 62%, meaning nearly 40% of behavioural data is invisible without server-side infrastructure.
An app inverts this. Logged-in users, deterministic identity, complete behavioural history, first-party by construction. You know what someone browsed, what they abandoned, what they returned, and when they're due to reorder, without renting that knowledge from an ad platform.
For personalisation this is decisive. Personalised recommendations drive around 31% of ecommerce revenue, and 71% of customers now expect personalised experiences as a baseline. You can't personalise well for a user you can't identify.
8. This Is Not Website Versus App
The framing that trips up most brands is treating this as a replacement decision. It isn't. The two channels do different jobs, and running both is the point.
Your website is the acquisition layer. It absorbs search traffic, catches paid clicks, converts strangers, and stays open to anyone who's never heard of you. Nobody installs an app for a brand they encountered ninety seconds ago. Your site has to carry the entire top of the funnel, and it must stay fast and well-optimised regardless of what else you build.
Your app is the retention layer. It exists for people who have already bought once, the cohort where a 2x conversion lift and a 33% frequency increase actually compound into something. Trying to acquire customers through the app store is the fastest way to waste money on this project.
The practical sequence follows from that split:
- Acquire broadly through the website, social, and paid.
- Convert the first purchase there, with a mobile checkout that doesn't leak.
- Ask for the install at the highest-intent moment, right after that first order lands.
- Move retention, replenishment, and loyalty into the app, where the marginal cost of reaching someone is zero.
Brands that report the strongest results consistently describe this shape: a modest share of customers in the app, generating a wildly disproportionate share of repeat revenue. One reported split has app users driving 62% of total revenue from around 16% of traffic. That ratio isn't a fluke. It's what happens when you concentrate your best customers into your best channel.
A useful sanity check: if your app and your website look like the same store doing the same job, you've built an expensive duplicate rather than a second channel.
9. The Honest Counterargument: When You Should NOT Build an App
Any article that only argues one side isn't worth trusting. Here's what the app-builder marketing pages leave out.
Installs are brutally hard to retain. Around 49% of apps are uninstalled within 30 days. Day-30 retention for shopping apps sits at roughly 4%. If you build an app expecting it to acquire customers, you will burn money.
The attribution is partly an illusion. App users show 3-5x higher lifetime value, but who installs a brand's app? Your existing best customers. Some of that "app lift" is selection effect, not causation. The app amplifies loyalty that already existed; it rarely creates it from nothing. Any ROI model that assumes every app user's entire value is app-attributable is lying to you.
It's a second storefront to run. Unless you use a mirroring platform, you now have app-specific merchandising, app-specific promotions, OS updates, app store reviews, and two places for things to drift out of sync.
Your product category may not support it. Apps earn their keep on repeat purchases. Consumables, beauty, supplements, pet supplies, fashion, groceries: strong fit. A mattress brand, a furniture retailer, anything with a multi-year purchase cycle: much weaker. If your customer's natural repurchase interval is 18 months, push notifications have nothing useful to say.
Below a certain volume, the maths doesn't work. If you're doing under roughly $30-50K/month online, your effort is almost certainly better spent on mobile site speed, checkout optimisation, and email flows. Those have shorter payback periods and no ongoing platform fee.
The realistic threshold: most practitioners put positive ROI at somewhere above $500K in annual online revenue, with the sweet spot being brands where mobile is dominant and repeat purchase is natural. Below that, fix the mobile web first.
10. Running the Numbers on Your Own Store
Here's a framework rather than a promise. Plug in your actuals.
Take a store doing $1.2M in annual online revenue, 75% mobile traffic.
- Identify the migratable cohort. Realistically, 10-15% of your customer base will install and use the app in year one, and it'll be your most engaged decile. Say those customers currently generate 25% of revenue: $300K.
- Apply a conservative lift. Not the 3x headline. Assume a 20-25% blended increase in revenue from that cohort, from higher conversion, higher AOV, and more frequent purchase. That's $60-75K incremental.
- Subtract the honest discount. Assume a third of that would have happened anyway through email and organic repeat behaviour. Call the true incremental $40-50K.
- Subtract cost. A managed builder at $500/month is $6K/year, plus perhaps $2-3K setup and some internal time. Call it $12K all-in for year one.
- Net: roughly $30-40K, with a payback period commonly quoted at 30-60 days for stores above $500K/year, and 10-16 months for those making heavier custom investments.
Run this with your own retention curve and repeat rate. If step 1 gives you a small number because you have few repeat customers, that's your answer: fix retention fundamentals before you build a retention channel.
11. How to Actually Build It: Three Paths
| Path | Cost | Timeline | Best for |
|---|---|---|---|
| No-code builders (Tapcart, Vajro, MageNative, Shopney, Plobal, AppMaker) | $49-$999/month, some with 1.75-2.5% success fees on in-app orders | Days to 2 weeks | Validating the channel; sub-$1M brands |
| Managed platforms (MobiLoud, Appbrew, VennApps, Poq) | ~$300-$1,500+/month plus setup | 2-6 weeks | Mid-market brands wanting native quality without internal dev |
| Custom build (React Native / Flutter) | $20K-$50K basic; $50K-$200K+ full-featured | 2-6 months | Complex logic, ERP integrations, non-standard platforms |
Two practical notes. Cross-platform frameworks cut cost roughly 30-40% versus building separate native apps, with negligible performance difference for a shopping app. And watch the contract terms on the popular builders: 12-month lock-ins and revenue-share fees are common, and the success fees can quietly become your largest line item as the channel grows.
Do not over-buy or under-buy. A pre-revenue store doesn't need an enterprise platform. A brand doing $5M shouldn't be fighting a template tool that caps its roadmap.
12. What Separates Apps That Work from Apps That Die
The install is not the win. Here's what the top-quartile apps do that the median ones don't.
AGet the Fundamentals Right First
- Guest checkout and one-tap payment (Apple Pay, Google Pay, Shop Pay). One-tap checkout is reported to lift mobile conversion 30-50%.
- Smart search and order tracking. Tracking alone measurably reduces support tickets.
- Reviews surfaced in-app. 93% of consumers read reviews before buying.
BBuild the Retention Engine
- A personalised home feed driven by browse and purchase history. A static feed forces navigation; a personalised feed sells before the user decides to look.
- Cohort-based push strategy. Different cadence for new users (a 4-5 touch welcome series in week one), engaged buyers (restocks and drops, 2-3 per week), and lapsed users (win-back sequences). Sending everyone the same push is the single most common failure.
- A cart recovery sequence, not a single message. The pattern that works: a neutral reminder at 30 minutes, scarcity or social proof at 24 hours, an incentive at 72 hours. Leading with a discount trains customers to abandon deliberately.
- App-exclusive value. Early access to drops, app-only pricing, loyalty points, members-only content. Without a reason to install, nobody installs.
CSolve the Install Problem Deliberately
Don't expect the app store to send you customers. Drive installs from where your customers already are: an in-cart banner on your mobile site, a QR code on packaging and inserts, a post-purchase email, and a call-out in your order confirmation. The single highest-intent moment to ask for an install is immediately after someone's first purchase.
DConsider AR Where It Fits
Retailers offering AR try-on or room placement report roughly 65% higher conversion among users who engage with it and around 40% lower return rates. Fashion, beauty, eyewear, and furniture see the strongest results.
13. The Metrics That Tell You If It's Working
Ignore downloads. Track these:
| Metric | What It Tells You |
|---|---|
| App revenue as a share of total online revenue | Available cleanly as a separate sales channel in most platforms |
| Repeat purchase rate: app users vs web-only | Measured by acquisition cohort |
| D1 / D7 / D30 retention | Tells you whether onboarding works |
| Revenue per push & recovered cart revenue | Direct channel ROI signal |
| Stickiness (DAU ÷ MAU) | How often monthly users return daily |
| CLV:CAC ratio for app-acquired cohorts | 3:1 is the sustainability floor |
Compare yourself against your own trend line, not against industry medians. Published benchmarks skew heavily toward high-volume senders in ecommerce, news, and gaming.
30-Minute Decision Audit
- 1Minutes 1-5: Pull your mobile traffic share and mobile revenue share from analytics. Calculate the gap.
- 2Minutes 6-10: Check your repeat purchase rate. What % of customers buy a second time within 90 days?
- 3Minutes 11-15: Identify your product category's natural repurchase interval. Is it weeks or years?
- 4Minutes 16-20: Run the ROI framework from Section 10 with your actual revenue and retention numbers.
- 5Minutes 21-25: Audit your current mobile checkout. How many taps from product page to confirmation?
- 6Minutes 26-30: Choose a path from Section 11 that matches your current revenue stage and internal capacity.
Final Checklist
- ☐ Mobile traffic share and mobile revenue share gap identified
- ☐ Repeat purchase rate above 30% (minimum viable app candidate)
- ☐ Annual online revenue above $500K threshold
- ☐ Product category has a natural repeat-purchase cycle (weeks, not years)
- ☐ Mobile site speed and checkout already optimised before building the app
- ☐ ROI framework run with actual store numbers (Section 10)
- ☐ App platform chosen to match revenue stage (no-code vs managed vs custom)
- ☐ Install strategy planned (post-purchase email, packaging QR, in-cart banner)
- ☐ Push notification cadence defined (max 2-3 promotional per week)
- ☐ Cart recovery sequence built (30-min reminder → 24-hr social proof → 72-hr incentive)
- ☐ App-exclusive value defined (early access, loyalty, app-only pricing)
- ☐ Six core metrics tracked (app revenue share, repeat rate, D30 retention, revenue per push, stickiness, CLV:CAC)
Frequently Asked Questions
Do apps really convert 3x better than mobile web?
The 3x figure comes from Criteo's methodology, which measures buyers per product-page viewer rather than buyers per session. More recent same-brand data puts the honest lift at roughly 2x. That's still an enormous number on your most valuable mobile segment, but any ROI model built on 3x is overstating the case.
What's the minimum revenue to justify building a mobile app?
Most practitioners put the positive ROI threshold at around $500K in annual online revenue, with the sweet spot being brands where mobile is dominant and repeat purchase is natural. Below that, the effort is almost certainly better spent on mobile site speed, checkout optimisation, and email flows.
Should I build a native app or use a no-code builder?
For most Shopify brands under $1M, a no-code builder (Tapcart, Vajro, Shopney) is the right starting point. It validates the channel at low cost and low risk. Move to a managed platform or custom build only when you've proven the channel generates meaningful repeat revenue and your roadmap outgrows the template tool.
How do I get customers to actually install the app?
Don't rely on the app store. Drive installs from where your customers already are: an in-cart banner on your mobile site, a QR code on packaging and inserts, a post-purchase email, and a call-out in your order confirmation. The single highest-intent moment is immediately after someone's first purchase.
How many push notifications should I send per week?
The consensus cadence is 2-3 promotional pushes per week maximum, with behavioural triggers (cart abandonment, back-in-stock, replenishment) spaced separately. Over-messaging is the fastest way to convert a hard-won install into an uninstall.
The Bottom Line
A mobile app is not a mobile version of your website. It's a different asset with a different job.
Your website is a discovery machine: it catches search traffic, absorbs paid clicks, handles the first transaction from a stranger. Your app is a retention machine: it takes the customers you've already paid dearly to acquire and dramatically increases the odds they come back, buy more often, and spend more when they do.
The brands winning mobile in 2026 aren't the ones with the best-optimised responsive theme. They're the ones who realised that after a certain point, the cheapest revenue available isn't a new customer at all. It's the second, third, and fourth order from someone who already trusts you. And the most reliable way to earn those orders is to occupy a permanent square of screen real estate on the device where your customers spend 90% of their time.
If mobile is most of your traffic, your customers buy more than once, and you're above roughly half a million in annual online revenue: you're not deciding whether to build an app. You're deciding how much longer to keep paying for that decision.
Sources and Further Reading
Data in this article is drawn from Sensor Tower's State of Mobile 2026, Criteo Global Commerce Review, Baymard Institute cart abandonment research, AppsFlyer benchmark reports, Poq platform data (Jan 2025 to Jan 2026), MobiLoud's ecommerce app benchmark reporting, Think with Google retail performance research, Klaviyo and Omnisend 2026 email benchmarks, eMarketer, and Statista.
Note: figures cited across industry sources use varying methodologies, particularly conversion rate definitions. Where sources disagreed, the more conservative and more recent session-based figures have been used.