Mobile App Development Company in Amsterdam

A focused MVP is in both stores 8 to 14 weeks after kick-off, with the Dutch and English versions submitted together. Add a custom backend and third-party integrations and you are looking at 3 to 6 months. Payments and health builds with DNB, AFM or NEN 7510 requirements, multiple roles and legacy integrations usually run past 6 months, and we sequence them against your season or pilot date. A new build lands on your phone every two weeks regardless.

No, and we say so plainly. Appther is remote-first, with registered entities in the United States, India and Australia and no Dutch office. Our engineering team's hours overlap the CET working day, so stand-ups, demos and escalations happen while your office is open, and one named senior engineer runs your project from the first workshop to the store release. Quotes, contracts and invoices are in euros.

Yes, and we recommend deciding that in discovery rather than after launch. Bilingual delivery means string tables instead of hard-coded text, layouts sized for the longer language, locale-aware dates, numbers and currency, Dutch parity on consent and privacy screens, bilingual QA and store listings in both languages. German and French can be added on the same foundation.

Yes. We integrate iDEAL and Wero through a licensed PSP such as Adyen or Mollie, build SEPA Direct Debit mandates and refunds with a reconciled ledger, design PSD2 strong customer authentication into every payment flow, and connect open-banking data through DNB-licensed providers. Licensing and reporting to DNB or the AFM remain with you; the product and its documentation are built to support them.

Compliance is mapped with your privacy officer in discovery and engineered into the product. For GDPR that means a lawful basis for each processing activity, a data-protection impact assessment where one is needed, data-subject rights flows, processing agreements with every sub-processor and 72-hour breach readiness. For cookies and tracking it means real consent before anything fires, no cookie wall and a reject option as easy as accept, which is the standard the Autoriteit Persoonsgegevens enforces. Controls are documented as they are built, so the regulator can retrace them.

In the EU by default: Azure West Europe, whose data centres are in the Amsterdam area, or AWS Frankfurt, inside your own cloud account with backups that stay in region. Where engineering happens outside the EU we document the transfer safeguards your privacy officer will ask for, and production data never leaves the EU without your written agreement.

Everything is yours by contract: the repositories sit under your organisation, the App Store and Google Play accounts are in your company's name, and the infrastructure runs in your own tenancy. An NDA is signed before discovery, intellectual property passes to you as each invoice is paid, and taking the work in-house later means revoking our access and nothing more.