redplumm

Home › Mobile app development

Mobile app development

Native iOS and Android, plus cross-platform where one codebase genuinely beats two — with the offline behaviour, the push notifications and the store submissions handled for you.

Built for where the work happens

Most of the apps we build are not used on a sofa with full signal. They are used in a yard, a basement plant room, a field with one bar of reception, or a van between drops. That single fact drives almost every technical decision worth making, and it is the one most often skipped.

An app that assumes connectivity fails quietly and badly: the engineer fills in a form, hits save, sees a spinner, and loses twenty minutes of work. We build offline-first, so the device holds its own copy, the work continues regardless, and the sync reconciles when signal returns — including the unglamorous part, which is deciding what happens when two people edited the same record from two different dead spots.

Native, cross-platform, or both

We write native where native earns its keep: Swift for iOS, Kotlin and Java for Android. Heavy camera work, background location, Bluetooth hardware, tight battery budgets and anything that must feel immediate are all better native, and the gap is still real whatever the frameworks claim.

Where an app is mostly forms, lists and sync, one codebase across both platforms is the sensible answer and we will say so — it is less to build and half as much to maintain for the next five years. The choice is made on your requirements, not on what we happen to prefer writing.

The parts people forget to budget for

Shipping an app is not finishing an app. There are developer accounts to set up, signing certificates and provisioning profiles that expire at inconvenient moments, privacy nutrition labels and data-safety declarations to complete honestly, screenshots at the right sizes, and a review process that can reject you for something nobody mentioned.

We handle App Store and Google Play submission as part of the work, including the rejections. We also handle what comes after — operating system updates land every autumn and break things, and an app with no maintenance plan is an app with an expiry date.

It usually needs a back end

An app is rarely the whole system. There is normally a web side where the office sees what the field submitted, and a database that both talk to. We build those together so they actually agree with each other, rather than bolting an app onto something that was never designed to be synced against.

If the office side is the bigger half of your problem, web platforms and portals covers that, and systems integration covers connecting either to the software you already run.

How we start

With a working prototype on a real device, typically four to six weeks in — not a clickable mock-up. You hand it to the person who will use it every day and watch what they do with it, which tells you more in ten minutes than a specification does in a month.

After that it is a monthly commitment with unlimited developer time under fair use, so the app keeps growing with the business rather than freezing at version one. Store maintenance, operating system updates and support are inside that figure.

Related: custom software development, web platforms and portals.

Start with a conversation

The first meeting is free and its job is working out whether this is worth building at all. If it is, you will see a working prototype before any long-term money is discussed.

Book a slot   or call 020 4652 7504

Redplumm International Limited · United Kingdom, with a remote office in Johannesburg, South Africa