Mobile App Development Company in Copenhagen

Cost tracks scope. A scoped Copenhagen MVP on a single platform (iOS or Android) runs twelve to twenty weeks, covering UX, native build, MitID and MobilePay integration, backend API, and store submission. A cross-platform React Native or Flutter MVP across iOS and Android covers the same scope and is often a better economic call for early-stage Copenhagen startups outside the regulated banking space. Full production apps add neobank flows, brokerage, e-Boks integration, or PSD2 SCA plus ongoing maintenance. Copenhagen rates sit roughly ten to fifteen percent below Stockholm because the talent market is slightly cheaper but well above Aarhus or Aalborg because of the Pleo, Lunar, and Trustpilot talent premium. Denmark uses Danish Krone (DKK is pegged to the Euro through ERM II at roughly 7.46 per EUR), so we quote in DKK and fix the Euro-equivalent on contract signing. Fixed-fee proposals per release, not open time-and-materials.

MitID is the Danish national digital identity, launched October 2022 by Digitaliseringsstyrelsen and the Danish banks to replace NemID. It is mobile-first by design — most Danes use the MitID app on their phone as the primary authenticator, with code-display or chip alternatives for accessibility. For mobile apps, you do not integrate with MitID directly. You contract a certified broker — Signicat, Criipto, or Nets are the common Copenhagen choices — that fronts the MitID Broker scheme on your behalf and shields you from the underlying SAML and OIDC complexity. Same-device flows launch the MitID app via URL scheme, the user confirms with PIN or biometrics, and your app receives a signed assertion containing CPR or pseudonymous identifiers depending on your data minimisation profile. Cross-device flows use code transfer. We implement both, store the absolute minimum personal data, and log every authentication so Datatilsynet GDPR audits do not turn into incident reports. Email-and-password is never a default in Denmark.

MobilePay was launched by Danske Bank in 2013 and merged with Norway's Vipps in 2022 to form Vipps MobilePay, now jointly owned by Danske Bank and DNB. It is the dominant Danish mobile payment app, used by the overwhelming majority of Danish consumers for peer-to-peer transfers, retail checkout, and SME invoicing. For mobile apps, you integrate via MobilePay Online (e-commerce, in-app payments) or MobilePay Point of Sale (in-store). Integration requires a MobilePay agreement with your acquiring bank, production credentials, and IP whitelisting. We handle the bank paperwork, build the m-commerce flow with deep links that hand off to the MobilePay app and return with a signed payment token, and ship the webhook handler for asynchronous settlement. MobilePay typically beats card payments on Danish conversion by ten to twenty percentage points for B2C checkout, and the fee structure is materially cheaper than Visa or Mastercard interchange for most Copenhagen merchants. Apple Pay and Google Pay are still implemented for international users.

e-Boks is the Danish digital mailbox — every Danish resident over 15 is required to have a Digital Post account (provided through e-Boks or mit.dk), and state, municipal, and major-bank communications sent through it have full legal validity, equivalent to registered post. For citizen-facing mobile apps in public sector, banking, insurance, utilities, healthcare, and pension, e-Boks integration is essentially mandatory — that is how Danes expect to receive legally binding communications. Integration uses the e-Boks Print API (you post a document, the citizen receives it in their e-Boks inbox) and the e-Boks Receive API (the citizen posts a reply or document, you receive it). Authentication is via certificate, and the underlying identity is MitID. We have built e-Boks integrations for KOMBIT-procured public-sector apps and Finanstilsynet-regulated insurance clients, including delivery receipt handling, retry logic, and the audit logging required for the legal-validity guarantee to hold.

Denmark does not have its own AWS, Azure, or GCP region, so the standard choices are AWS eu-west-1 (Dublin) or eu-central-1 (Frankfurt), Azure West Europe (Amsterdam) or North Europe (Dublin), and GCP europe-west1 (Belgium) or europe-north1 (Hamina, Finland) — all EU regions with low latency from Copenhagen and a clean answer for Datatilsynet residency questions. Datatilsynet is one of the strictest data-protection regulators in the EU and has issued significant fines for sloppy sub-processor handling, so we document data flows in a GDPR Article 30 record-of-processing template Datatilsynet would accept on inspection, run a Transfer Impact Assessment if any sub-processor sits outside the EU, and use Standard Contractual Clauses plus supplementary technical measures (encryption at rest with EU-controlled keys via AWS KMS or Azure Key Vault) where US-headquartered sub-processors are unavoidable. For Finanstilsynet-regulated apps we add signed audit logs and quarterly third-party penetration tests.

For Copenhagen fintech, neobank, and insurance apps with deep MitID, MobilePay, e-Boks, and PSD2 SCA integration, we usually recommend native — Swift and SwiftUI on iOS, Kotlin and Jetpack Compose on Android. The certificate handling, biometric prompts, secure-enclave usage, and broker SDK interaction are materially easier and less buggy in native code, and Finanstilsynet audits go more smoothly when the security-sensitive layer is platform-idiomatic. For consumer apps, marketplaces, SaaS-companion apps (the Trustpilot, Templafy, Famly pattern), and B2B tools, React Native (with Hermes and the New Architecture) or Flutter ship sixty to seventy percent faster on a single codebase and the user-perceptible quality gap is essentially gone in 2025 if the team is competent. Pleo and Lunar both ship significant cross-platform surface in production. We recommend the stack against your scope, team, and budget rather than the one that grows our hours.

Denmark implements the EU Accessibility Act (Directive 2019/882) through the Danish Web Accessibility Act extension, in force from 28 June 2025 for consumer-facing mobile apps in banking, e-commerce, transport, telecoms, audiobooks, e-readers, and emergency communications. Required conformance is WCAG 2.1 Level AA equivalent, with documented assistive-technology support — VoiceOver on iOS, TalkBack on Android, dynamic type, sufficient contrast, captions and transcripts for audio and video, and keyboard or switch navigation where the platform supports it. Enforcement sits with sector regulators (Erhvervsstyrelsen for retail, Finanstilsynet for banking, Energistyrelsen for telecoms). Denmark has historically been an early enforcer on digital accessibility, so we bake accessibility into design from the first wireframe, run automated axe-core and Accessibility Inspector scans every build, do a manual screen-reader pass on every release candidate, and ship a written conformance statement that matches the European Commission templates from 2024 and 2025.

Yes — and for Danish apps it matters more than most markets. MitID is on a continuous-evolution roadmap and Signicat, Criipto, and Nets push broker SDK updates regularly. MobilePay ships API and SDK changes on its own cadence. e-Boks and mit.dk both evolve. iOS and Android force major SDK and target-API migrations annually. The EU Accessibility Act 2019/882 conformance obligation is continuous, not one-off. Datatilsynet expects you to keep your Article 30 record current. Our standard maintenance retainer covers OS-version compatibility (we test against the latest two iOS and Android versions Apple and Google still sign), MitID broker, MobilePay, and e-Boks API upgrades, dependency and CVE patching within agreed service levels, crash and ANR triage from Crashlytics and Sentry, store-listing optimisation in Danish and English, accessibility-regression testing, and one minor feature release per quarter. Retainers run from DKK 28,000 per month for maintenance-only up to DKK 120,000-plus per month for an embedded team with active roadmap delivery.