If you're bootstraped, does that mean you already have something? What is it and why do you want to replace it? Beware of large greenfield remake projects, these often fail spectacularly.
Given your first project is in Node + React, you might find Toolpad (https://mui.com/toolpad/) worth considering. It’s a set of components designed to build React dashboards. It's built on top of Material UI and is fully extensible. Also, it’s open source and free to use regardless of scale.
Can't speak about Retool but I wouldn't want to go away from standard software development life cycle with version control, release management and testing... And I definitely would want to avoid a proprietary platform. Isn't there an open source alternative?
We evaluated PayloadCMS to drive the backend of a mobile app and eventually settled on Directus because it supported heterogeneous collections which was something we had to have.
Directus also has a template for a multi-tenant app which sounds like something you might need.
Curious, why do you want to start another product, especially on a new stack if you have one already in the market? Doesn't it make sense to put focus all in the one you've launched? I am also trying to figure out this bootstrapping thing so got curious.
yeehhh thats a very good question - we've been asking ourselves the same thing.
We've got one product in the market, but launching that product and talking to customers has given us insight into a potentially larger, more lucrative problem to solve.
So we're currently allowing idea #1 to tick over, while validating idea #2.
We plan to only focus on one of the two ideas going forward, but are first trying to do enough discovery on idea #2, so that we can choose the best one to take forward.
