I have been planning to have my app be available as only a subscription service: monthly or annual.
I was expecting to have them sign in with OAuth from Google or Apple, using Supabase Auth to handle things like sessions. Then, once signed in/registered, update my own data `user` data table to store things about the user depending on their interactions within the app.
Now I am trying to add RevenueCat.
I see that in the docs about Users, Purchases.configure({apiKey: <public_sdk_key>});
will generate a random ID. Unfortunately, this will not tie into my backend of known users. So the docs give an option to include appUserID
in the config.
My question is now about the flow.
Is it reasonable to have my subscription-only app open on the login screen, then user logs in, and once logged in, trigger the configure({apiKey: ‘123abc’, appUserID: ‘known@user.com’)
API with the appUserId
?
Or I can call the RC `logIn()
` method later too...
Is there a downside to waiting to configure
& load my products until after user logs in?