In my opinion, if you don't know if you have a product-market fit, there's no point in effectively doubling your "bet" in the existence of the market by rewriting the prototype.
So you're not using the best possible tech, but neither scalability nor performance matters when there's absolutely no users. Once you get at least some traction you can make more informed decisions about the rewrite, but right now you'd be just throwing more coding hours into creating something that might not have a market.
I agree with the last chapter 100% though, just throw the baby in the pool and see if it can swim. Our launch version had a lot of features implemented as "one of the founders is going to do it manually if you click on the button". Then we automated the tasks we actually had to do more than once per hour.
So you're not using the best possible tech, but neither scalability nor performance matters when there's absolutely no users. Once you get at least some traction you can make more informed decisions about the rewrite, but right now you'd be just throwing more coding hours into creating something that might not have a market.
I agree with the last chapter 100% though, just throw the baby in the pool and see if it can swim. Our launch version had a lot of features implemented as "one of the founders is going to do it manually if you click on the button". Then we automated the tasks we actually had to do more than once per hour.