Repository navigation
Should Next.js provide an official full-stack starter for modern SaaS applications? #94482
SummaryHi Next.js team and community, I’ve noticed that many developers building SaaS applications with Next.js end up setting up the same stack repeatedly:
While Next.js provides excellent building blocks, developers often spend a significant amount of time configuring infrastructure before they can focus on their product. Would it make sense for the Next.js ecosystem to provide an official, production-ready SaaS starter that demonstrates current best practices? Additional informationNo response ExampleNo response |
Replies: 1 comment
|
I think an official starter could be valuable, but I would probably frame it as a reference implementation rather than a single “official SaaS stack.” Next.js already gives the core building blocks, but a maintained full-stack example would help developers understand how the framework authors expect common production concerns to fit together:
The tricky part is avoiding too much provider lock-in. For example, auth, payments, storage, and databases all have multiple valid choices. So the most useful version might be an official “SaaS reference app” with replaceable adapters or clearly documented provider choices, instead of trying to make one starter that covers every use case. In my opinion, the biggest benefit would not just be saving setup time. It would be giving the community a maintained example of current best practices for building a production app with the App Router. |
I think an official starter could be valuable, but I would probably frame it as a reference implementation rather than a single “official SaaS stack.”
Next.js already gives the core building blocks, but a maintained full-stack example would help developers understand how the framework authors expect common production concerns to fit together:
The tricky part is avoiding too much provider lock-in. For example, auth, payments, sto…