E-commerce app development
We build mobile apps for online stores and marketplaces: catalog, cart, checkout, customer account, and the integration with your backend, inventory and order system. iOS and Android come from one React Native codebase; the server side runs on Node.js. We can start from scratch or connect an app to a store that's already running.
This is our turf by real experience: on Jiffy (express grocery delivery, London) we built a set of apps — for shoppers, warehouse pickers and couriers — and the service later grew into a platform for online stores. On Devis Group we built a gifts online store with online payments from scratch. So when we talk about catalogs, checkout and a storefront with thousands of items, it's from practice, not a brochure.
What's included
A catalog with categories, search and filters, a product page, cart and checkout, online payments, a customer account with order history, statuses and addresses, and push notifications on order status. Under the hood — integration with your backend, inventory and catalog: stock, prices, availability and orders stay in sync instead of being keyed in twice.
No backend yet? We stand one up on Node.js: an API for catalog, cart and orders, plus an admin panel for content and products. Already have an ERP, CMS or a marketplace backend? The app connects to it over the API.
When you need two apps
A marketplace or a delivery service needs more than one storefront: alongside the customer app you need a business app (seller, warehouse, operator) and/or a courier app. That's how Jiffy worked — separate apps for shoppers, warehouse pickers and couriers with live map tracking.
We design these sets as a whole: one codebase and one backend, shared order statuses from storefront to delivery, roles and permissions split cleanly. Two or three apps, but one product and one context — no drift between teams.
What we watch in e-commerce
A catalog with thousands of SKUs must stay fast: lazy-loaded lists, caching, quick search and careful image handling. Payments go through your provider (acquiring, wallets, local methods) with clear error and refund handling. Separately — correct statuses and cart state on a flaky network and offline.
App Store and Google Play publishing is on us: review prep, the stores' rules for commerce and payments, and zero-downtime updates after release.
How we run it
Through our cycle: Discovery → MVP → Production → Support. In Discovery we lock the storefront, purchase flows, integrations and metrics. In the MVP we ship a working end-to-end purchase — catalog, cart, checkout, order — on real data, not mockups. Then we harden it for release: load, payment security, monitoring, publishing.
After launch we stay for support: new categories and features, promo mechanics, updates for new iOS and Android versions. The store keeps living and growing instead of freezing on delivery day.
FAQ
How much does an e-commerce app cost?
Can you connect the app to our website and inventory?
How long until launch?
Tell us about your product — a path to production follows
A 30-minute call: the task, the risks and the format of working together. No obligations.