Mobile App Development Company in Amsterdam

Payment features are the fork in an Amsterdam app budget, because everything short of iDEAL and DNB supervision is comparatively predictable to estimate. Three builds are typical: a scoped MVP at Amsterdam rates over twelve to eighteen weeks, covering iOS and Android (cross-platform or thin-native), iDEAL plus Apple Pay plus Google Pay, App Store and Play submission, and a DPIA aligned with AP guidance, a production-grade native app with offline support, deep linking, push notifications, biometric onboarding, and full analytics, or a larger build with DNB-supervised payment features, custom backends, and EU Accessibility Act conformance. Amsterdam rates sit above Rotterdam and Utrecht because of the Booking.com, Adyen, and bunq talent premium. We give fixed-fee proposals rather than open T and M estimates, billed in EUR with Dutch BTW (21 percent) applied where required.

Yes. iDEAL is non-negotiable for any consumer app targeting Dutch users; it accounts for the majority of Dutch online payments and the new iDEAL 2.0 / Wero rollout under the European Payments Initiative is extending it across the EU. We integrate through Adyen, Mollie, Buckaroo, or Worldline acquirers depending on volume, ticket size, and SMB vs enterprise context. For in-app flows we use Adyen Drop-in or Components SDKs (the reference standard), Mollie SDK for hosted checkout, or direct iDEAL Quick Pay where the merchant has a Currence contract. Apple Pay and Google Pay are layered as alternatives for cross-border and Belgian (Bancontact) users. PSD2 / PSD3 strong customer authentication is enforced through the bank-side flow.

If your app handles citizen authentication for a Dutch ministry, gemeente, or public body, yes. DigiD is the Dutch national digital identity, run by Logius, and it is the required login mechanism for MijnOverheid, gemeente Amsterdam services, tax authority (Belastingdienst), DUO, UWV, and most public bodies. We integrate DigiD through the official Logius interface, handling SAML or OIDC depending on the version, plus eHerkenning when business identity is in scope. eIDAS cross-border identity is layered when EU citizen access matters. Every public sector engagement also conforms to the Tijdelijk besluit digitale toegankelijkheid (Dutch implementation of the EU Accessibility Act) with WCAG 2.1 AA as the baseline, AAA where feasible.

The EU Accessibility Act (EAA) came into force on 28 June 2025, transposed in the Netherlands through the Tijdelijk besluit digitale toegankelijkheid and related frameworks. It applies to consumer-facing digital services including e-commerce, banking, telecoms, transport ticketing, and e-books. Our mobile builds target WCAG 2.1 AA as baseline (with iOS VoiceOver and Android TalkBack tested end-to-end), large touch targets, scalable typography, sufficient colour contrast, captions on video, and keyboard navigation on hardware-keyboard-equipped Android. We deliver an accessibility statement, a conformance report, and a remediation roadmap. Non-conformance can be enforced by Dutch market surveillance authorities, and we have built remediation programmes for clients caught flat-footed by the deadline.

Native Swift and Kotlin remain the right choice when payment flows, biometric onboarding, AR, or deep OS integration matter; Booking.com, Adyen, and bunq run substantial native code for this reason. React Native fits when the same product team owns iOS and Android and the UI is screen-heavy rather than gesture-heavy; we have shipped React Native at scale for Dutch e-commerce and SaaS. Flutter fits when design fidelity must be pixel-identical across platforms and the team is comfortable with Dart. We will recommend honestly based on the team you actually have, the payment integration depth, and the OS feature exposure your roadmap needs, not based on which framework we want to bill more hours against.

We manage end-to-end submission including App Store Connect and Google Play Console setup, Dutch and English metadata, screenshots tuned for both languages, App Privacy declarations under Apple’s privacy nutrition labels, Google Play Data Safety form, EU DSA trader registration where required, and content rating questionnaires. For payment apps under DNB supervision we manage Apple’s External Purchase Link entitlement where it applies, and the EU Digital Markets Act (DMA) alternative app distribution flows for iOS in the EU when relevant. We also handle the new EU Trader Registration requirements that took effect February 2024 for any developer distributing paid apps or apps with in-app purchases in the EU.

Tikkie, run by ABN AMRO, is the dominant Dutch peer-to-peer payment request mechanism, using iDEAL behind a shareable link or QR. We integrate Tikkie through its API for B2C apps that need to send payment requests, and we build Tikkie-style flows for clients who want their own branded peer-payment experience under their existing iDEAL acquiring contract. For broader EU peer-payment, we integrate Wero (the EPI successor product) as it rolls out across Dutch, German, Belgian, and French banks. Bancontact is layered for Belgian users, and SEPA Instant Credit Transfer is wired for euro-area peer flows.

A typical Amsterdam fintech mobile app (iDEAL checkout, Apple Pay, Google Pay, biometric onboarding, KYC via eIDAS or Onfido, basic transaction history) takes sixteen to twenty-four weeks from kickoff to App Store and Google Play approval, assuming DNB licensing is already in place or scoped under an existing acquirer. Week 1 to 4 is discovery, DPIA, and design. Week 5 to 16 is build with TestFlight and Play Internal Testing from sprint one. Week 17 to 20 is store submission, App Privacy declarations, EU DSA trader registration, and DNB review where applicable. Week 21 onward is staged rollout. If full DNB payment institution licensing is part of scope, add three to six months for regulatory work in parallel.