Relegacy

Mobile app development

Mobile apps for your staff and the public.

We design, build and release iPhone and Android apps, then keep them current. New apps from scratch, or an aging app rebuilt on a modern framework with the features and data your users rely on.

Discuss an app APIs and integrations
Before: a 2014 hybrid inspection app on an old Android phone, showing a sync failure. After: the same inspection rebuilt in React Native on an iPhone and an Android phone, working offline with photos and a checklist.
An aging hybrid inspection app rebuilt for iPhone and Android. Illustrative example with fictional data.

New apps and app refreshes

New

A new app

From an idea or a paper process to an app in the stores: field inspections, work orders, resident requests, permits, payments, events or internal tools.

Refresh

An existing app, rebuilt

Apps built with Xamarin, Cordova, PhoneGap or older native code, rebuilt on a current framework. Features, rules and records carry over, and old problems like failed syncs do not.

Extend

A mobile front end for an old system

A modern app for staff or residents that works with your existing back-office system through a secure API, while that system is replaced in stages.

From design to continuous updates

01Design

User research, wireframes and an interface that follows Apple and Google guidelines and accessibility standards.

02Build

Development in short cycles with working builds you can try on your own phones, and automated tests on every change.

03Release

Signed builds, beta testing, and App Store and Google Play submission, or private distribution to your organization's devices.

04Continuous updates

New features, operating system and security updates, crash monitoring and store maintenance on an agreed plan.

Four panels: a wireframe and design tokens, React Native code with tests, a release pipeline submitting to the App Store and Google Play, and a release history of ongoing updates.
The lifecycle of an app: design, build, release and continuous updates. Illustrative example.

Cross-platform or native

We recommend the approach that fits the app, and explain the tradeoffs before you commit.

React Native

One TypeScript codebase for iPhone, iPad and Android. The right fit for most business and public-facing apps, with lower build and maintenance cost.

Kotlin for Android

Fully native Android apps for deep device features such as Bluetooth equipment, background location or rugged field devices.

Swift for iOS

Fully native iPhone and iPad apps for demanding performance, widgets or a design built entirely around iOS.

Left: a shared React Native screen shipped to the App Store, Google Play and managed devices. Right: native Kotlin and Swift code reading a Bluetooth water meter.
One shared codebase for both stores, and native Kotlin and Swift where an app needs it. Illustrative code.

What you receive

Connect the app to your systems

Most apps need data from somewhere: a CRM such as Salesforce, a payment provider, GIS or a legacy database. We build the APIs and integrations too. See custom development.

Discuss an app