@m0agh Totally agree.
Motivation dies but discipline doesn't.
I am building something which I am gonna use in my day to day life, so I hope number of active users doesn't stop me from building.
But true in order to refine and adapt we need genuine feedbacks from real users.
12/12
I started with:
βSupabase and Firebase are databases.β
I ended with:
βThey're BaaS platforms.β
Once I understood that distinction, it became much easier to understand where they fit into a backend architecture.
I thought Supabase and Firebase were just databases.
Then I asked:
βIf I already have PostgreSQL, Node.js, and my own backend, why would I need them?β
That question made me realize I had misunderstood what BaaS actually means. π§΅
11/12
Traditional backend:
More control β More responsibility
BaaS:
Less infrastructure work β More platform dependency
Neither approach is automatically better.
The right choice depends on what your application needs.
9/12
And you don't have to choose:
My Backend OR Supabase
You can combine them:
Frontend
β
My Backend
β
Supabase
β
PostgreSQL
Your backend handles business logic while Supabase provides selected managed services.