In short
- Mobile web is the acquisition layer, the app is the retention layer. Treating them as competitors is the most expensive framing mistake a D2C brand can make.
- App store commissions mostly do not apply to physical goods. Apple and Google both direct sellers of real world products to use standard payment methods, so the 15% to 30% fee panic is largely misplaced for apparel, beauty, home and food brands.
- The real app cost is installs and maintenance, not commission. Paid install costs, two platform release cycles, SDK upkeep and a permanent QA surface are the recurring bill.
- Repeat purchase frequency is the only number that justifies an app. If your customer does not come back at least a few times a year on their own, an app is a very expensive loyalty card.
- Progressive web apps close part of the gap but not all of it. Home screen presence and offline caching are solved; deep hardware access, reliable iOS push behavior and app store discovery are still weaker.
Why the app versus mobile web question got harder in 2026
For most of the last decade the answer was easy in a bad way. Every D2C brand that raised money was told to ship an app, because apps signaled maturity and because a slide showing app revenue looked better than a slide showing browser sessions. The question was never really about customers.
Three things changed that. First, paid acquisition stopped being cheap, which made the fully loaded cost of an app install impossible to hide inside a growth budget. Second, mobile browsers got substantially better, closing much of the performance and capability gap that justified native builds in 2016. Third, Apple’s App Tracking Transparency framework, introduced in 2021, weakened exactly the attribution loop that made app install campaigns look efficient in the first place.
The result is that the honest answer in 2026 is conditional. Some D2C categories genuinely earn an app. Most do not, and the ones that do usually earn it later than they think. Understanding where your brand sits requires separating four things that get blurred together constantly: acquisition, conversion, retention and margin.
It also helps to keep the base rates in view. According to US Census Bureau quarterly estimates, e-commerce accounts for a mid-teens percentage share of total US retail sales, and that figure moves each quarter, so check the current release rather than a number quoted in a blog post. Within that e-commerce slice, mobile devices carry the majority of sessions for most consumer brands while typically converting at a lower rate than desktop. That gap is the entire commercial argument, and it is worth reading alongside our breakdown of mobile commerce conversion, which covers where those sessions leak.
None of this is unique to D2C, and the channel logic underneath it is the same logic that governs where you sell at all. Our complete guide to selling on global e-commerce marketplaces works through the same tradeoff at portfolio level: owned surfaces give you margin and data, borrowed surfaces give you reach.
Key terms and definitions
The debate gets muddy because people use three words for at least five different things. Pinning the vocabulary down first removes about half the disagreement in any internal meeting on this.
Native app
A native app is software written for a specific platform, distributed through the Apple App Store or Google Play, installed on the device and updated through a store release cycle. It gets the deepest access to device hardware: camera, biometrics, secure payment sheets, background processing and the platform’s own push notification service. It also inherits the platform’s rules, review process and release latency.
Mobile web
Mobile web is your storefront rendered in Safari, Chrome or an in-app browser. There is nothing to install, the URL is shareable, search engines can index it, and you ship changes the moment you deploy. It is the only surface that can receive a click from an ad, a search result, a creator’s link in bio or a text message without friction.
Progressive web app (PWA)
A progressive web app is a mobile website that adds an installable manifest and a service worker, which lets it sit on the home screen, launch without browser chrome and cache assets for offline or flaky network use. It is web technology wearing an app costume. Support has improved substantially on both major platforms, though push notification behavior on iOS remains more constrained and more easily broken by user settings than on Android.
Hybrid and wrapper apps
A hybrid app packages web views inside a native shell, often built with React Native, Flutter or a commercial wrapper platform. It ships to the app stores and can access some native capabilities, while reusing much of the web codebase. This is where most mid-size D2C brands actually land, and it is a reasonable compromise, provided nobody pretends it delivers native-grade performance on older devices.
In-app purchase versus standard payment
In-app purchase (IAP) is the platform’s own billing system, which carries a commission. Standard payment means your normal checkout and your normal payment processor. The distinction matters enormously and is the single most misunderstood point in this entire discussion, which the next section addresses directly.
How the economics actually work
Start with the fee question, because it dominates the conversation and is usually wrong.
The commission argument is mostly a myth for physical goods
Both Apple and Google’s published developer guidelines direct apps selling physical goods and real world services to use payment methods other than the platform’s in-app purchase system. A sweater, a jar of moisturizer, a meal kit or a piece of furniture is a physical good. That means the headline commission rates that dominate app store discourse, generally cited as 30% standard and 15% under the small business programs, do not apply to a typical D2C retail transaction. Rates, thresholds and eligibility rules change, so confirm the current terms in Apple’s and Google’s own developer documentation rather than relying on secondhand figures.
Where commission genuinely bites is digital goods and subscriptions delivered inside the app: a paid membership tier, unlocked content, a digital styling service. Brands selling those should model the fee carefully. Brands shipping boxes should stop citing it as a reason to avoid apps, because it is not their bill.
The regulatory picture around these rules has been moving. In the United States, a federal court ruling in the long-running Epic Games litigation resulted in an injunction that expanded developers’ ability to link customers to external purchase options, and in the European Union the Digital Markets Act imposed a separate set of obligations on designated gatekeeper platforms. Both remain subject to appeals, revisions and evolving compliance terms. Treat any specific entitlement as something to verify with the platform’s current developer terms and, where the stakes are material, with your own counsel. This article is general information for commercial planning, not legal advice.
The real cost is installs, and it compounds
The genuine expense of an app strategy is getting it onto phones. Every install is a conversion event with its own cost, and unlike a web session, an uninstall is silent and permanent until you pay again. Reported cost per install for retail and shopping apps in the US varies widely by category, targeting and season, and it climbs during Q4 alongside every other auction. Model your own number from your own campaigns; industry averages are close to useless at brand level.
Then add the maintenance line that rarely appears in the business case: two platform release cycles, annual OS updates that break things, SDK version churn, store review delays at the worst possible moment, crash monitoring, and a QA matrix that now includes device models as well as browsers.
Retention is where the math flips
Apps win on repeat behavior. A customer with your icon on their home screen has a zero-friction path back, a stored payment method, a saved size profile and a notification channel you do not rent from anyone. For brands with genuine repeat frequency, the lifetime value difference is real and consistently observed across the category.
The trap is that this advantage is conditional on frequency you already have. An app does not create repeat purchase behavior in a category that lacks it. It amplifies repeat purchase behavior that already exists. A skincare brand whose customers reorder every eight weeks has something to amplify. A brand selling one mattress per household per decade does not, and no amount of push notification strategy will change that.
Side by side cost and return profile
| Dimension | Mobile web | Progressive web app | Native or hybrid app |
|---|---|---|---|
| Cost to reach a new customer | Lowest: a click is the whole funnel | Lowest, same as mobile web | Highest: paid install plus first-session drop-off |
| Build cost | Already paid, part of the storefront | Incremental on top of existing site | Substantial, plus ongoing platform maintenance |
| Commission on physical goods | None | None | None under current published guidelines, verify at source |
| Commission on digital goods and subscriptions | None | None | Applies, rates vary by program |
| Repeat purchase rate | Baseline | Modest lift from home screen presence | Highest for genuinely frequent categories |
| Time to ship a change | Minutes | Minutes | Days, subject to store review |
| Discoverability | Search, social, ads, links, all of it | Same as mobile web | App store search plus whatever you drive |
| Data and identity quality | Weaker post-ATT, cookie constrained | Similar to mobile web | Strongest: logged-in by default, durable identity |
What each channel is genuinely good at
Strip the strategy language away and each surface has a short list of things it does better than the alternative. Building around those lists produces better decisions than debating the abstract question.
Mobile web wins on reach and first contact
Every acquisition channel a D2C brand uses terminates in a browser. Paid social, creator links, search results, email, SMS, QR codes on packaging, a friend forwarding a product page. None of those can hand a customer directly into an installed app without an install step in between, and each step costs conversion.
Mobile web also carries the entire organic discovery layer. Your product pages are indexable, your content is citable by AI assistants and search engines, and your URLs work when pasted anywhere. That is not a small advantage; it is the foundation of low-cost growth for brands that cannot outspend their competitors.
Apps win on frequency, identity and merchandising control
Inside an app the customer is logged in by default. That single fact fixes a long list of problems: order history is present, sizes are remembered, payment is stored, returns are self-service, and the identity persists across sessions in a way that browser storage increasingly does not. For a brand trying to build durable first-party data, this matters, and it connects directly to how D2C brands earn first-party data without resorting to intrusive tactics.
Apps also give you a merchandising canvas nobody else controls. No competitor ad sits next to your product. No algorithm decides which of your collections gets seen. For brands with a strong editorial or community component, that control has real value.
Push notifications: the asset and the liability
Push is the most cited reason to build an app and the most abused capability once one exists. It is a genuinely valuable channel: delivery is immediate, it does not compete with an inbox, and it can be triggered by behavior rather than a calendar.
It is also the fastest route to an uninstall. Opt-in rates differ substantially between iOS, where the user must actively grant permission, and Android, and both platforms make it trivially easy to mute an app permanently. The brands that keep push working treat it as a scarce resource: shipping updates, back in stock alerts on items the customer actually saved, and replenishment reminders timed to real consumption cycles. The brands that lose it send a promotion every Thursday.
Capability comparison
| Capability | Mobile web | PWA | Native app |
|---|---|---|---|
| Home screen icon | No | Yes | Yes |
| Push notifications | Limited | Supported, weaker and more fragile on iOS | Full, both platforms |
| Offline browsing | No | Yes, cached content | Yes |
| Camera, AR try-on, biometrics | Partial | Partial | Full |
| Apple Pay and Google Pay at checkout | Yes | Yes | Yes |
| Persistent login | Fragile, storage limits apply | Better | Durable |
| Indexable by search engines | Yes | Yes | Partially, via app indexing |
| Shareable link to any product | Yes | Yes | Requires deep link setup |
| Update without approval | Yes | Yes | No |
A threshold test for whether you have earned an app
Rather than arguing from principle, run four checks. If you fail any of the first three, the answer is almost certainly to keep investing in mobile web.
Check one: purchase frequency
Look at your twelve month repeat rate among customers who bought at least once. If a meaningful share of your customer base buys three or more times a year without being prompted by a discount, you have the frequency an app amplifies. If your repeat rate is thin and discount-dependent, an app will produce a small cohort of enthusiasts and a large pile of maintenance.
Check two: base of existing customers
Apps are not an acquisition channel for D2C brands; they are a retention channel that you seed from your existing base. If your customer list is small, there is simply not enough installed base to make the fixed cost work. The usual failure mode is launching an app, converting a few thousand of your best customers, and then paying to maintain infrastructure for a group you could have reached by email.
Check three: mobile web is already good
This is the check most often skipped. If your mobile site loads slowly, your checkout takes six screens, and your search returns poor results, an app will not fix any of it, because the app will be built on the same commerce backend by the same team. Fix the web experience first. The improvement applies to one hundred percent of your traffic instead of the fraction that installs.
Check four: is there a capability you genuinely need
Some categories have a real native requirement: augmented reality try-on for eyewear and cosmetics, in-store scanning and mode switching for brands with physical retail, loyalty wallet integration, or a service component that runs in the background. If you have one of these, the app case strengthens considerably. If your list of native features is “push notifications and a nicer feel”, you do not have one.
Common mistakes and how to avoid them
The failure patterns in this space are remarkably consistent across brands and years.
Building the app to fix a conversion problem. Conversion problems live in page speed, checkout length, payment options, shipping cost transparency and product information. An app inherits all of them. Diagnose the leak before changing the container.
Paying for installs from cold audiences. An install from someone who has never bought from you is an expensive way to acquire a probable uninstall. Seed the app from purchasers, email subscribers and packaging inserts, where the cost per install is a fraction of paid media and the retention is far better.
Interstitials that block the mobile site. The full-screen “open in app” overlay that appears before a customer can see a product is a conversion tax paid by every visitor to benefit a minority. Search engines have historically penalized intrusive interstitials on mobile, and customers dislike them regardless of ranking impact. Use a dismissible banner, and only for logged-in returning customers.
Splitting the team. When app and web are owned by different groups with different roadmaps, the experiences diverge, promotions get out of sync, and a customer who sees a price in one place and a different price in the other loses trust. One merchandising source of truth, two presentation layers.
Letting the app rot. An app with a two-star rating full of crash complaints damages the brand more than having no app at all. If you cannot commit to a maintenance cadence for several years, do not start.
Ignoring the PWA middle path. Many brands jump from mobile web straight to a native build without testing whether a progressive web app captures most of the retention benefit at a small fraction of the cost. It frequently does, especially for brands whose customers are majority Android.
Examples from US retail and e-commerce
Real behavior across the US market illustrates the pattern better than theory.
High frequency categories that earned it
Grocery, quick-service food, pharmacy and coffee are the clearest app winners in US retail. The purchase happens weekly or daily, the order is highly repetitive, and the app removes friction from a task the customer already intends to complete. Order-ahead flows, stored favorites and loyalty balances are genuinely better native, and the frequency easily absorbs the install cost.
Within D2C, the equivalents are replenishable consumables: supplements, pet food, personal care, coffee subscriptions. These brands have a natural reorder cycle to build around, which is also why subscription structures work in some categories and fail in others. Our analysis of subscription D2C models maps which categories actually sustain that cadence.
Considered purchase categories that mostly did not
Furniture, mattresses, eyewear frames, luggage and premium apparel sit at the other end. Purchase cycles run in years, discovery happens through search, social and editorial coverage, and customers research across devices before buying. For these brands, investment in fast mobile pages, strong product content, generous return policy communication and a short checkout produces more revenue than any app would.
Some of these brands do run apps, generally as a retention layer for a small VIP cohort, or as a companion to physical stores. That is a reasonable use, provided the business case is honest about the size of the audience being served.
The wholesale pivot changes the question entirely
A growing number of US D2C brands have moved a large share of volume into retail partners and marketplaces, which reduces the strategic value of an owned app because the brand no longer controls most transactions. When a brand’s growth comes from shelf space rather than its own site, engineering budget is better spent on product content syndication, inventory accuracy and retail media than on a native build.
Smaller catalogs and creator brands
For brands with narrow catalogs, the app case is weakest of all. A store with twenty products does not need a sophisticated browsing experience; it needs a fast page and a two-tap checkout. This is the same logic that makes lightweight site builders viable for small-batch sellers, a point covered in our look at Squarespace Commerce for creators working at that scale.
Tools, partners and vendors worth knowing
If you decide to proceed, the vendor landscape splits into a few clear layers. None of these are endorsements; they are the categories to shortlist within.
App builders on top of your commerce platform
Several vendors build and maintain a native or hybrid app that syncs directly with an existing Shopify, BigCommerce or headless backend, typically on a monthly subscription. This is the fastest and cheapest route to a functioning app, and the tradeoff is design flexibility. For brands testing whether an app moves retention at all, a templated build is the sensible first experiment.
Cross-platform frameworks
React Native and Flutter dominate custom builds, letting one team ship to both platforms from a largely shared codebase. Choose this route when you have a genuine native capability requirement and the in-house engineering to sustain it. Budget for maintenance, not just the build.
Engagement and messaging infrastructure
Push, in-app messaging and lifecycle campaigns run through customer engagement platforms that should sit across both app and web rather than only the app. Insisting on a unified messaging layer from day one prevents the classic outcome where app users and web users receive contradictory campaigns.
Attribution and deep linking
Mobile measurement partners handle install attribution and deferred deep linking, which is what makes an ad click land on the right product page inside the app after installation rather than on a generic home screen. Without this, app campaign performance is unmeasurable and the customer experience is poor.
Web performance tooling
Whatever you decide about apps, the mobile web work continues. Core Web Vitals monitoring, image optimization, edge rendering and checkout analytics deliver returns across your entire traffic base. The Baymard Institute’s long-running review of checkout research consistently places documented average cart abandonment near the seventy percent mark, and a meaningful share of that is attributable to fixable checkout friction rather than genuine loss of intent.
A practical sequencing plan
For a brand that has not yet built an app and is genuinely unsure, the following order minimizes wasted spend.
- Fix mobile web performance and checkout first. Measure page speed on real devices on cellular connections, not on office wifi. Reduce checkout to the minimum viable field set. Add the wallet payment methods your customers already use.
- Ship a progressive web app. Add the manifest and service worker so returning customers can install a home screen icon. This costs a fraction of a native build and tests whether home screen presence changes behavior at all.
- Instrument repeat purchase cohorts. Track ninety day and three hundred sixty five day repeat rates by acquisition channel. This is the number the app decision rests on.
- Run a retention experiment on your best cohort. If PWA install moves repeat rate meaningfully among your top customers, a native app will likely move it further. If it does nothing, an app will not save you.
- Only then, scope the app. Start templated, seed installs from existing customers, and set a defined review point at which you either invest further or sunset it cleanly.
The through line across all five steps is that the mobile web work is never wasted, which is exactly why it comes first. Every improvement there compounds across your whole customer base, and it is the surface that feeds every other channel you operate, including the pillar-level channel decisions covered in our guide to selling on global e-commerce marketplaces.
The brands that get this right in 2026 are not the ones with the best app or the best website. They are the ones that stopped treating the two as a strategic identity and started treating them as tools with different jobs: the web brings people in, the app keeps the ones worth keeping. And for a brand that does not yet have people worth keeping in volume, there is only one of those jobs that matters. That framing is also the reason so many teams end up revisiting whether retail brands still need a shopping app a year or two after launching one.
Frequently asked questions
Does Apple take 30% of my D2C sales if I build an app?
For physical goods, generally no. Apple’s and Google’s published developer guidelines direct sellers of physical products and real world services to use payment methods other than in-app purchase, which means your normal checkout and processor apply. Commission applies to digital goods and in-app subscriptions. Because platform terms change and vary by program, verify the current rules in the platforms’ own developer documentation before modeling revenue.
What repeat purchase rate justifies building an app?
There is no universal threshold, but the practical test is whether a meaningful share of your customers buy three or more times a year without discount prompting. Below that, the fixed cost of building and maintaining an app rarely clears. Replenishable categories such as supplements, pet food and personal care usually pass; considered purchases such as furniture and mattresses usually do not.
Is a progressive web app good enough instead of a native app?
For a large share of D2C brands, yes. A PWA delivers home screen presence, faster repeat visits and offline caching at a small fraction of the cost, while keeping a single codebase. The gaps are deep hardware access such as augmented reality try-on, and push notification reliability, which is stronger on Android than on iOS. If your app wishlist is home screen icon plus speed, a PWA covers it.
Will an app improve my conversion rate?
App users typically show higher conversion rates, but this is largely a selection effect rather than a causal one. People who install your app are already your best customers, so their higher conversion reflects who they are, not what the app did. Comparing app conversion to overall site conversion overstates the benefit substantially. Compare app users against a matched cohort of your best web customers instead.
Should I show an “open in app” prompt on my mobile site?
Use a small dismissible banner at most, and ideally only for logged-in returning customers. Full-screen interstitials that block content have historically been treated unfavorably in mobile search guidance and impose a conversion cost on every visitor, including the majority who will never install. The prompt should never appear before a first-time visitor has seen the product.
How much does it cost to build and run a D2C app?
Costs vary enormously by route. A templated app builder on top of an existing commerce platform runs as a monthly subscription and can launch in weeks. A custom cross-platform build is a substantial engineering project with a permanent maintenance line covering two operating systems, SDK updates, store review cycles and crash monitoring. The recurring cost is the part most business cases underestimate.
Does having an app help or hurt my SEO?
An app itself does not improve organic search performance, because app content is not indexed the way web pages are. The risk is indirect: teams that shift attention to the app often let mobile site speed, product content and technical health slip, which does hurt rankings. Keep the web surface as the primary investment and the app as an additive retention layer.
How do I get people to install without paying for it?
Seed from customers you already have. Packaging inserts, post-purchase order tracking flows, email and SMS to buyers, and account holders logging into mobile web are all far cheaper sources than paid install campaigns, and they produce dramatically better retention because those users already have a relationship with the brand.
What should I measure to know if the app is working?
Track incremental repeat purchase rate against a matched cohort, thirty and ninety day retention after install, revenue per installed user versus comparable web customers, and uninstall rate following notification campaigns. Total app revenue on its own is a misleading metric, because most of it is revenue that would have arrived through the website anyway.