Next.js developer · Leeuwarden

# How I build with Next.js

I am a developer in Leeuwarden and build products of my own with Next.js, React and TypeScript: from a first idea to something that is live, the frontend and the backend with it. This is how I go about it.

- Next.js
- Leeuwarden, NL
- 4 projects
- Updated 8 Oct 2026

## What I look after

What I do again with every product.

1. 01
### From idea to live
Traklyst began as a side project and grew into a product with its own recognition pipeline, accounts and paid plans. I designed and built it, and host it myself.
2. 02
### A frontend with a system
React and TypeScript, with Tailwind and shadcn/ui as the base for an interface that stays consistent while the product grows.
3. 03
### The backend too
API routes, a database in PostgreSQL or Supabase, accounts and payments. For Traklyst and UntitledOne I built both sides.
4. 04
### Headless for WordPress
A fast frontend in Next.js, while the content and the orders stay in WordPress. That is how the French webshop Oursondenaissance is set up.
5. 05
### Easy to find
Server-side rendering, clean metadata and a product feed where it is needed. For Oursondenaissance, French SEO and a feed for Google Merchant were part of the build.
6. 06
### Tested with users
UntitledOne was built on interviews, a survey and usability tests. What came out of those decided what went into the first version.

## How does Traklyst work?

Traklyst is the largest thing I have built in Next.js. You paste a link to a DJ set on YouTube or SoundCloud and the tracklist is built on the page while the scan runs, with a timestamp for every track.

Each scan follows the same steps. First Traklyst collects what has already been published about the set: the description, the comments and community tracklists. Then it analyses the recording itself. A track is only added when two independent sources agree. A part nobody can name stays in the list as ID, instead of being filled in with a guess.

Around it sits what a product needs: accounts, plans and billing, and a public library in which every scanned set gets a page of its own. In early October 2026 it held 2,954 identified tracks, 81% of them confirmed by the audio.

tracks identified

2,954

confirmed by the audio

81%

sources needed per track

2

## Built with Next.js

Products of my own, a graduation project and a webshop.

[View all work](https://sanderr.nl/projects/)

- [Traklyst Product, Design & Development · 2026 Next.js · TypeScript · React · Tailwind · shadcn/ui](https://sanderr.nl/projects/traklyst/)
- [OnderhoudJe Product, Design & Development · 2025 Expo · React Native · Next.js · TypeScript · Node.js · PostgreSQL · Docker](https://sanderr.nl/projects/onderhoudje/)
- [UntitledOne Open-source music collaboration · 2025 Next.js · React · TypeScript · Tailwind · shadcn/ui](https://sanderr.nl/projects/untitledone/)
- [Oursondenaissance Headless commerce · 2024 Next.js · Node.js · React · shadcn/ui · Tailwind · TypeScript](https://sanderr.nl/projects/oursondenaissance/)

Often in the same projects

- TypeScript
- React
- Tailwind
- shadcn/ui
- Node.js
- [Expo](https://sanderr.nl/react-native/)
- React Native
- PostgreSQL
- Docker

## How I work

Clear decisions, short loops and something real to react to.

1. ### Find the actual need
Before choosing a stack, I clarify the goal, the user and the smallest version worth building.
2. ### Build the right amount
I choose the simplest stack that fits, then move quickly into something real enough to test and improve.
3. ### Refine the experience
Responsive behaviour, subtle motion, accessible choices, readable code and a clear CMS turn a working build into a finished product.

## Questions

What I often hear about it.

1. I choose the simplest stack that fits. If it is about content someone manages themselves, WordPress is often enough. If it is a product with accounts, logic of its own or a lot of interaction, Next.js fits better.
2. Yes. WordPress then stays the admin and Next.js becomes the front. Oursondenaissance works that way, with WooCommerce behind it.
3. Yes. For Traklyst and UntitledOne I built the interface as well as the database, the accounts and the rest of the server side.
4. Of UntitledOne it can: it is open source under the MIT licence.

## Which stack when

I choose the simplest one that fits.

| Stack | When |
| --- | --- |
| [WordPress](https://sanderr.nl/wordpress/) | Content someone manages themselves: a site, a portfolio, a blog. |
| [Expo](https://sanderr.nl/react-native/) | Something you carry with you and that has to remind you: an app. |
| Next.js | A product with accounts, logic of its own or a lot of interaction. |
| [Laravel](https://sanderr.nl/laravel/) | An application with users, permissions and a lot of data. |

---

- [Sander de Vries for agents](https://sanderr.nl/llms.txt)
- [Sitemap](https://sanderr.nl/sitemap.xml)
- [Contact](mailto:hello@sanderr.nl)