HoiDutch for hi

Next.js developer in Amsterdam for accessible React front ends

I'm Maniruzzaman Jubayer, and if you need a Next.js developer in Amsterdam, I build React front ends for Dutch teams remotely, with accessibility in the code rather than in a report afterwards. We share 5 hours of your day, and I build for the European Accessibility Act, WCAG 2.2 and the move from iDEAL to Wero.

Free 30 min intro call · One fixed quote · No retainer

Amsterdam canal houses with bicycles along the railing
Amsterdam--:--
My desk--:--

5 hours of your day shared

SaaS, fintech and AI teams work with me

Raised by my clients
$30M+
Monthly visits on client platforms
10M+
Client satisfaction in project reviews
90%
Companies helped
50+
Years building web and mobile apps
6+
Behance features
20+

Trusted by teams at

  • boon
  • Asendia AI
  • sitecove
  • mergepoint.ai
  • Parfait Art Logistics
  • oneclick

Where Dutch front ends fall short

The rules caught up with the code in 2025, and the payment rails change through 2026 and 2027.

A tree-lined Amsterdam canal under a summer sky

Since 28 June 2025, e-commerce services in the Netherlands must be accessible, and the ACM enforces it for businesses above 10 staff or €2 million turnover. Many React apps were never built for keyboards or screen readers. I fix that in the components, then guard it in CI.

Interfaces I designed for real products

A mobile wallet for sending, receiving and tracking money, one dashboard for a real estate operation and a hospital management dashboard: dense interfaces of the kind I build in code.

  • ZenPay: A mobile wallet for sending, receiving and tracking money

    Product design · Fintech

    ZenPay

    A fintech app for payments, expense tracking and budgets, with its research, user flow and UI design.

    Read the case study →
  • Emura: One dashboard for a real estate operation

    Product design · Real estate

    Emura

    Properties, agents, customers and revenue analytics brought together in one web platform for real estate managers.

    Read the case study →
  • Mediso: A hospital management dashboard

    Product design · Healthcare

    Mediso

    Patients, appointments, staff and departments managed from one healthcare admin platform.

    Read the case study →

Can a keyboard user finish your checkout? Let's make sure they can.

Hoi, let's talk

WCAG web app development: what I build for Dutch teams

React and Next.js front ends with the Dutch rules and payment rails built in.

  • 01

    Accessible components

    Semantic HTML, focus management, keyboard paths and screen reader testing, built to WCAG 2.2 AA in your component library rather than patched page by page.

  • 02

    Accessibility checks in CI

    Automated checks on every pull request plus manual keyboard and screen reader passes before release, so a regression is caught in review, not by the regulator.

  • 03

    iDEAL and Wero checkout

    Payments through Mollie, Adyen or your provider, with iDEAL | Wero branding, redirects, pending and failed states handled, and a plan for the full move to Wero.

  • 04

    Dutch and English, properly

    Internationalised routing, dates, numbers and currency, with content your team can edit in its CMS without waiting for a developer.

  • 05

    Cookie consent to the AP's guidance

    A consent layer where reject sits beside accept on the first screen and takes no extra clicks, with tracking scripts blocked until someone opts in.

  • 06

    A clean handover

    Typed, tested and documented code in your repository, a walkthrough with your developers and no lock-in. How I choose a stack: Framer, Webflow or Next.js.

How a Dutch build runs, step by step

Four steps from the first call to code in your main branch.

  1. 01

    Free 30 minute intro call

    We talk on Google Meet in your morning. Share the repository or the URL, the screens that worry you for accessibility and your payment set-up, and I will tell you what I see.

  2. 02

    Written scope and one fixed quote

    A technical scope covering the components, the WCAG 2.2 AA work, the checkout and the languages, with one fixed quote for the whole build. No retainer, no hourly billing.

  3. 03

    Build sprints in your repository

    Weekly sprints with pull requests your developers review, accessibility checks on every merge and a written update in Slack every 48 hours.

  4. 04

    Release and handover

    A keyboard and screen reader pass before release, documentation for your team and a walkthrough, so your developers own the code from the first day.

Working with me from Amsterdam

Languages
English in meetings and code reviews; interfaces in Dutch and English, with Dutch copy from your team
Shared hours
5 hours of your day; I am 4 hours ahead of Amsterdam in summer time and 5 in winter
Working week
Monday to Friday, planned around who on your team works which days
Ways to talk
Slack, Google Meet and pull request reviews in your repository
Stack
React, Next.js and TypeScript, deployed to EU regions

How I work with your team in Amsterdam

Remote, inside your repository and your rhythm.

Amsterdam12:00
Me17:00

We can talk now

Your day My day Shared

  • 01

    You talk to the developer

    You speak to me, the developer writing your code, in Slack and in pull request comments. No project manager relays your questions, so a review comment gets its reply from the person who wrote the line.

  • 02

    Shared hours and the Dutch week

    I am four hours ahead of Amsterdam in summer and five in winter, so we share 5 hours of your day. The Netherlands has the EU's highest share of part-time work, so I plan reviews around who on your team is in on which day.

  • 03

    Everything in the repository

    Work arrives as pull requests with notes, decisions live in the tickets, and you get a written update in Slack every 48 hours plus a weekly call. Nothing important lives only in someone's head.

  • 04

    I know the Dutch rules and rails

    I build for the European Accessibility Act and the ACM's enforcement, the AP's cookie banner guidance, iDEAL and its move to Wero, and Dutch and English content. Your legal team confirms which obligations apply.

What Amsterdam builds, and what its front ends need

Dealroom counts 26 unicorns in Amsterdam, and the Noord- and Zuid-Holland region takes more than 70% of Dutch venture capital. These sectors set the bar for the city's web apps.

  • Payments: a screen from a product I designed

    Payments

    Adyen and Mollie are Amsterdam names, and iDEAL carries most Dutch online purchases. Checkout front ends need every redirect, timeout and failed payment handled and tested, plus a smooth path to Wero.

    My fintech work →
  • Banking software: a screen from a product I designed

    Banking software

    Mambu, one of the city's best-funded companies, builds banking software. Consumer banking services fall under the EAA, so dense account and transaction screens still have to work by keyboard and screen reader.

    My fintech work →
  • Travel and hospitality: a screen from a product I designed

    Travel and hospitality

    Booking.com and Mews are among the city's biggest names. Booking flows serve every language and device, so they need fast pages, clear dates and prices, and forms a screen reader can complete.

  • Grocery and delivery: a screen from a product I designed

    Grocery and delivery

    Picnic is Amsterdam's best-funded startup by Dealroom's count. Delivery apps need live tracking, delivery slots that are easy to change and an order history people can read on a small phone.

  • Mobility and clean energy: a screen from a product I designed

    Mobility and clean energy

    The State of Dutch Tech 2026 counts mobility and cleantech among the country's strongest sectors. Their apps need maps, live charging or trip status, and payments that work outdoors on a phone.

  • AI products: a screen from a product I designed

    AI products

    The same report points to the region's strong AI talent. AI front ends need streamed answers a screen reader can follow, visible sources, and controls to stop, retry or correct the output.

    My ai products work →

Who I help in Amsterdam

Four kinds of Dutch teams I am set up to build for.

That sounds like you?

Funded startups shipping fast

Seed and Series A teams with a product in market and more roadmap than developers. I add senior React and Next.js capacity that works in your repository from the first week.

Talk it through on a free call

Hiring a Next.js developer in Amsterdam: in-house, a freelancer or me

The honest trade-off for a Dutch product team, including where a hire is the better choice.

What you getWith meIn-house hireFreelancer
Senior React developers in your repository within daysYesNoSometimes
One person for the design and the React buildYesNoNo
WCAG 2.2 AA built into components and checked in CIYesSometimesSometimes
Checkout code planned for the iDEAL to Wero moveYesSometimesSometimes
Speaks Dutch in stand-upsNoYesSometimes
Scales with the roadmap, without a contract to unwindYesNoYes
A single fixed quote, agreed before the first sprintYesNoSometimes

What clients say about working with me

“The final product exemplified Muhammed’s profound comprehension of UI design principles, presenting a visually captivating experience that was both seamless and intuitive for users.”
Youssef RzikiClient, oil and gas trade
01 / 02

A good front end starts with a clear design, and I do both.

Development in other cities

Guides for Dutch product teams

Notes from my own projects on stacks, dashboards and accessible interfaces.

Next.js developer in Amsterdam: frequently asked questions

Answers on the EAA, Wero, languages and working with me remotely.

Still have a question?

Ask me on a free 30 minute call, in Amsterdam time.

Ask me on a free call
  • The number of screens and components, how much accessibility repair the current front end needs, the payment and identity integrations, the languages, and whether I design as well as build. After a free 30 minute intro call I write a technical scope and give you one fixed quote for the whole build, with no retainer and no hourly billing.
  • If you sell products or services online to Dutch consumers, it may. Since 28 June 2025 e-commerce services must be accessible, with the ACM supervising them and the AFM covering banking and financial services. Very small businesses, at or under 10 staff and €2 million turnover, are exempt. Your legal team confirms the scope; I build the front end to meet it.
  • Because 2.2 is where it is heading. EN 301 549 version 4.1.1, published in September 2026, adopts WCAG 2.2, although version 3.2.1 with WCAG 2.1 AA stays the reference until the Commission cites the new one in the Official Journal. Building to 2.2 AA now covers both and saves a second pass later.
  • It moves onto Wero in stages, and your checkout has to follow. In early 2026 merchants switched to iDEAL | Wero branding. From October 2026 every Dutch issuing bank is connected to Wero and payments start moving onto it, with the migration due to finish by 31 December 2027. I update your checkout through Mollie, Adyen or your provider and test every outcome along the way.
  • Yes. The Autoriteit Persoonsgegevens wants reject and accept on the same layer, declining to take no more clicks than accepting, and withdrawing consent to be as easy as giving it. I build exactly that, block tracking scripts until people opt in, and your privacy lead approves the wording.
  • Often both. The Netherlands ranks first in the EF English Proficiency Index 2025, so many B2B teams launch in English, while consumer products usually earn trust faster in Dutch. I internationalise the app from the start, so adding Dutch later is content work rather than a rebuild.
  • Yes. Send me the audit and the URL. I group the findings by component, fix the root causes in your design system so the same issue does not come back on every page, and re-test by keyboard and screen reader. You get a short record of what changed, ready for your accessibility statement.
  • Neither. I am not a Dutch company and have no Amsterdam office; I work with you remotely. You hire one accountable person, and I work in your repository, answer your pull request comments and share 5 hours of your day. The build is scoped in writing and priced as one fixed quote before the first sprint. The same set-up covers UI/UX design in Berlin and fintech UX in London.
  • Book a free 30 minute intro call in Amsterdam time. Share the URL or the repository and the screens you worry about, often the checkout or the sign-up form, and I will tell you on the call where the accessibility gaps are likely to be. The technical scope and one fixed quote follow.

Hoi

Accessible for every visitor, ready for Wero

Pick a time that suits your day in Amsterdam. Thirty minutes on your product and your deadline, and you leave knowing whether I am the right fit.

  • Free, 30 minutes, on Google Meet
  • Times shown in your own time zone
  • A written scope and one fixed quote after the call
Sources and references (13)
  1. Dealroom, Amsterdam deep dive (26 unicorns; Booking.com and Adyen decacorns; top funded: Picnic, Bird, Mollie, Mews, Mambu), accessed 3 October 2026: dealroom.co
  2. I amsterdam, State of Dutch Tech 2026 (AI, fintech, mobility, cleantech and deeptech; Noord- and Zuid-Holland take more than 70% of venture capital; strong AI talent base), 12 February 2026: iamsterdam.com
  3. ACM, ACM calls on businesses to prepare for new rules on the accessibility of websites and apps (from 28 June 2025; e-commerce and electronic communication services; businesses with more than 10 staff or EUR 2m turnover), 5 June 2025: acm.nl
  4. Business.gov.nl, Rules for accessibility of products and services (EAA; ACM, AFM and CvdM supervise; accessibility statement; micro-enterprise exemption), accessed 3 October 2026: business.gov.nl
  5. AccessibleEU (European Commission), EN 301 549 has been updated (v4.1.1 adopts WCAG 2.2; v3.2.1 based on WCAG 2.1 AA remains the reference until cited in the Official Journal), September 2026: accessible-eu-centre.ec.europa.eu
  6. European Payments Initiative, Successful first phase marks major next steps in iDEAL to Wero migration (co-branding earlier in 2026; all Dutch issuing banks connected in October 2026; migration complete 31 December 2027), 15 July 2026: epicompany.eu
  7. Mollie, What is Wero (iDEAL | Wero co-branding in early 2026; iDEAL phased out by late 2027), accessed 3 October 2026: mollie.com
  8. Dutch Payments Association, Online payment methods (72% of online purchases via iDEAL), accessed 3 October 2026: betaalvereniging.nl
  9. EF, EF English Proficiency Index 2025 launched (the Netherlands remains first), 19 November 2025: ef.edu
  10. Autoriteit Persoonsgegevens, Clear cookie banners (reject and accept on the same layer; declining no more clicks than accepting; withdrawal as easy as consent), accessed 3 October 2026: autoriteitpersoonsgegevens.nl
  11. Eurostat, Part-time and full-time employment statistics (the Netherlands has the highest share of part-time workers in the EU, 38.6% in 2024), accessed 3 October 2026: ec.europa.eu
  12. Rijksoverheid, Waarom wordt de klok 2 keer per jaar verzet (clocks change on the last weekend of March and October, EU-wide), accessed 3 October 2026: rijksoverheid.nl
  13. Wikipedia, Bangladesh Standard Time (UTC+06:00, no daylight saving), accessed 3 October 2026: en.wikipedia.org

City photos from Unsplash.