The tech stack I used to build my MVP — full breakdown 🛠

Hey IH, I think we're all used to seeing the "what tech stack to use" posts here on IndieHackers.

Well, I just recently was able to launch the MVP for a new project I'm working on, Jobly (jobly.so), and I thought it would be worth sharing the tech stack.
Everyone's project will require different tech, so this obviously won't be a perfect list for everyone.
Still, I always find it interesting to read about what other people use and to try and discover new tools.

Marketing Site

NextJS / React + Vercel

The marketing site is a pretty standard NextJS app, hosted on Vercel.

In part, this was because I was using NextJS for the demo app as well, and I thought it would be helpful to match the technology.
I also knew that I wanted to use TailwindUI templates and components, which are super easy to integrate with NextJS.

I used Vercel for hosting, mainly because of how easy it is to use, and because it integrates so well with NextJS. They also offer unlimited subdomains (*.jobly.so) for a project on their premium tier, which is something I need for Jobly, so that was another factor in my decision.

Vercel — vercel.com

Splitbee (analytics)

I've used Splitbee for all my recent side projects, so of course I was going to use it again. I love the design and the fun way they display analytics. It's also really easy to setup custom event tracking and A/B testing, which is handy. I've been using the custom events feature to track my pre-order flow.

Splitbee — splitbee.io

TailwindUI / TailwindCSS (UI Components)

TailwindUI is one of the main reasons I was able to get the MVP up and running so quickly.

There are so many components available, and recently they've also released full site templates which make it even easier to get a basic site up and running. I used on of the site templates as a starting point for the Jobly marketing site, which sped things up greatly.

All the templates are built using TailwindCSS for the styling, which can be a bit tricky to wrap your head around. I found that once I got into it though, it made styling a lot easier to manage and is definitely worth trying out.

TailwindUI — https://tailwinduix.com/
TailwindCSS — https://tailwindcss.com/

Demo / MVP

The MVP reuses a lot of the tools I used for the marketing site, namely —

• NextJS
• Vercel
• TailwindUI + TailwindCSS

As I mentioned above, I tried to keep the tech stack for the marketing site and main app similar. This was to reduce context switching for me and to make deployment and maintenance easier.

Another benefit is being able to apply things I learn from one aspect of Jobly to another. When I learn something new about TailwindCSS while I'm building the marketing site, I can take that and apply it straight away to the main app.

Those are the main tools that Jobly is built on.
If you have any questions, I'm happy to answer them.
I'd also love to hear about the technology your MVP's use.