Building an e-commerce app in 2026: the guide
75% of mobile carts are abandoned, often because the experience is too slow or too complex. A native app converts on average 3 times better than a mobile site.
Article summary
- 75% of mobile carts are abandoned, often because the experience is too slow or not reassuring enough.
- Conversion sits around 1% to 2% on mobile web, and 3% to 5% on a native app.
- On mobile web, checkout abandonment exceeds 70%, mostly because of the payment form.
- Apple Pay and Google Pay bring payment down to one tap and biometric recognition, with no card re-entry.
- A cart-abandonment notification, sent 2 to 4 hours later, often exceeds 10% click conversion.
Summarize this article with
75% of mobile carts are abandoned. Not because buyers did not want to buy. Because the mobile experience was too slow, too complex, not reassuring enough. Your responsive site is not a mobile app. And that confusion costs you sales every day.
A mobile e-commerce app built well converts on average 3 times better than a mobile site. Sessions are longer, average order value is higher, and the return rate of loyal customers is structurally higher. This is not a trend. It is what the numbers have shown since the e-commerce giants, ASOS, Amazon, and Zalando, made their app their primary sales channel.
firstapp works with founders who want to turn their mobile traffic into revenue. This guide covers what that means in practice.
The problem: your mobile site is costing you sales
The average conversion rate on mobile web sits around 1% to 2%. On a native app, that figure rises to 3% to 5%. On the apps of the most optimized brands, it exceeds 8%.
The gap comes from several structural factors.
The first is speed. A native app loads data from cache, with no HTTP request on every interaction. The feeling of fluidity is immediate, even on a mediocre connection. A mobile site reloads every page from a server. On 4G in a dense area, the difference is noticeable. On 3G while moving, it is a deal-breaker.
The second is payment friction. On mobile web, the user has to re-enter their address, card number, and CVV. Even with autofill, that is 12 fields to validate on a 6-inch screen. In an app with Apple Pay or Google Pay, it is one tap and biometrics. Checkout abandonment drops mechanically.
The third is the relationship over time. A mobile site has no direct re-engagement channel. An app can send a push notification 2 hours after a cart abandonment, or alert a customer when an out-of-stock product is back. Used well, this channel represents 10% to 20% of additional revenue on the most mature apps.
If your existing app underperforms on these metrics, our guide to the mobile app redesign helps you diagnose exactly where you are losing money.
Newsletter
Once a week.
Last issue
We opened 10 apps to see how they sell a subscription.
+534 people read us each week
Why a native app converts better than a mobile site
The question "app or responsive mobile site?" has been settled for e-commerce for several years. But many merchants still answer it poorly, often for short-term cost reasons.
A responsive site adapts to screen size. It does not adapt to mobile interaction patterns: no native gestures, no direct camera access for scanning, no frictionless biometric payment. The experience is acceptable. It is not optimal.
A native app has the phone's full toolkit: Face ID, Touch ID, Apple Pay, Google Pay, push notifications, camera, geolocation, Haptic Feedback. It stores the catalog and the cart locally, which makes the experience instant. And it creates a permanent entry point on the phone's home screen, a presence the mobile site never has.
For markets or use cases where the question is still open, our full comparison web app vs native mobile app helps you decide.
The types of e-commerce apps
Not all e-commerce apps look alike. Identifying your model up front shapes architecture decisions and feature priorities.
The DTC brand app (Direct-to-Consumer)
A brand that sells directly to its end customers: ready-to-wear, cosmetics, food, accessories. The app is the premium channel of the customer relationship. It carries the catalog, checkout, loyalty program, order history, and personalized recommendations. The challenge is to create a coherent brand experience that justifies the download against the big platforms.
The marketplace
An intermediary that connects sellers and buyers: Vinted, ManoMano, LeBonCoin in a different register. Two sides to manage, the buyer app and the seller app, with very different experience logics. The complexity is in flow management (payment, commission, disputes, reviews) and in the matching algorithm.
B2B commerce
A distributor or manufacturer that sells to professionals on mobile: replenishment ordering, a catalog with prices negotiated per client, hierarchical order approval. These apps combine B2B constraints (ERP integrations, multi-user account management) with B2C experience requirements.
The subscription commerce app
A monthly box, a subscription to a recurring delivery service. The logic is close to a SaaS app: the challenge is less the initial conversion than retention over time. Subscription pauses, smart win-backs, a referral program: these mechanics have to be designed from the start.
The essential features of an e-commerce app
Here is what a serious e-commerce app has to ship in V1. Not all at once, but in this order of priority.
The catalog and search
Smooth navigation, relevant filters, instant search that tolerates typos. The catalog is the heart of the app. A search that returns empty results on common terms is a lost sale. Variant management (size, color, quantity) has to be intuitive on a small screen, which takes specific UX work.
The purchase funnel
A persistent cart (that survives closing the app), checkout in 2 steps maximum, saved addresses. Every extra step in the funnel is a leak. The goal is to take the user from product to payment in fewer than 3 interactions.
The customer account and history
Light sign-up (Apple Sign In, Google Sign In), order history, real-time delivery tracking, paperless returns. The customer account is also the entry point to the loyalty program.
Reviews and social proof
Reviews shown in the right place in the product journey, a post-purchase collection system. On mobile, other customers' photos of the product convert better than studio photos. Integrating a UGC flow (user-generated content) into product pages is underused by most apps.
The loyalty program
Points, cashback, VIP statuses, perks reserved for app members. The loyalty program is the mechanism that turns a one-off buyer into a repeat customer. On its own, it justifies downloading the app instead of using the website. Our benchmarks on the mobile app retention rate show that apps with an active loyalty program have a significantly higher median Y1 retention.
Apple Pay and Google Pay: the checkout that changes everything
This is the technical decision with the most impact on an e-commerce app's conversion rate, and it is often the last one founders think about.
On mobile web, checkout abandonment exceeds 70%. The main cause is not the price, or the delivery time. It is payment-form friction. Entering 16 card digits, an expiration date, and a CVV on a phone screen, on the move, is a painful act. Many people do not do it.
Apple Pay and Google Pay compress that process into one tap and biometric recognition. The address and payment method are already stored on the phone. The user has nothing to type. The time between "I want to buy" and "it's ordered" goes from 2 minutes to 10 seconds.
The impact is immediate and measurable. Apps that integrate Apple Pay and Google Pay from launch consistently see a rise in checkout conversion. This is not a premium feature to plan for later. It is a prerequisite to integrate from V1.
Push notifications: recovering lost sales
An e-commerce app with no push notification strategy is a salesperson who never follows up. The channel exists, it is free, and most apps use it badly - either not at all, or so aggressively that they get notifications turned off within 48 hours.
The 4 sequences that actually work.
Cart abandonment. A product added to the cart, a session closed without a purchase. A notification 2 to 4 hours later, with the product visual and a direct hook. It is the most profitable trigger in mobile e-commerce, with click conversion rates that often exceed 10%.
Back in stock. An out-of-stock product the user set an alert for. The notification at restock is a purchase intent captured weeks earlier. The purchase rate on this kind of push is among the highest in the e-commerce toolkit.
Order tracking. Confirmation, shipping, delivery on the way. These notifications are expected, opened, and they build trust. They also reduce the volume of support contacts.
Personalized offers. Based on purchase history and categories browsed. A promotion on a category the user visited 3 times without buying is infinitely more relevant than a generic promotional blast sent to the whole base.
How firstapp approaches e-commerce projects
Mobile e-commerce has a particularity many agencies underestimate: every millisecond of latency and every extra form field translates directly into lost euros. This direct link between experience quality and revenue is what makes these projects demanding, and what makes them exciting.
At firstapp, we start by auditing the purchase funnel before writing a line of code. Where are the leaks? What does the current website reveal about buyer behavior? Which 3 features will have the most impact on conversion from launch?
We ship a V1 in 4 to 6 weeks, with the purchase funnel optimized, Apple Pay and Google Pay integrated, and push notifications configured from the start. Not because we want to be fast for the sake of it - because one month of real data on real buyers is worth more than 3 extra months of specs.
MVP, budget, and platform for an e-commerce app
Defining the MVP scope
The temptation in e-commerce is to pack every feature into V1: full catalog, loyalty program, personalized recommendations, AR (virtual try-on), live shopping. The result: 9 months of development, a budget that triples, and an app that ships when the market has moved on.
A well-scoped e-commerce MVP covers: catalog + search, customer account (Apple/Google Sign In), persistent cart, checkout with Apple Pay and Google Pay, order history, and a cart-abandonment push sequence. Everything else is an iteration. Our analysis of the mobile app MVP breaks down what must, and must not, be in a V1.
iOS, Android, or both?
For B2C e-commerce, launching on iOS first is generally the right decision. The iOS buyer profile has a structurally higher average order value and conversion rate than Android. Once V1 is validated and the funnel is optimized, Android follows in a second step.
The budget
A well-designed e-commerce MVP - catalog, checkout with native payments, customer account, push notifications - generally sits between €15,000 and €30,000. The variable line item is catalog complexity (variant management, real-time stock, promotions) and integrations with your existing back end (Shopify, WooCommerce, custom ERP). Our guide to the mobile app quote details the 7 parameters that move this figure in your specific case.
FAQ
Is a mobile e-commerce app really better than a responsive site?
For a merchant with a significant volume of mobile traffic, yes. The conversion difference is documented and structural. A native app gets biometric payments, push notifications, and a local cache, which responsive cannot reproduce. The question is not "app or site" but "from what volume is the app's ROI positive?" For most brands with more than 10,000 monthly visitors on mobile, the answer turns favorable quickly.
Should you connect to Shopify or WooCommerce, or build a custom back end?
If you already have a working e-commerce back end (Shopify, WooCommerce, Prestashop), the mobile app connects to that existing system via API. That is the most common setup and the fastest to put in place. A custom back end is justified only if your specific needs (complex pricing logic, marketplace, B2B with multiple accounts) cannot be covered by existing platforms.
How do you manage the product catalog in the app if the website changes often?
The app does not duplicate the catalog. It consumes it through your back end's API. When you update a price or add a product on Shopify, the app reflects the change in real time, with no update to ship on the App Store. That is the standard architecture, and it is non-negotiable for any merchant with a living catalog.
Can you launch an e-commerce app without an existing website?
Yes, but it is generally not the best starting strategy. A website, even a simple one, lets you validate the offer, build an initial customer base, and feed the app with behavioral data from launch. Launching the app first makes sense in specific cases: a brand that wants an exclusive mobile channel, or a project born directly on mobile with no e-commerce history.
Which metrics should you watch first at the launch of an e-commerce app?
The four to watch from day 1: checkout conversion rate (target: 3% minimum, 5% with Apple Pay integrated), cart abandonment rate (and the effectiveness of the recovery push sequence), average order value (compared with the website), and the 30-day return rate (which measures retention and the effectiveness of the loyalty program).