Skip to main content
Dimension 03 // Mobile

Apps that keep working when the Wi-Fi gives up.

Cross-platform mobile apps for customers, field teams, and warehouses, built to sync reliably with your back office, even from a basement loading dock.

One codebase, two app stores, offline by design.

Frameworks
Flutter · React Native
Specialty
Offline-first sync
Back office
Odoo & custom APIs

Explore mobile apps

What we build

Customer apps

Ordering, account, and service apps connected to your systems.

Warehouse apps

Barcode scanning, picking, and stock counts on rugged devices.

Field apps

Jobs, inspections, signatures, and photos captured offline.

Internal tools

Approvals, dashboards, and notifications for staff on the move.

One backend. Every screen.

Your web app, iOS app, and Android app call the same API, with the same rules and the same data. Hover a device (or tap it) to send requests: repeats are answered by the cache in milliseconds, so the app servers and database only work when they have to. The figures are illustrative.

One API backend serving web, iOS and AndroidThree device docks send requests along cables into one server rack. Each request passes the gateway and checks the cache; about 85% are answered straight from the cache, and the rest go on to the app servers and database, then get cached for next time.idleidleidleidletarget 85%– mshover or tap– mshover or tap– mshover or tap
ReadyHover or tap a device to send a request
Last latency
–
Avg · cache hit (0)
–
Avg · cache miss (0)
–
Cache hit rate · target 85%
–
  • Web app–
  • iOS app–
  • Android app–
How it works
  • Gateway checks the token and rate limit on every call.
  • Cache answers repeat reads without touching the database.
  • On a miss the app reads the database, then fills the cache.
  • Same API for web, iOS and Android, so all three stay in sync.

Also building for the browser?

See web engineering for SaaS platforms, progressive web apps, and design systems.

How we approach mobile

We start with the people using the app and the place they use it: a warehouse aisle, a customer's site, a delivery van. That decides how simple screens must be, which device features matter, and whether the app must work offline.

Most business apps we build are cross-platform, with one codebase for iOS and Android, connected to Odoo or your backend through a well-defined API. Every app ships with crash reporting, analytics, and a plan for updates, because launch is the beginning of an app's life, not the end.

Which service fits

If you needStart with
One app for iPhone and AndroidReact Native & Flutter
A fast field app connected to OdooOdoo mobile apps
An app that keeps working without signalOffline-first architecture

Every mobile app ships with

  • Crash reporting and analytics
  • Secure login and encrypted storage
  • Automated builds and test releases
  • Store listings under your accounts
  • A maintenance plan for OS updates

How a mobile project runs

  1. Discover

    Shadow users at work and agree the core tasks.

  2. Prototype

    Test clickable designs with real users.

  3. Build

    Iterations with test builds on real devices.

  4. Release

    Store submission, staged rollout, and support.

App or mobile-friendly web?

Not every need justifies an app. If users only need occasional access, a responsive web app or PWA may be faster and cheaper, and we'll recommend it.

Who we work with

We build apps for operations teams, field staff, and customers: warehouse and delivery crews, technicians, sales reps, and the businesses that serve them. Most connect to Odoo or another ERP, and many must keep working where the signal doesn't.

Keeping apps healthy

Apps need regular care as operating systems and store rules change. We keep dependencies current, monitor crashes and performance, and plan small updates throughout the year so no release becomes a scramble.

Built for the conditions, not the demo

Mobile apps fail in the field for predictable reasons: weak signal, gloves, glare, old devices, and users who are busy doing something else. We design for those conditions from the first sketch, with large touch targets, offline-first data, and screens that make the next action obvious.

We test on real devices in real places where we can, such as a warehouse aisle or a delivery van, because an emulator on a fast office connection hides exactly the problems that matter.

Connected to the back office

A business app is only as good as its connection to the systems behind it. We design the API layer alongside the app, so orders, stock, jobs, and signatures flow to and from your ERP reliably, and conflicts are handled by rules your team agreed rather than by whichever device synced last.

Choosing the right kind of app

OptionGood forTrade-off
Progressive web appSimple tools, quick rollout, no app storeWeaker offline and device access on some phones
Cross-platform appMost business apps for iOS and AndroidOccasional native work for special hardware
Native appHeavy device features or graphicsTwo codebases to build and maintain

Frequently asked questions

Native or cross-platform?
Cross-platform suits most business apps. Native makes sense for heavy device integration or very demanding graphics.
Do you publish to the app stores?
Yes, including store listings, review requirements, and release pipelines.
Can the app work offline?
Yes. Offline-first architecture is one of our specialties.
Can it connect to Odoo?
Yes, through Odoo's API or a dedicated backend service.
Should we build a PWA instead?
Maybe. PWAs avoid app stores but have device limits. We compare both against your needs.
How much does a business app cost?
It depends on the number of workflows, integrations, and offline needs. After discovery we give a fixed price for a defined first release.
Do you maintain apps after launch?
Yes. Maintenance plans cover OS updates, store policy changes, dependency upgrades, and small improvements.
Can you build an app for our customers rather than staff?
Yes. Customer-facing apps for ordering, bookings, or account access follow the same practices, with more attention to onboarding and store presence.
Do you design the apps as well as build them?
Yes. Design, prototyping, and user testing are part of every mobile project, so the app is shaped by the people who will use it.
Can apps send notifications?
Yes, with push notifications on both platforms, targeted by role or event.
Can one app serve both staff and customers?
Sometimes, but they usually need different flows and permissions. We often build one shared backend with two focused apps on top.