Mobile app development for Danish businesses

When a Danish business needs an app

Many ideas that start as an app work better as a good mobile website. An app earns its place when people use it often, need push notifications, camera or offline access, or log in with a secure identity. Denmark has a high smartphone use and strong iPhone presence, but check your own analytics before choosing platforms. Our comparison of PWA vs native app covers the decision.

For most first versions we recommend one codebase in React Native or Flutter, shipped to both stores. A native build is worth the extra cost only for heavy graphics or deep device features. The mobile app service page explains our process.

Danish integrations to scope before design

None of these should surprise you in month three. We list them in the quote with the dependencies on your side.

Store rules that apply to Danish publishers

• Apple and Google both require privacy declarations in the store listing. We map every SDK and data type before submission so the declaration is accurate.
• For apps distributed in the EU, both stores ask the publisher to declare trader status and show contact details under the Digital Services Act. Check the current requirements in the developer consoles, and use the legal entity you want shown publicly.
• Danish store text is written for the listing, not machine-translated, with screenshots in Danish.
• Review times vary, so we plan the first submission well ahead of any campaign date.

Developer accounts stay in your name. We work with limited roles and you keep the keys.

GDPR, consent and accessibility

Datatilsynet applies GDPR to apps just as to websites. Analytics SDKs, crash reporters and advertising identifiers are the usual problem, since they process personal data on the device. The Danish cookie order covers storing or reading information on the user's device, so consent logic applies to apps as well. We include only SDKs you need and ask for consent before non-essential ones start.

The European Accessibility Act, in force since 28 June 2025, covers apps that deliver in-scope consumer services such as online shopping and banking. Some very small service providers are exempt, so check with your lawyer. We build for large text, screen readers, contrast and clear error messages, and we test with VoiceOver and TalkBack.

Testing for Danish users

An app that works in a developer's office can still fail on a train between Aarhus and Copenhagen. We test on a range of real iPhone and Android devices, on slow and dropped connections, and with the phone set to Danish. Specific checks include long Danish words in buttons, numbers written with a comma as the decimal separator, dates written day first, and a phone keyboard that offers æ, ø and å.

Before launch we run a closed beta through TestFlight and Google Play testing tracks with a small group from your side. Their feedback goes into a written list, and we fix what blocks launch first.

How a build runs from India

1. Discovery and quoteA call in the Danish morning, a feature list and a fixed quote within one working day.
2. Design and prototypeClickable screens in Danish for your approval before development.
3. Sprints with demosWeekly builds sent through TestFlight and Google Play internal testing, one project lead.
4. Store submissionListing text, privacy declarations, trader details and screenshots prepared with you.
5. After launchCrash monitoring, fixes and updates for new iOS and Android versions.

Calls usually sit between 09:00 and 14:00 Danish time, which is mid-afternoon in India.

Pricing

Projects start at $1,500, with extra work at $30 an hour. A small utility app sits near the bottom. Login with MitID, payments, an admin panel, offline mode and a back end each add scope. Store fees and payment provider fees are paid by you. The SaaS MVP cost guide gives ranges for a first product release.