Next.js developer in Amsterdam, Netherlands
Next.js developer in Amsterdam for accessible React front ends
I'm Maniruzzaman Jubayer, and if you need a Next.js developer in Amsterdam, my team builds React front ends for Dutch teams remotely from Dhaka, with accessibility in the code rather than in a report afterwards. We share 6 hours of your day and build for the European Accessibility Act, WCAG 2.2 and the move from iDEAL to Wero.
With the ACM enforcing accessibility, it belongs in every pull request, not a yearly audit.
Free 30 min intro call · One fixed quote · No retainer
SaaS, fintech and AI teams work with me and my developers
- Years leading a design team
- 3+
- Products shipped
- 20+
- Behance gallery features
- 22
- Clutch rating
- 5.0
Product designer and design lead, with a senior team behind me
Where Dutch front ends fall short
The rules caught up with the code in 2025, and the payment rails change through 2026 and 2027.
Problem 01
The ACM now checks accessibility
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. My team fixes that in the components, then guards it in CI.
Problem 02
iDEAL is becoming Wero
iDEAL carries about 72% of Dutch online purchases, and from October 2026 it starts moving onto Wero, with the migration due to finish by the end of 2027. My developers build the checkout so the brand, the flow and the edge cases can change without a rewrite.
Problem 03
Two languages, one codebase
The Netherlands tops the EF English Proficiency Index, so many teams ship in English first, but Dutch customers still expect Dutch. My developers internationalise from day one: routes, dates, currency, plurals, and content your team can edit without a deploy.
Problem 04
Hiring against Europe's best-funded teams
With 26 unicorns in the city, Adyen and Booking.com among them, you are hiring senior front-end developers against some of Europe's best-funded teams. My team joins your repository within days of an agreed scope and leaves code your own developers want to keep.
Interfaces my team 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 my developers build in code.
Product design · Fintech
ZenPay
A fintech app for payments, expense tracking and budgets, with its research, user flow and UI design.
View case study →
Product design · Real estate
Emura
Properties, agents, customers and revenue analytics brought together in one web platform for real estate managers.
View case study →
Product design · Healthcare
Mediso
Patients, appointments, staff and departments managed from one healthcare admin platform.
View case study →Can a keyboard user finish your checkout? Let's make sure they can.
Hoi, let's talkWhat my developers build for Dutch teams
React and Next.js front ends with the Dutch rules and payment rails built in.
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.
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.
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.
Dutch and English, properly
Internationalised routing, dates, numbers and currency, with content your team can edit in its CMS without waiting for a developer.
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.
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.
- 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.
- 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.
- 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.
- 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 my team from Amsterdam
- Languages
- English in meetings and code reviews; interfaces in Dutch and English, with Dutch copy from your team
- Shared hours
- 6 hours of your day; Dhaka is 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
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
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.
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.
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
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
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
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.
How my team works with yours in Amsterdam
Remote from Dhaka, inside your repository and your rhythm.
You talk to the developers
You speak to me and to the developers 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.
Shared hours and the Dutch week
Dhaka is four hours ahead of Amsterdam in summer and five in winter, so we share 6 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.
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.
We know the Dutch rules and rails
My team builds 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.
With my team, an Amsterdam hire or a freelancer
The honest trade-off for a Dutch product team, including where a hire is the better choice.
| What you get | With me | In-house hire | Freelancer |
|---|---|---|---|
| Senior React developers in your repository within days | Yes | No | Sometimes |
| One team for the design and the React build | Yes | No | No |
| WCAG 2.2 AA built into components and checked in CI | Yes | Sometimes | Sometimes |
| Checkout code planned for the iDEAL to Wero move | Yes | Sometimes | Sometimes |
| Speaks Dutch in stand-ups | No | Yes | Sometimes |
| Scales with the roadmap, without a contract to unwind | Yes | No | Yes |
| A single fixed quote, agreed before the first sprint | Yes | No | Sometimes |
Who my team helps in Amsterdam
Four kinds of Dutch teams we are set up to build for.
Funded startups shipping fast
Seed and Series A teams with a product in market and more roadmap than developers. My team adds senior React and Next.js capacity that works in your repository from the first week.
Scale-ups facing an accessibility review
Companies selling online to consumers that now fall under the EAA. We audit the front end, fix the components that fail and add checks so every new feature stays accessible.
Payments and checkout teams
Teams preparing for the iDEAL to Wero move, or rebuilding a checkout. We handle every redirect, pending and failed state, in Dutch and English, and test each one by keyboard.
International teams entering the Netherlands
Companies from the UK, the US or elsewhere launching to Dutch customers. We add Dutch content, local payment methods and EAA-ready accessibility before launch, not after the first complaint.
Other services for Dutch teams
A good front end starts with a clear design, and my team does both.
What clients say about my team
Working with Jubayer and the team has been a blast. Their creativity has honestly taken our platform to new heights. Incredibly professional and so proud to work with, we’re over the moon with their results, and we can’t wait to team up with them again.
I highly recommend Jubayer for any design project. He quickly grasps complex concepts, excels in standard design practices, and responds promptly.
Working with Jubayer on our website was fantastic from start to finish. He took the time to understand our vision and provided valuable insights.
Development in Amsterdam: frequently asked questions
Answers on the EAA, Wero, languages and working with a team in Dhaka.
What drives the cost of a Next.js build in Amsterdam?
The number of screens and components, how much accessibility repair the current front end needs, the payment and identity integrations, the languages, and whether we 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.
Does the European Accessibility Act apply to us?
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; my team builds the front end to meet it.
Why build to WCAG 2.2 when the standard still says 2.1?
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.
What does the move from iDEAL to Wero mean for our checkout?
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. My team updates your checkout through Mollie, Adyen or your provider and tests every outcome along the way.
Can you build our cookie banner to Dutch rules?
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. We build exactly that, block tracking scripts until people opt in, and your privacy lead approves the wording.
Should our product be in Dutch or English?
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. We internationalise the app from the start, so adding Dutch later is content work rather than a rebuild.
Can you fix the issues in our accessibility audit?
Yes. Send us the audit and the URL. We 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.
Can you work with our part-time Dutch team?
Yes. The Netherlands has the EU's highest share of part-time work, so many teams have people in on different days. We keep pull requests small, write a handover note on each one and book reviews for the days your reviewers work, so nothing waits a week for the one person who knows that part of the code.
How do we start a build with your team?
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.