I used NextJS and Firebase and while I disliked some of it: I would use it again because if the benefits of speed in building. With this setup you can permanently host for next to nothing until you get users, do zero devops or ops, and have something that will scale up (wont be the fastest thing but it will be OK and will scale) You could switch out NextJS for a static site generator too, but NextJS is pretty conveni…
Ask HN: What would be your stack if you are building an MVP today?
11–20 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#12Supabase is very resource intensive. Django+drf+ spectacular+filters+jwt gives you all the perks of supabase with - much easier syntax - much lighter weight - alot higher productivity - UI auto generation
Re: Ask HN: What would be your stack if you are building an MVP today?
#132. Supabase for Postgres and Authentication.
3. Astro as a framework for front-end, deployed on Vercel, running in Hybrid mode.
With all of these in-place, I can extend my existing components to accommodate any needs. It scales very well in the beginning as I move very fast, and anecdotally scales very well regardless of size.
The only missing parts here is support for timed jobs, but that can probably be done with Fly.io machines in the future.
Re: Ask HN: What would be your stack if you are building an MVP today?
#14Re: Ask HN: What would be your stack if you are building an MVP today?
#15I personally don’t think that if you’re building an MVP you should be worrying that much about how to store users in the database and add RBAC and building a way to add middleware and a storage layer and all of that crap. It’s not worth it, your application is not a special snowflake.
Edit: Should say that with that I mean serving HTML via Django. Usually I would use Bootstrap for layout. Very occasionally I’d add an API for some interactivity but I think for most MVPs interactivity is likely to be a secondary concern until later.
Re: Ask HN: What would be your stack if you are building an MVP today?
#161. you get a lot of out of the box rails like glue jsut like rails or django but the runtime perf is way faster. you can get away without even using caching in prod for awhile
2. supabase is written in elixir
3. lambda could functiosn have their place but loc you in to a cloud provider. I can move my elixir mvps accross providers with no issue and I won't get any surprise bills.
Re: Ask HN: What would be your stack if you are building an MVP today?
#17Re: Ask HN: What would be your stack if you are building an MVP today?
#18It's boring but it works. It also scales as far as your wallet can handle.
Re: Ask HN: What would be your stack if you are building an MVP today?
#19https://github.com/learn-anything/learn-anything
Reasoning behind the stack is that I feel productive in Solid and it's plenty fast on first load and as SPA when fully loaded. I love the component model and JSX.
ChiselStrike is new to me but I was looking for something that lets me declaratively manage my schema. I checked https://entgo.io (it produced too many Go files to my liking), also Prisma (https://www.prisma.io), found it bit complex to get started with.
I also checked https://www.edgedb.com and it's nice but with ChiselStrike I can deploy it with LibSQL (fork of SQLite) and replicate it so responses should be plenty fast and I can build on top more easily.
For native apps will use SwiftUI composable architecture when it comes to it. React Native code sharing seems nice but Solid doesn't have a React Native alternative yet sadly.
Re: Ask HN: What would be your stack if you are building an MVP today?
#20Why:
- has almost everything that I need usually in mature gems - battle tested in production
- speed of development