willschneider15

Many people cringe at this approach, as most prefer to use industry-best standards and avoid refactoring. However, since most projects fail anyway, I prioritize speed and opt for managed tools.

I believe that with extensive experience, one can effectively manage everything from the start. Nevertheless, implementing your own authentication, designing database schemas, and managing infrastructure can all be challenges addressed later if the project proves successful. What is your preferred stack and infra for starting projects?

I can remove that but I'm trying to reward early users for taking the risk on a new product. Any other suggestions?

I used Supabase in a previous project and found that I prefer Firebase for MVPs.

1. I prefer NoSQL to start because I don’t have to deal with numerous database migrations when I want to update the schema due to changing requirements.

2. I prefer Firebase’s out-of-the-box authentication: https://blog.hyperknot.com/p/comparing-auth-providers

However, I would consider Supabase if row-level security or complex queries were necessary for the MVP.

Regardless, if one of my MVPs gained real traction, I would want to move away from a Backend-as-a-Service solution.

I did check out their features but did not see that listed on their landing page.

May consider dropping the $300 to try out their kit.

I appreciate the feedback I will add that to the lander.