You’re in good company

A few of the companies we’ve worked with.

Native, cross-platform or the web

There’s more than one good way to put your product on a phone. The right one depends on what it has to do and who will look after it, so we recommend one only once we understand both.

Shared by the iOS and Android apps

  • Native: two separate apps, one for iOS and one for Android, each with its own screens, app logic and phone features. Only the back end beneath them is shared.

    Native

    Separate apps for iOS and Android, each built with its platform’s own tools. Often the better fit when the app relies on the phone itself: the camera, location, work in the background or each platform’s newest features.

  • Cross-platform: the iOS and Android apps share one set of screens and one app logic, with the phone’s features native on each side, over one shared back end.

    Cross-platform

    One codebase for both, with native parts where the app needs them. Often the better fit when both apps should work the same way and one team will look after them.

  • A web app: one stack of screens and app logic that opens in the phone’s browser, over the same back end. Everything shown is shared.

    A web app

    If people use it now and then, and don’t need it offline or the phone’s own features, a web app can be simpler to build and run. We’ll say so when it is.

Web & App Development

One back end for web and mobile

Your app and your web product should always agree. So both use the same back end: the same accounts, the same data and the same rules about who can see and change what. A change made in one appears in the other, and a new rule is written once.

Phones don’t all update at once, so the back end keeps working for the versions people still have installed. An app that’s too old asks to be updated rather than failing.

Systems & API Integration
One booking, a boiler service, in the web product and in the app, with the same values in both: the day and the engineer. The day is changed on the web from Thursday to Friday. The change passes once through the shared back end, and the app shows Friday too.

Built for life on a phone

Phones lose signal, get interrupted and get used with one hand on the move. We build for that from the first screen.

  • Works without signal

    People keep working when the connection drops. Changes are saved on the phone and sync when it returns, with clear rules for when two changes meet.

  • Sign-in that’s quick and secure

    Passkeys or the phone’s face or fingerprint unlock where it’s available, with sensitive data kept in the phone’s secure storage.

  • Notifications people want

    Permission asked for when it makes sense, not the moment the app opens, and messages sent only when there’s something to act on.

  • Accessible from the start

    Checked with each platform’s screen reader and larger text sizes as the app is built, not left to the end.

  • Private by default

    The app asks only for the permissions it needs, when it needs them. Its privacy details in each store match what it collects, and people can delete their account from the app.

Our work

Apps that carry the same information as the web product behind them.

  1. Sargasso’s live operations screen: vessel tracks and a predicted arrival on the harbour map, the berth schedule below with one conflict flagged, and a suggested plan with its reasoning for the duty officer to approve
    Sargasso’s crew app on three phone screens: today’s shift with the next berthing and tasks, Nordic Tern’s predicted arrival on the map, and the approved plan with a button to acknowledge it

    Port operations

    Sargasso Port Intelligence

    A berth-planning system combining vessel tracking, arrival predictions and scheduling support, with the duty officer in control of the plan.

    A companion app gives the quayside crew the same plan.

  2. Solenne’s quote screen for Geneva to London Luton: three aircraft priced side by side, the price broken down into aircraft, crew, landing fees and taxes, a curfew warning and the time left on the hold
    Solenne’s client app on three phone screens: the trip from Geneva to London Luton, the passengers and their documents, and the day of travel, with the car meeting the passengers at the aircraft

    Private aviation

    Solenne Air Charter

    A live quote engine that prices each aircraft with crew, landing fees and taxes broken out, and flags curfew or slot issues before anyone commits.

    The client app carries the trip through to the car on the tarmac.

  3. Aevum’s member portal: biological age against chronological age over the year, the biomarker panel with one result flagged, this week’s protocol, a note from the physician and the next appointment
    Aevum’s app on three phone screens: today’s protocol, the flagged marker explained in plain English, and messages with the physician

    Private healthcare

    Aevum Longevity Clinic

    A secure member portal behind the public site, bringing lab results and trends, the weekly protocol and physician messaging into one place, with a companion app that carries the daily protocol.

    A companion app carries the same protocol day to day.

  4. Belle Mare’s charter planner: a week of anchorages along the Croatian coast plotted on the chart, the day by day list beside it with cruising time and nights at anchor, and the button that sends the plan to the captain
    Belle Mare’s guest app on three phone screens: today’s anchorage and cruising time, the week’s itinerary, and a change request sent to the crew

    Yacht charter

    Belle Mare Yacht Charter

    A charter planner where guests build their week on the chart, with cruising time recalculated as they go and the finished itinerary sent to the captain.

    On board, a guest app carries the same plan day by day, with changes reaching the crew in one tap.

Explore our work

From first build to the stores

You’ll have working builds on your own phone from early on, through each store’s testing tools, so you can try the app as it takes shape. Store review is planned into the schedule, and new versions can roll out in stages, so a release can be paused early if something looks wrong.

Your app is published under your own developer accounts, and its code and signing keys are yours.

One release’s status, changing once per step: on your phone, then in review, then rolling out, while it can still be paused.

Kept current, year after year

Every year brings new versions of iOS and Android, new phones and new store requirements. Google Play stops offering apps that fall behind its target API level to new users on newer versions of Android, and Apple sets the SDK that new uploads must be built with. We plan for those changes ahead of time, so your app stays available and keeps working on new phones.

Then we keep improving it with you, or hand it over with the code, the accounts and the documentation.

Already have an app that’s fallen behind? We can review it, bring it up to date and look after it from there.

Work with us as a dedicated team, on a fixed price project or a mix of both.

Compare engagement models

Every yearYour app stays available and keeps working on new phones.

Let’s build it better

Tell us what the app needs to do, who it’s for and the systems it has to work with. We’ll talk through the options and a sensible first step.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}