When you're building an MVP to find product market fit, it's important to know what you want to learn, what category of tool to use and which tool to build with.
This document is a work in progress. I'm building it for the 30 - Collections/Organizations/Murmur team to use as a guide for how we can experiment with ideas with no/low code tooling.
One of the most important things to consider when exploring an idea for a product is how can I make something fast to validate my idea?
There are some basic mindsets that you need for this kind of product development:
The first thing to do once you've decided what you're hacking on, is to ask "what category of tool do I need to hack this together?"
There are a few categories to consider:
Forms are a great way to learn specific things about your target audience.
You can create quizzes, surveys, even single question. The main benefits of using forms are:
Some of the downsides to using forms for an MVP:
Here are a few no code form builders that people generally use for MVPs:
Landing pages are a higher fidelity MVP solution than forms, because they usually require more design (even if you're building with no-code).
Some of the benefits of using landing pages for finding product-market fit:
Some downsides to using prototypes for MVPs:
There are a few well known landing page builders for hacking together MVPs:
Prototypes are higher fidelity than Landing pages. On top of needing design, you need to also be aware of the user flows.
If you're going to build a prototype, it's good to know that you're on the right track based on insights from forms or landing pages.
Some of the benefits of using prototypes as an MVP for finding product-market fit:
Prototypes are a great way to see how a user will use your MVP.
There are a few tools that are great for building prototypes for MVPs:
Chatbots are a great way to test an MVP, because they allow you to test an MVP without needing to worry about the visual aesthetics and focus on the workflows and interactivity that the user will experience.
Some of the benefits of using chatbots when creating an MVP:
While a chatbot can be a great way to create an MVP, they also come with some disadvantages:
There aren't any chatbot builders that I know of. Why aren't there no code chatbot builders?!
You could use a few nocode tools to stitch together a chatbot builder (mileage may vary):
Functional apps ideally should be what you start to build when you know that people want what you have told them they could have.
Starting with a functional app reduces the amount of learning you can do for the amount of time you'll invest into making it.
Make sure you have a good MVP of what you're going to build and know that it's just the starting point to building something better.
Some of the benefits of using functional apps to create a MVP:
Some of the downsides to using functional apps to create an MVP:
There are a few functional app builders:
Hey, I'm Chase. I help aspiring entrepreneurs and makers turn their ideas into digital products and apps.
A figma community project of vectorized hand-drawn arrows.Go To Figma
A figma community project of vectorized hand-drawn lines.Go To Figma
A figma community project of vectorized hand-drawn shapes.Go To Figma
Subscribe to my Newsletter
Every other week I publish the Curiously Crafted newsletter.
In it, I explore the intersection of curiosity and craft: the people who make stuff, what they make and the way they pursue the craft of making.
I'm on almost all social media as @curiouslychase.