Supabase developer experience improvements - realtimes, types & transactions - Supabase hosted backed/server functions as solution?

I like the idea of Supabase - open source, Postgres first and the approach to use other existing open-source technologies. And to build a basic app, Supabase offers a great developer experience. But I think lately, more and more apps would like to offer more Realtime features and are transaction (or trigger) heavy while many developers prefer to build their frontends in typescript (or other typed languages). And I personally feel, that once you try to do that using Supabase, things are not that straightforward anymore, and the developer experience suffers. So, I wanted to argue why I believe this and if Supabase could improve it. The case of Realtime Supabase recommends using [broadcasting ]( now. But to setup a Realtime query, I must write a lot of code and in theory also test that code. As far as I understood, if I would like to listen to a Realtime Todo list table, I would have to: 1. Create a todo table (in sql) 2. Set up row level security (in sql) 3. Activate …