iOS and Android mobile app development
Mobile development rarely costs much because of the code. It costs because of everything around it: developer accounts, review rules, operating system versions, and the real devices you have to check on.
One codebase, two stores
We build in React Native, which serves iPhone and Android from a single application codebase, with native bridges where they are needed. For the vast majority of business applications the difference from a native build is invisible to the user and is measured in months saved.
We recommend native development when the subject genuinely demands it: heavy video processing, specific sensors, games. Saying so in advance is part of the job.
- React Native, with native modules where the need justifies them
- Publication on the App Store and Google Play, accounts in your name
- Notifications, offline mode and deferred synchronisation
- Biometric authentication and encrypted on device storage
- Internal distribution for apps that do not go to a store
Store review, handled upfront
A rejection from Apple can cost two weeks of a launch date. The reasons are known and can be prepared for: justification of the permissions requested, an accessible privacy policy, account deletion from inside the app, payment going through the store where the rule requires it.
We address those points during design rather than while waiting for review. The first submission then becomes a formality instead of a gamble.
- Permissions justified and requested at the right point of the journey
- Account deletion built in, as the stores require
- Privacy policy and data collection declaration
- Support for the operating system versions still in circulation
- Acceptance testing on real devices, not only on simulators
Living after release
A mobile app ages faster than a website. Every year a major version of iOS and one of Android force adjustments, and an app that does not keep up ends up removed from the store. We take that follow up on, with a release rhythm agreed in advance rather than emergency catch ups.
- Tracking the annual releases of both systems
- Regular publication rather than emergency catch up
- Crash measurement and abandoned journey tracking
- Dependency and signing certificate maintenance
iOS and Android mobile app development
Do we really need two separate apps?
Rarely. A shared codebase covers both systems for most business and commercial applications. We recommend native when video processing, sensors or graphics performance justify it, and we say so before the budget is committed.
Who owns the store accounts?
You do. Apple and Google developer accounts are opened in your company's name and we work in them with delegated access. That is what lets you change provider without losing your app or its ratings.
Can an app and a website share the same foundation?
Yes, and it is often the right call. Server, database and business rules are shared, only the interfaces differ. It avoids the classic trap of two systems that drift apart within a year.
Mobile and web applications
Applications built to last, with a running cost known from the design stage.
In the division Mobile and web applications
Let us talk about what you want to build.
Describe your situation in a few lines. If it falls outside what we do well, we will say so immediately.
Get in touch