Mobile development

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.

See it in our work

At a glance

Default
React Native, native where a feature needs it
Fixes
Over the air, within the hour
Store accounts
Yours, from the first build
Existing apps
Diagnosed and stabilised first

What it covers

iOS and Android, from one team.

  • 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

One pipeline, small releases, often.

  1. 01

    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. 02

    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. 03

    Monitoring from launch

    Crash reporting, performance traces and analytics in the first build, so the first week of real users is measured.

  4. 04

    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

Apps in the stores, on your accounts.

  • 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

Real engagements, named.

Questions

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?
For most changes, yes. Anything in the JavaScript layer, which is most of a React Native app, goes over the air to every installed phone within the hour, and can be rolled back the same way. Changes to native code, permissions or the app binary still go through Apple and Google review, and we say which is which before promising a date.
Can you take over our existing app?
Yes. We start with a diagnosis, stabilise the release process, and ship the next feature before touching anything structural.
Who owns the store accounts?
You do. Everything is published under your developer accounts from the first build.

What clients say

In their words.

01 / 04

Life Insurance Direct
Before Metricsense, checking calls was a manual process: we selected files for review. Now the platform analyses every call, and we review by risk. It has identified customer experiences we would not have picked up before, and it lets us scale our quality assurance program without increasing headcount, with our team still the human in the loop. It helps us protect our customers, our business and our agents.

Russell Cain

Founder and CEO, Life Insurance Direct

Also under product development

Where it leads next.

All of product development

Not sure this is the right place to start?