[ksubedi]

Next.js creates a good setup to create a React frontend application with server side rendering support out of the box. Pair that with Vercel and you get an amazing deployment environment with CDN, cloud functions, edge functions (middleware) server side rendering and more without much hassle.

Tailwind let me quickly create any UI I want, and Daisy helps me reduce the amount of time needed to style basic elements like inputs and all.

Firebase lets me get a low latency real time data source for my application, that can scale infinitely. It also handles some other parts of building an application that normally take a lot of time: authentication, storage management etc. And the pricing is really really cheap once you consider how much it costs to create an infrastructure that scales as well as firebase does, unless you model your data wrong and end up using a lot of db read/write cycles unnecessarily.

The backend API piece is not missing, you can use either Next.js API or firebase functions for backend piece, I use those for things like stripe billing backend etc.

This stack is enough for most projects out there, and when its not enough its flexible enough that you can integrate it with other things. And that timeline I mentioned was for a production ready MVP.

[tomatowurst]

Where is Vercel's cloud functions running? How do they compare to AWS Lambda/Edge?

The documentation on https://nextjs.org/learn/basics/api-routes/api-routes-detail... seems quite sparse. I see basic routing and middleware but seems nowhere near as many features as other frameworks.

I see it's great for building an MVP but may not be a good fit outside of startups. Nevertheless, its the front-end and server side rendering is quite interesting to me.

What are some problems with this setup? Might have a go just for the frontend portion but seems to good to be true in some aspects.