eCommerce app development is the process of building a mobile app that lets customers browse products, pay and track orders on their phone. Most apps connect to an existing online shop, such as Shopify, WooCommerce or Adobe Commerce, and read products, stock and orders from it.
An app suits retailers with repeat customers, a large mobile audience or a loyalty scheme. A new or small shop usually gets more from a mobile-friendly website first.
Based on Intelivita's project pricing, a custom eCommerce app costs from £12,000, rising above £120,000 for complex apps, and takes 3–6 months to build. The price depends on the features, the number of platforms (iOS, Android or both) and the systems the app connects to.
What Is eCommerce App Development?
eCommerce app development is building a mobile or web application that allows people to buy goods or services over the internet. The app joins the customer screens to the business systems that manage the product catalogue, stock, payments and delivery.
An eCommerce app is the finished product: a shopping app installed on a phone or tablet. It brings product search, checkout and order tracking into one place. ASOS, Tesco and Sainsbury's all run shopping apps alongside their websites.
For a business, an app creates a direct channel to customers, collects data on how they shop and supports personalised offers. For customers, it speeds up checkout and keeps their account, saved items and orders on their phone.
eCommerce apps use the same three business models as online shops.
- Business-to-consumer (B2C): a retailer sells to the public, as ASOS does.
- Business-to-business (B2B): companies order wholesale stock or reorder supplies, often at trade prices.
- Consumer-to-consumer (C2C): people sell to each other through a marketplace, such as Depop or Vinted.
Does Your Business Need an eCommerce App or a Mobile Website?
Most businesses need a mobile-friendly website before they need an app. A website reaches every shopper through search and links, while an app reaches only people who download it. An app pays off when customers buy from you often enough to keep it on their phone.
An app is worth building when most of these apply:
- Customers buy from you several times a year.
- Most of your sales already come from phones.
- You run, or plan, a loyalty scheme or member pricing.
- Push notifications for restocks, offers or order updates would bring customers back.
- You need phone features a browser handles poorly, such as barcode scanning or camera try-on.
| Option | What it is | Best for | Main limit |
|---|---|---|---|
| Mobile-friendly website | Your online shop, designed for phones | Every shop; the first step | No home-screen presence or app store listing |
| Progressive web app (PWA) | A website that installs to the home screen and works with a weak connection | Shops that want app-like speed without app store fees | Push notifications and device features are more limited on iPhones |
| Native or cross-platform app | An app downloaded from the App Store or Google Play | Retailers with repeat buyers and loyalty schemes | Highest cost; customers must choose to download it |
If you do not yet sell online, start with the website. The eCommerce web development process covers that first stage, and the cost of an eCommerce website in the UK is a fraction of a custom app.
What Features Does an eCommerce App Need?
An eCommerce app needs a product catalogue, search and filters, a basket, secure checkout, customer accounts and order tracking. These let customers browse, choose, pay and receive their order. Everything else can follow in later releases.
Features for the First Release
- Product catalogue: categories, descriptions, prices and stock levels, kept in step with your online shop.
- Search and filters: narrow products by price, size, rating or brand. Good filters matter most in large catalogues.
- Basket: holds items, changes quantities and lets customers review the order before paying.
- Checkout and payments: card payments through a gateway such as Stripe or PayPal, plus Apple Pay and Google Pay for one-tap payment.
- Customer accounts: sign-up, login and saved addresses. Two-factor authentication adds protection for payment and address details.
- Order tracking: status updates from dispatch to delivery, which cut "where is my order?" queries.
- Push notifications: order updates, basket reminders and offers, sent only with the customer's consent.
Features to Add Later
- Wish list: customers save products to buy later, and you learn what they want.
- Reviews and ratings: verified reviews help other buyers decide.
- Loyalty scheme: points, member prices or rewards, often the main reason customers keep the app.
- Personalised recommendations: products suggested from browsing and order history, usually powered by machine learning.
- In-app support: live chat or help articles for order and payment questions.
- Camera features: barcode scanning in store, or augmented reality to see furniture in a room or try on glasses.
Native, Cross-Platform or PWA: Which Approach Suits an eCommerce App?
A cross-platform app suits most retailers: one codebase serves iPhone and Android, which cuts cost and time. Native apps suit brands that need the fastest performance or deep device features. A PWA suits shops that want an app-like experience without the app stores.
| Approach | How it is built | Strength for a shop | Trade-off |
|---|---|---|---|
| Native app | Separate apps in Swift (iOS) and Kotlin (Android) | Fastest, with full access to camera, payments and notifications | Two codebases, so the highest cost |
| Cross-platform app | One shared codebase, usually Flutter or React Native | Close to native speed for most shopping journeys at lower cost | Some device features need native code |
| Hybrid app | Web pages inside a native container, using Ionic or Cordova | Reuses web code; quick to build | Slower and less smooth than native or cross-platform |
| Progressive web app | A website that installs from the browser | No app store approval; one build for every device | Fewer device features, especially on iPhone |
For most UK retailers building their first app, the choice is between cross-platform and native. Choose native when the app relies on camera features, heavy animation or very large catalogues on older phones. A progressive web app development project is the lower-cost route when app store presence is not a priority.
Which Technologies Are Used to Build an eCommerce App?
An eCommerce app has three layers: the app customers use, the server that runs the business logic, and the database that stores products, customers and orders. Each layer uses its own framework and language.
| Layer | What it does | Common choices | Languages |
|---|---|---|---|
| App (front end) | Screens customers browse, search and pay on | Flutter, React Native, SwiftUI (iOS only), Jetpack Compose (Android only), Kotlin Multiplatform | Dart, JavaScript or TypeScript, Swift, Kotlin |
| Server (back end) | Accounts, payments, orders and links to other systems | Node.js with Express, Laravel, Django, Ruby on Rails, Spring Boot | JavaScript, PHP, Python, Ruby, Java |
| Database | Stores products, customers, orders and stock | PostgreSQL, MySQL, MongoDB, Firebase Firestore, Amazon DynamoDB | SQL, or the database's own query tools |
An app built on Shopify, WooCommerce or Adobe Commerce often needs little custom server code, because the platform already runs the catalogue, checkout and orders. The app reads and writes that data through the platform's API.
Swift and Kotlin are compared in detail in the guides to iOS app development languages and Android app development languages.
How Does an eCommerce App Connect to Your Online Shop?
An eCommerce app connects to your online shop through the platform's API, a secure link that lets the app read products and stock and send orders back. Your shop stays the single source of truth, so prices, stock and orders match across the website and the app.
Shopify, WooCommerce, Adobe Commerce and BigCommerce each provide one.
- Shopify: The Storefront API supplies products, collections, baskets and customer accounts to custom apps.
- WooCommerce: the REST API and Store API give apps access to products, orders and customers in WordPress.
- Adobe Commerce (Magento): REST and GraphQL APIs cover catalogue, basket, checkout and orders.
- BigCommerce: the GraphQL Storefront API supports custom apps and front ends.
This set-up is often called headless commerce: the platform runs the back office, and the app and website are separate front ends. It lets you change the app without rebuilding the shop.
Shopify retailers have a lower-cost route: app builders from the Shopify App Store turn an existing store into a branded app for a monthly fee. They suit shops that need a standard shopping app quickly but limit custom features. How the main eCommerce platforms compare matters here, because the platform decides how much of the app can be built on what already exists.
Apps that link to an ERP, warehouse system or till system need custom server code between those systems and the app. That integration work is often the largest single cost in a B2B or multi-channel app.
How Do You Build an eCommerce App?
To build an eCommerce app, plan the scope, design the shopping journey, build the app and server, connect payments and your shop, test, launch in the app stores, then maintain it. The steps follow the general mobile app development process, with extra work on catalogue sync, checkout and payments.
Step 1: Plan the Scope and Research the Market
Planning defines the app's goals, audience, budget, timeline and first-release features. A clear plan prevents wasted spend and keeps the timeline realistic. Market research looks at competitor apps, their reviews and what customers expect. For a shop, this step also maps which platform, payment provider and stock system the app must connect to.
Step 2: Design the Shopping Journey
UI/UX design turns the plan into wireframes, mock-ups and visual designs. The user interface covers colours, fonts and buttons; user experience covers how easily customers move from product to payment. Keep the route from home screen to checkout short, make search visible and show product photos large.
Step 3: Build the App and the Server
Front-end development builds the screens customers touch: product pages, basket, account and checkout. Back-end development handles accounts, payments, orders and stock. Developers use Flutter, React Native or native code for the app, and Node.js, Laravel or Django for any custom server.
Step 4: Connect Payments, Your Shop and Other Services
Integrations link the app to the services it depends on. These include a payment gateway such as Stripe, PayPal or Klarna, your eCommerce platform's API, delivery and tracking services, and Firebase for push notifications. Choose a payment gateway on UK card fees, support for Apple Pay and Google Pay, and PCI DSS compliance.
Step 5: Test on Real Devices
Testing checks that the app works across phones, screen sizes and operating system versions. Test the full purchase: search, basket, payment, confirmation email and refund. Tools such as Appium and Postman automate repeat checks. Testing protects the app from crashes, poor reviews and failed payments after launch.
Step 6: Launch in the App Stores
Launch means submitting the app to the Apple App Store and Google Play and switching on production servers. Each store reviews the app against its guidelines, so follow them closely to avoid rejection. Set up analytics and crash reporting before launch. A soft launch to a small group finds last-minute problems before full release.
Step 7: Maintain and Improve the App
After launch, monitor crashes, speed and where customers drop out of checkout. Release fixes and security patches regularly, and update the app for each new iOS and Android version. Use analytics and customer feedback to decide which features to add next.
How Much Does an eCommerce App Cost in the UK?
A custom eCommerce app costs from £12,000, rising above £120,000 for complex apps, based on Intelivita's UK project pricing excluding VAT. The total is the design stage plus the development stage. The initial consultation is free, and post-launch support is a separate monthly cost.
| Stage | What it covers | Intelivita price |
|---|---|---|
| Initial consultation | Scoping, requirements, quotation, fixed cost and timeline | £0 |
| UX/UI design and clickable prototype | User journeys, wireframes, Figma design, clickable prototype | £4,000–£20,000 |
| Development | Mobile app, back end and APIs, admin platform, integrations | £8,000–£100,000+ |
| Post-launch support | Maintenance, security updates, platform upgrades, ongoing improvements | £400–£2,000 a month |
Five things decide where an app falls in that range: the number of features, native or cross-platform build, the systems it connects to, security requirements and how many platforms it supports. A UK-based team costs more upfront but makes communication, UK compliance and post-launch support simpler.
Running costs continue after launch. Apple's Developer Program costs $99 a year, charged in pounds in the UK, and a Google Play developer account costs a one-off $25. Hosting, third-party services, analytics and maintenance add to the yearly cost. The factors behind app development costs in the UK apply to eCommerce apps too, with extra cost for catalogue and payment integration.
What UK Rules and App Store Requirements Apply to eCommerce Apps?
A UK eCommerce app must follow the same consumer and data laws as an online shop, plus the rules of the Apple App Store and Google Play.
UK Law
- UK GDPR and the Data Protection Act 2018: collect only the data you need, keep it secure, publish a privacy notice and pay the ICO data protection fee.
- Privacy and Electronic Communications Regulations (PECR): get consent before sending marketing push notifications or emails, and before tracking or analytics tools store data on the customer's phone, unless an exemption applies.
- Consumer Contracts Regulations 2013: show the total price and key terms before payment, and give customers 14 days to cancel most orders.
- Consumer Rights Act 2015: goods must be of satisfactory quality, as described and fit for purpose.
- PCI DSS: protect card data. Using a hosted payment form or Apple Pay and Google Pay keeps card numbers off your servers.
App Store Rules
- Payments for physical goods: Apple's guidelines (section 3.1.3(e)) require apps selling physical goods to use payment methods other than in-app purchase, such as card payments or Apple Pay. Google Play applies the same rule. Neither store takes a commission on physical product sales.
- Account deletion: an app that lets customers create an account must also let them delete it from within the app.
- Tracking: on iPhone, an app must ask permission before tracking customers across other companies' apps and websites.
- Review: both stores review every new app and update. Missing privacy details, broken links or placeholder content are common reasons for rejection.
Security work continues after launch: encrypt data in transit with TLS, run regular security tests and apply patches quickly.
How Do You Choose an eCommerce App Development Company?
Choose an eCommerce app development company on proven shopping apps, experience with your eCommerce platform, a clear delivery process and support after launch.
- Technical experience: ask which app frameworks, server stacks and eCommerce platform APIs the team has used. A good team can explain when it would choose native over cross-platform for your app.
- Results, not just designs: look for live apps that have launched and grown, with figures on downloads, ratings or conversion.
- References: speak to past clients about deadlines, budgets and support. Communication matters as much as code quality.
- Process and milestones: expect clear phases for planning, design, build, testing and launch, with a named contact and regular demos.
- Understanding of your business: a strong team asks about your customers, margins and fulfilment, and suggests what to leave out of the first release.
Also confirm who owns the code and designs, what support costs after launch, and how app store submissions and updates are handled. Intelivita builds eCommerce apps for UK businesses, from first release to ongoing support.
FAQs
How long does it take to build an eCommerce app?
A basic custom eCommerce app takes 3–4 months to build, and an advanced app 4–6 months or more. An app builder linked to a Shopify store can launch in a few weeks. Integrations with stock or ERP systems add the most time.
Can I turn my Shopify store into an app?
Yes. You can use an app builder from the Shopify App Store for a template app, or build a custom app that reads your store through Shopify's Storefront API. The app builder is faster and cheaper; the custom app gives full control over design and features.
Do Apple and Google take a cut of sales in an eCommerce app?
No. Apple and Google do not take a commission on physical goods sold through an app, because these payments go through your own payment provider. You still pay your payment provider's card fees, Apple's yearly developer fee and Google's one-off registration fee.
Is a progressive web app better than a native app for a shop?
A progressive web app is cheaper and needs no app store approval, so it suits shops testing demand. A native or cross-platform app offers better speed, push notifications on every device and an app store listing, so it suits retailers with loyal repeat customers.
How do you get customers to download a shopping app?
Give customers a reason to install it: app-only offers, a loyalty scheme, faster checkout or early access to sales. Promote the app on your website, in order emails and at checkout, and add app store links to your site's mobile pages.
Discuss Your eCommerce App
Tell us about your shop, your platform and what you want the app to do. We will recommend whether you need an app, a PWA or a better mobile website, and send an itemised quote.