This is really scary to think about when you're days or weeks away from launching an MVP.
I'm building a service for developers. I really want to polish the design and get the UX perfect, and have really good documentation and client libraries for various languages. But I think I can launch without those.
I really just need to record a screencast and get a demo online. But wow, the struggle is real. I really don't want to launch it yet.
I was just curious on how other people think this through.
It's a question I love hearing feedback on from other hackers who are building things to solve problems. A useful way I like to think about the MVP is : "if I removed everything, what's the last thing I could possibly remove without the solution no longer addressing the problem?"
I try to stop just before that line. That being said, it's always easier said than done.
DM me on Twitter/I just followed you! I'd love to try out your product when you're ready!
Is Dropbox considered a product that "launched early", despite them waiting to receive feedback on a video before building software?
Additionally, what tracks better: a good screencast or a bad useable demo (I imagine a good demo is obviously better than a good screencast)?
Otherwise, great list, and thank you for putting it together.