Skip to content

Integration · Mobile

Mobile apps on your commerce platform

iOS, Android and Flutter shopping apps on the same commerce API as your web store: one catalogue, one cart and account, push notifications and app store releases.

Kinds of data synced
4
Systems
3
Retries and alerts built in
Queued

What moves, which way

One catalogue, one cart, one account, on web and in the app. Each kind of data has one system of record, so nothing gets overwritten.

  • Catalogue, prices and stockStore → Mobile appsHow often: Live, through the APICommerce engine
  • Cart and wishlistBoth waysHow often: LiveCommerce engine
  • Accounts and order historyBoth waysHow often: LiveCommerce engine
  • Push notification eventsStore → Mobile appsHow often: On eventStore

How we connect it

  • 01ConnectionThe app uses the same API as the web store, so prices, stock and promotions never differ between them.
  • 02OwnershipA cart started on the phone is there on the laptop, and the other way round.
  • 03TraceabilityReleases go through the App Store and Google Play with staged rollouts.

When something fails

Integrations fail in predictable ways. These four rules keep a failure from reaching a customer.

  1. Queued

    Every change travels as an event on a queue, so nothing waits on a slow or offline system.

    Phase 1 of 4

  2. Safe to retry

    Each message carries an ID, so a retry never creates a duplicate order or double stock movement.

    Phase 2 of 4

  3. Visible

    Messages that keep failing move aside and alert a named engineer, with the reason attached.

    Phase 3 of 4

  4. Reconciled

    A nightly check compares key numbers between systems and flags any drift before customers notice.

    Phase 4 of 4

Questions

Native or Flutter?

Flutter builds iOS and Android from one codebase and suits most commerce apps. Native makes sense when you need deep platform features.

Book an architecture review

A 60-minute session with a senior architect. We review your current platform, integrations and growth plans, then send a written summary of risks and options.

  • For companies with a real platform decision coming up
  • NDA signed before we talk details
  • The written summary is yours to keep
Your project

What are you planning?

Where you are today

Where are you today?

Platform Optional
Annual online revenue Optional
When do you need to decide? Optional
Your details

A senior engineer replies within one working day.