One app for Android and iPhone, with the backend that powers it and the panel you run it from. We build every part, so you don't have to coordinate three teams.
A mobile app is a big investment, both to build and to maintain. That's why we first check whether you really need one - and when you do, we build it so one codebase runs on both operating systems.
01
Do you really need an app?
An app makes sense when users come back to it several times a week, when push notifications matter to you, or when it uses the camera, location, Bluetooth or offline mode. Examples are loyalty apps, booking, field work or order tracking.
If people open your content once or twice a year, they won't install an app. In that case a well-built website or a web application that opens in the phone's browser is the better choice.
02
React Native or Flutter
We work with both. Each lets you build an app for Android and iOS from one codebase, so development and maintenance cost less than two separate apps.
React Native is the natural choice when you already have a web application in React, because some knowledge and code can be shared. We choose Flutter when the app has many custom animations and a bespoke look that must be identical on every phone. When a feature neither of them covers is needed, we write that part natively for Android or iOS.
03
Backend, API and admin panel
Almost every app needs a server: for user accounts, data, payments and sending notifications. We build it on Symfony and an API your website or partners can use later as well.
It comes with an admin panel where your team edits content, sees users and orders and sends notifications - without a new app release for every small change.
04
Login, notifications and analytics
Users sign in with email, a Google or Apple account, and can sign back in with a fingerprint or face recognition. We send targeted push notifications based on what the user did, because mass messages quickly lead to notifications being turned off or the app being deleted. How we build notifications and chat is described on our real-time chat and notifications page.
We set up analytics so you can see which features people use, where they drop off and when they come back. We plan the next versions based on that.
05
App store release - and after
We prepare the app for the App Store and Google Play and take it through their reviews. For the store listing we work on the name, description, keywords and screenshots, because they determine whether people find and install it. That's called ASO, app store optimization.
After release the app needs maintenance: Apple and Google release new OS versions every year and change their rules, so an app that isn't updated eventually becomes unavailable to new users or is removed from the store. How we handle that is described on our website and application maintenance page.
Mobile apps are part of our development services, alongside web applications and websites that often share the same backend.
FAQ
Questions about mobile app development
Usually not. With React Native or Flutter, one codebase runs on both platforms, and we only write separate code for the parts that require it.
It depends on the number of screens and features, whether you already have a backend and which systems the app connects to. You get an estimate once you describe what the app should do.
We agree on that before release. The app can be published on your own Apple and Google developer accounts, and we help you set them up.
App store optimization: optimizing the app's page in the App Store and Google Play - the name, description, keywords and images. Like SEO, but for app stores.
We test the app on the new version and fix whatever is needed before users notice a problem. The scope of that is agreed as part of maintenance.
Planning a mobile app?
Tell us who would use it and what they would do in it. We'll tell you whether you need an app and how we would build it.