Choosing a stack for your MVP

For an MVP the best technology is the one that gets you in front of users soonest and will not need a rewrite in six months.

Optimise for learning speed

Pick tools you or your team already know well. A familiar stack beats a fashionable one.

Buy before you build

Authentication, payments, email and file storage are solved problems. Use a managed service and spend your time on what makes your product different.

Keep the data model honest

You can change the UI endlessly, but a messy database is expensive to fix. Spend an extra day on the schema.

Deploy on day one

Set up a deployment pipeline before the first feature. Shipping daily is a habit you want from the start.

There is no perfect stack. There is a stack you can finish with.