undefined | Better HN

0 pointsquicksnap3y ago0 comments

About a year ago I took off maybe 5 months to create a ephemeral voice messaging mobile app (Android + iOS)

Stack:

- React Native + Expo - Typescript - Supabase - Vercel - Some Vercel/nextJS-ish lamda functions so I could avoid AWS (Supabase didn't have that kind of offering yet)

For me, it was _very_ pleasant to work in. I was able to ship features via OTA updates from idea to live in literally minutes.. sometimes even under a minute.

Loved working with Supabase.

0 comments

4 comments · 1 top-level

speakfreely3y ago· 3 in thread

How did you define your models and manage database migrations with Supabase?

quicksnapOP3y ago

After things were live, my migrations would be backward compatible. It's also possible to organize your tables where most of your data is in private schemas, and public views serve as your apis and versioning. Anything in a public view must be treated as a long-lived API until clients can be phased out.

My userbase was in the dozens at most, so pushing out a version OTA usually was effective to get things moving along.

Worst case, I had some code to check if the client version was too old and would shut it down until they updated.

As per models, what kind of details are you asking?

kiwicopple3y ago

The supabase CLI supports database migrations:

https://supabase.com/docs/guides/cli/local-development#datab...

andrewmunsell3y ago

Personally, I've found node-pg-migrate works well for a Node stack and Postgres migrations in Supabase. Then, I primarily interact with the database using the Supabase GraphQL API + RLS.

j / k navigate · click thread line to collapse