Arguing for Next.js, in writing
The problem
The initial plan for KoninPay was HTML, Sass and Blade, for a product with merchant and store creation, payments and a wallet that had to keep growing.
What I did
I advocated Next.js, focusing on scalability, maintainability, development efficiency and long-term product evolution, and wrote a technical comparison of both approaches: architecture, advantages, trade-offs and maintainability. Part of the case was SEO: storefront product pages needed proper titles and link previews, and with Next.js they render on the server with their own metadata.
Result
The comparison supported the team's technology decision. Product pages became shareable and indexable, and seven live storefronts run on the platform today.
The call
Build the platform on Next.js
Instead of: HTML, Sass and Blade
Scalability, maintainability, development speed, and product pages that render with their own metadata for SEO and link previews.
A written comparison persuades better than an opinion, especially for people outside frontend.
Read the full case study→