Do we need separate iOS and Android builds?

Usually not two separate applications, but you should expect platform-specific work inside one codebase. Anyone quoting a single price for 'both platforms' without asking what the app does is quoting the easy four-fifths.

Mobile applications

Cross-platform where it makes sense, native where it does not

A cross-platform framework will carry roughly four-fifths of a mobile application and then stop. The remaining fifth is notifications that arrive when the app is closed, background work the operating system would rather kill, overlays that survive losing focus, and anything touching the secure element. That final fifth is what separates an app that feels native from one that feels like a website in a frame, and it is the part most quotes quietly omit. It is also where store review rejections come from.

What the work involves

Choosing cross-platform or native per feature, with the reasoning written down rather than assumed
Native modules in Kotlin or Swift for the capabilities JavaScript cannot reach
Push and background delivery designed against each platform's actual power-management behaviour
Offline behaviour decided deliberately — what is cached, what is queued, what simply refuses
One source of truth per piece of visible state, because a badge drawn in two places will eventually disagree
Store submission, review response, and a release process that separates over-the-air updates from store builds

Why we are credible at this

We build and ship the KamoCRM mobile client: React Native with Kotlin modules for overlay windows, background message delivery and device enrolment, distributed through both store releases and over-the-air updates.

What moves the price

We quote after discovery and the number is fixed before anything starts. These are the things that move it, so you can see roughly where your project sits before you talk to us.

How much of the application needs native capability rather than cross-platform code
Whether it must work offline, which changes the data architecture rather than adding a feature
Store review risk — some categories attract far more scrutiny than others
Whether you have an existing design system or the application needs one

Proof we have done this

A mobile application, in the storesReact Native with native modules where JavaScript will not do Our own video conferencingWebRTC media servers, TURN relays and the ICE path in between

Questions we get asked

Other App Development work

Custom web applicationsThe system your business actually runs on, built properly API and integration developmentMaking two systems agree, including the one with no documentation AI and retrieval systemsAssistants that read your documents, and know what they are not allowed to read Real-time systemsLive data, messaging, presence and media — the unforgiving end of the web

All App Development

Tell us what you are trying to do

A short conversation is usually enough to tell whether we are the right people. If we are not, we will say so and point you somewhere better.

Start a conversation I already use KamoCRM How we quote