Mobile apps

Native apps in Swift and Kotlin give the fullest access to device features and the closest fit to each platform. Cross-platform apps in React Native or Flutter share most of their code between iOS and Android, which lowers the cost of building and changing them. We recommend native when the app depends heavily on the device, such as payment hardware or complex media, and cross-platform for most business and consumer apps.

The number of journeys and screens, whether you need a native app for each platform or one cross-platform app, the back-end work, and the security the app needs. Offline use, payments, device features and the range of devices to support add effort. Store releases and keeping up with new operating system versions are ongoing costs to plan for.

We keep keys and tokens in the platform’s hardware-backed secure storage, never in plain files. We use certificate pinning, biometric or device-bound sign-in, and server-side checks for every sensitive action. Where the risk calls for it, we add detection of rooted or jailbroken devices and tampered builds. We follow the OWASP Mobile Application Security guidance and can support an external penetration test before launch.

Yes. We prepare the listings, manage signing keys and certificates, submit builds for review and release in stages, so a problem reaches few users. The developer accounts stay in your organisation’s name, so you own the apps and their listings. We work under your accounts with access that you grant and can revoke.

Yes, where the journeys allow it. We store the data the user needs on the device, encrypted, and queue their changes until the connection returns. Sync rules decide what happens when the same record changed in two places. We design those rules with you, because they are business decisions as much as technical ones.

Apple and Google release new operating system versions every year, and store rules change. Libraries need security updates. We test the app against each new release, fix what changes and keep its dependencies current, alongside your own roadmap of features. This usually runs under a support agreement or within a dedicated team.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.