Hey Indie Hackers,
My name is Drew. I use Next.js for nearly every project, both at work and on side projects.
I wrote a 3000+ word essay this weekend on why React developers should use Next.js. It was received pretty well on Twitter so I thought I'd share it here as well.
I'm adding some extra tips here for Indie Hackers that I left out of the essay.
P.s. - The first section of the post talks about React & how it became successful. If you're already sold on React, there's no need to read that section.
(use this link to skip to the Next.js section)
In order to find your way to product-market-founder fit, it is crucial you're able to iterate enough on the project. If you spend too much time configuring routers, setting up your CICD, and trying to figure out how to pre-render pages, you're not going to make it.
Because you're just one person working in an app, the idea of separating an app on a frontend/backend split doesn't make sense. Put all the code in one place, access it quickly, and iterate.
We're all lucky at work. Someone configured our CI/CD pipelines for us, configured the e2e tests, and automated the Lighthouse audits.
When you host on Vercel, your Next.js app gets the power of at least 2 DevOps engineers for free.
If you're an Indie Hacker, maker, bootstrapper, there's one thing that's true no matter what.
You're short on time.
Next.js + Vercel helps with that.
I'll be sending out essays and newsletters at drew.tech once a month. Subscribe to follow along. I'll also try to share most of my content on Twitter (@dbredvick) and here.