Well, damn. I put effort into making a thing that could be tried out by anonymous users but still had RLS policies and now they've provided a solution that would have made the whole thing heaps easier.

Supabase also offers data (DB as a service).

I wonder if that means Supabase can solve the (separate) user storage problem[1].

[1]: https://threadreaderapp.com/thread/1651434348174778370.html

supabase auth stores your users in the same database created, just in a separate schema so you have full access to it to perform joins or enforce referential integrity.

Cool! Now I know at least two auth services that don't have this user storage problem.

FaunaDB also integrates DBaaS with their auth, but FaunaDB is a very different DB that doesn't work with standard SQL.

And FaunaDB doesn't have support for anonymous users!

I wonder how anonymous user sign-in info is persisted on the client. Specifically, I want to know whether re-installing the App will make it forget the previous anonymous sign-in.

re-installing the app will remove any locally persisted state - which includes the anonymous user’s sign in info

in a web app, we store this stare in either local storage / cookies

in a mobile app, this state is stored in the local storage equivalent - SharedPreferences for android and NSUserDefaults for IOS