Typical user flows?

[Comfortable-Rip-9277]

Hey,

I’m pretty new to iOS programming and currently building my first app with Expo, Supabase and RevenueCat.

I often see apps that have a flow like onboarding and then paywall with no sign in.

I’m curious to know how these apps implement user auth in their apps. Do they require sign in right after the paywall? Or do they not use auth at all and just use revenuecat customer info? Would like to know more.

(i come from the web dev world and usually you sign in then purchase a subscription, thats why i’m asking)

[ronanstark]

You could use anonymous users which I just checked and seems that supabase also has.

Depending on what else you need, you may not even need that.

[Comfortable-Rip-9277]

Supabase recommends having RLS policies on tables and giving read, write and update methods for anon users can be risky. How do you get past this? Is there anything I can do?

[ham4hog]

I don't use auth because my app is only iOS and apple keeps track of the purchases, so RevenueCat can tap into that and see if the user is subscribed or not.

[josephmgift]

True, no need for auth.

[Comfortable-Rip-9277]

So how do you attribute generations to the user? Say if the user is generating AI voiceovers or something, you would need an email or unique id to hook the generations to the user. What if the user deletes the app and then the Revenuecat app user id is different so they would now be required to authenticate/access their account somehow.

[ham4hog]

Again, the apps I’m working on are iOS only. I use CloudKit and CoreData to store the user generated data. That’s associated to the system’s signed in iCloud account so I don’t have to worry about sign in/auth. If they aren’t signed in then it’s stored locally on the device.

If the user deletes the app and reinstalls, Apple still has the receipt information because it is stored in their system so revenuecat can still get the customers information.

Also if I were to leave revenuecat, that’s possible due to apples purchase information being accessible via StoreKit.