iOS & Android Apps
Native and Flutter apps for iPhone and Android, tested on real devices and released in careful phases.
Nummeropslag: who called?
Our free caller-ID apps for iPhone and Android identify unknown Danish numbers and flag spam, backed by a number lookup portal. Native Swift and Kotlin, in Danish, English and Ukrainian, released in phases on both stores.
A phone app is the most expensive way to reach your customers, and the most powerful one. It earns its cost when the phone has to do something a web page cannot: identify an incoming call, work in the background, show a widget, use the camera all day or send notifications people actually act on. If none of that applies, a web app is usually the better buy, and we will tell you so.
We build native apps in Swift and SwiftUI for iOS and in Kotlin with Jetpack Compose for Android when the app needs deep access to the system. When the app is mostly forms, lists and workflows, one Flutter codebase can serve iPhone, Android and the browser at once; we used Flutter for a construction company's subcontractor app. Behind the app we build and host the backend in Python with FastAPI, so one team answers for the whole chain.
Our own caller-ID apps for nummeropslag.dk show what this looks like in practice. On iOS, the call identification extension may use only 12 MB of memory, and loading about 658,000 numbers at once crashed it on some iPhones, which earned us one-star reviews. We reproduced the crash on a real device, then loaded the list in seven portions of 100,000; peak memory fell to 7.4 MB and the fix shipped as version 1.3.1. We also lowered the minimum iOS version from 17 to 15 so people with older iPhones, who are often the ones scammers call, can install it. On Android, the call screening role cannot be switched on by the app itself, so the first launch guides the user through the system dialog, with an extra step on Xiaomi phones. A test on a real Android 11 phone found two defects; they were fixed in 1.5.1, which went out to 20 percent of users first.
A mobile app starts from 10,000 DKK. After launch you pay the store developer fees in your own name, hosting of the backend, and work each time Apple or Google change their requirements. Our project support from 600 DKK per month covers monitoring, OS updates and small fixes.
An app is not the right choice when your users will open it twice a year, when the content changes daily and needs no phone features, or when your budget only allows one platform done properly. In those cases an installable web app or a good mobile website gets you further for the same money.
Key Features
Native Swift and Kotlin
SwiftUI on iOS and Jetpack Compose on Android for apps that use call identification, background tasks, widgets, extensions or the camera, where a shared framework would get in the way.
Flutter when it fits
One codebase for iPhone, Android and the web when the app is mostly forms and lists. Cheaper to build and change, and it can install straight from the browser.
Support for older phones
We decide the minimum OS version from who your users are, not from what is newest. The compiler checks every newer API is guarded, so older phones never hit a missing feature.
Backend from the same team
API, database and admin built and hosted by us in Python and FastAPI. When a screen is slow, there is no argument about whose side the problem is on.
Three languages built in
Danish, English and Ukrainian in the app, the store listing and the release notes. Every language is checked on a device, since long words break layouts that look fine in English.
Version control from the server
The backend knows the newest app version and can ask outdated installs to update, so you are not stuck supporting an old version that still talks to your API.
Why Choose This Service
Simulators do not enforce extension memory limits or vendor quirks, so we test on physical iPhones and Android phones before release.
Phased release on iOS and staged rollout on Android mean a defect is caught while most users are still on the previous version.
Store listings, reviews and signing keys live in your developer accounts, so you can change suppliers without losing the app or its ratings.
We read store reviews, reproduce the problem on a device and answer the reviewer once the fixed version is live.
How We Deliver
Our proven process ensures quality at every step
Decide native, Flutter or web
We list what the phone must do and who will use it. That decides the technology and whether a store app is needed at all, before design begins.
Clickable build on devices
Within the first weeks you install a working build through TestFlight or Google Play internal testing and use it on your own phone, not a video.
Device testing and store review
Automated UI tests run per language, then we test on physical phones, prepare screenshots, privacy answers and review notes, and handle Apple's and Google's questions.
Phased release
The new version goes to a share of users first. If crashes or bad reviews appear, the rollout pauses and the fix ships under a new build number.
Maintenance by the month
OS updates, new store rules, dependency upgrades and small fixes under project support, with a short note to you after each release.
Frequently Asked Questions
How long does it take to build an app?
It depends on the number of screens and integrations, so we give a timeline after the scoping talk rather than a guess. What we can promise is that you get a working build on your own phone early, and that each later step is something you can test, not a status report.
Native or Flutter: which should we choose?
Native when the app depends on system features such as call identification, extensions, widgets or heavy background work, because those are built for Swift and Kotlin first. Flutter when the app is mostly screens with data and you want iPhone, Android and web from one codebase. Flutter on the web is heavier than a normal web page, so for public pages that must rank in Google we use plain web technology.
Will Apple and Google approve the app?
Most rejections come from missing privacy answers, unclear permission texts or features reviewers cannot reach without an account. We prepare a demo login, review notes and permission texts in your languages before submission. If a review question comes back, we answer it and resubmit.
Can you update an app that is already in the stores?
Yes, as long as you control the developer accounts and the signing keys. We audit the code first and tell you whether to continue on it or rebuild parts. A new version keeps the listing, the reviews and the users, which is why taking over is often better than starting a new app.
What happens if Apple or Google change their rules?
Both change requirements every year, such as a new minimum Android target level or new privacy declarations. Under project support we follow those changes and ship the update before the deadline, so the app is not removed from the store or hidden from new users.
Ready to Cross the Bridge?
Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.