I was wondering… what’s your strategy to keep back...

# supabase-kt

[Nacho Ruiz Martin]

I was wondering… what’s your strategy to keep backwards compatibility with Supabase on mobile apps given the release cycle?

For instance, if I want to rename a table or change the structure, that would mean that old versions would stop working completely because the app is fetching from the database directly.

I’m starting to think it’s more robust to always use edge functions, but then realtime is not usable.