Native or React Native?

React Native with Expo in most cases: one codebase, two stores and half the maintenance. Native when there's a real hardware or graphics requirement, and that gets said before we start, not halfway through.

Do I need an app if I already have an online store?

Only if there's repeat purchase or a field operation. For one-off buying, a well-built website wins. If your customer buys monthly, or you have reps and a warehouse, the app pays for itself.

Who publishes on the App Store and Google Play?

The developer accounts are yours and we publish through them. We handle the listing, the screenshots, the privacy policies and the replies to store reviews.

Does it work offline?

In field sales and warehouse apps it has to: it works on local data and syncs when signal returns, with conflict resolution defined and tested.

Does it connect to my ERP and my store?

Yes, through the same integration layer we use on custom platforms. The app isn't an island: it drinks from the same data as the rest of the channel.

What does it cost to maintain?

There's an unavoidable fixed cost: developer accounts, keeping up with each iOS and Android release, and bug fixes. It gets budgeted from the start, not sprung on you six months in.

Apps

An app is only worth it if somebody opens it twice.

Customer, field-sales and warehouse apps built with React Native and Expo. Wired to the same data, published on the stores and looked after once they're live.

Book a free audit

Talk to the team

7Deliverables across product, build, release and data

iOS + AndroidOne codebase, two stores, the same experience

OTAFixes in hours without waiting for store review

The problem

Three reasons an app dies on its own

It solves nothing the website doesn't

If it's your store inside a frame, nobody installs it, and whoever does deletes it at the first phone clear-out.

The warehouse still runs on paper

Counts, locations and picking written down by hand, with stock discrepancies that end up as cancelled orders.

It launched and stopped there

No updates, store warnings left unresolved, and nobody looking at what people actually do inside it.

Deliverables

What we deliver

07 Inside the service

Product definition and scope

What job the app does that the website can't, for whom, and how success gets measured. No answer, no app.

iOS and Android apps with React Native

One Expo codebase, native modules where they matter, and performance looked after on long lists and transitions.

Customer and loyalty app

Repeat purchase, past orders, points card, vouchers and replenishment reminders for the items they actually buy.

Field sales app

Catalogue with customer-specific pricing, order taking online and offline, account history and signature on the visit.

Internal warehouse and inventory app

Barcode scanning, locations, cycle counting, picking and live syncing with the ERP.

Push notifications and engagement

Segmented by behaviour, not blasted: basket, back-in-stock and order status.

Release, maintenance and analytics

Store listings, App Store and Google Play reviews, OTA updates, crash tracking and funnel-level product analytics.

Not everything applies to every account. The audit decides what goes in and in which order.

How we work

How we get an app to the stores

01Step
Defining the job the app does
One main flow, one clear user and one success metric. If the app doesn't take work off somebody, it stops here.
02Step
Clickable prototype tested with real users
Tested with actual sales reps, warehouse staff or customers before any production code gets written.
03Step
Incremental development with internal builds
Every two weeks there's an installable version for your team. Feedback lands before fixing it gets expensive.
04Step
Field testing and release
Real devices, TestFlight and Google Play internal track, store listings, privacy policies and the store review process.
05Step
Maintenance, updates and data
Bug fixes, keeping up with each iOS and Android release, updates without review where possible, and a monthly read of usage.

Metrics

What we answer for

Installs and activations: A download isn't enough: we count who completes sign-up and reaches the first genuinely useful action.

30-day retention: The share of users still opening it a month later. It's the number that says whether the app is alive.

Sessions per user: How often it gets used. In operational apps that's productivity; in customer apps it's habit.

In-app conversion rate: Orders over sessions, compared with the website over the same period and the same audience.

Crash-free sessions: The share of sessions that end without an error. Below 99% it shows up in the reviews and in retention.

Store rating: The score and the substance of App Store and Google Play reviews, with the complaint reasons tracked.

We measure and report these metrics. We don't guarantee figures: your starting point decides.

Questions

What people ask us before starting

React Native with Expo in most cases: one codebase, two stores and half the maintenance. Native when there's a real hardware or graphics requirement, and that gets said before we start, not halfway through.

Keep going

What it pairs with

Custom platforms

For when off-the-shelf software runs out of road.

View service

Ecommerce 360

Your own store doing the work: acquisition, conversion and repeat purchase.