Native iOS and Android, one codebase where it makes sense.
Mobile apps on the same continuous delivery pipeline as the web, with crash and performance monitoring from launch day, and the same views your web users get, in the hand of a plant head or a house hunter.
What it covers
React Native
One codebase for shared logic and screens, with native modules where the platform demands them.
Native where it matters
Camera, background work, push, offline and payments done natively, not fought through a wrapper.
Fixes without waiting for the store
Over the air updates ship a fix to every phone in an hour, without a store review. Store releases, for anything native, are automated: builds, signing and submission, so a release is a decision rather than a week.
Taking over an app
Inheriting a codebase from another vendor, stabilising it, and shipping the next feature without a rewrite.
How we do it
Shared discovery with web
The story map covers every surface, so mobile is a first class slice of the product rather than a port.
One pipeline
Web and mobile ship from the same CI/CD with the same quality gates. Mobile does not get a slower, looser process.
Monitoring from launch
Crash reporting, performance traces and analytics in the first build, so the first week of real users is measured.
Small releases, often
JavaScript level changes go over the air the same day. Native changes go through the stores on a cadence. Never a big bang, and a bad update can be rolled back in minutes.
- 1
Shared discovery with web
The story map covers every surface, so mobile is a first class slice of the product rather than a port.
- 2
One pipeline
Web and mobile ship from the same CI/CD with the same quality gates. Mobile does not get a slower, looser process.
- 3
Monitoring from launch
Crash reporting, performance traces and analytics in the first build, so the first week of real users is measured.
- 4
Small releases, often
JavaScript level changes go over the air the same day. Native changes go through the stores on a cadence. Never a big bang, and a bad update can be rolled back in minutes.
What you get
- iOS and Android apps in the stores, on your accounts
- Over the air updates for same day fixes, and automated store builds, signing and submission for the rest
- Crash, performance and product analytics from the first release
- Shared component library with the web where it applies
- Code, documentation and a team that can run it
Where we have done it
view.com.au: the Android and iOS rebuild landed with the 2023 brand launch. In 2024 we took the apps over from another vendor and shipped project profiles, school catchment and REIP Nexus.
view.com.auLineomatic: the customer portal runs in a React Native app, so a plant head checks production from anywhere and gets alarms before downtime.
Lineomatic
Questions we get asked
React Native or fully native?
React Native by default, native where the feature needs it. We decide per feature, not per app, and we tell you why.
Can you ship a fix without a store release?
Can you take over our existing app?
Who owns the store accounts?
Also under product development
Talk it through
Tell us what you need from mobile development.
Thirty minutes with one of our architects. We will tell you whether it is a pilot, a build, or not worth doing yet.