Need advice for how minimal my MVP has to be
Hello, i develop MVP of my next try, simple product analytics service for beginners, https://simplestat.site
About "minimal". At the beginning I wanted to try new (for me) special database (ClickHouse), designed special for massive user data storage.
Then, i changed my mind, my primary stack is node/mongo, I know mongo very well, and don't want to waste the time to learn ClickHouse.
But now I think again - if i will need to move to ClickHouse anyway (and later it will be harder) so what should i do - use known stack, or use right stack - for MVP?
Do the MVP with what you already know. If the MVP will be a success, you will be able to rewrite the implementation when/if you hit the performance problems.
I’d stop worrying about the tech stack and define what the minimal functionality of the product will be to validate it. Then work out which stack helps you build that quickest (sounds like node/ mongo), and go build it.
You’re just to get something launched to validate the idea. So as long as it doesn’t create a ridiculous amount of tech debt, your main focus should be speed.
Who is this for? If you are saying for everybody it usually means for nobody.
It is not clear what you want to ask...
This is planned as saas for early stage mvp's, who just started and want to see what are first users doing on their sites. General product analytics systems as Mixpanel and Amplitude complicated and expensive for small traffic mvp's. I ask if i must create fast on well known stack, but then (maybe soon) re-create right way, or create more slowly, but right designed from beginning.
What exactly is a "product"? software/website?
This will be cloud service, saas.
What's the fastest way to figure out if your target customer is willing to spend money on your value proposition?