Skip to main content
Question

Should I store a purchase locally on my app?

  • February 23, 2025
  • 1 reply
  • 25 views

Forum|alt.badge.img+2

I have a simple app which does not require user login (at present). Users can purchase a one-time lifetime ‘subscription’.

Until now I have stored the purchase locally within the app local database.

In moving to RevenueCat for purchase handling, I now have the question - should I continue to store the purchase locally, or check each time with RC?  Related questions are

  1. Which is the best option regarding the question of risk here (hacking the subscription)?
  2. is there an issue with second option if user does not have wifi/connected?
  3. Or possibly do both (but possibly overkill!)

Thanks for any advice

This post has been closed for comments

1 reply

Forum|alt.badge.img+1

Hi!

The RevenueCat SDK will cache the data locally so you don’t need to worry about storing it locally yourself.

To answer your individual questions:

  • Which is the best option regarding the question of risk here (hacking the subscription)?

Assuming the device is not jailbroken, both options are equally secure. Doing it locally through the store APIs would not allow for tampering. For RevenueCat, we use cryptographic signatures to ensure the responses are not tampered with (more details).

  • is there an issue with second option if user does not have wifi/connected?

Checking each time with RevenueCat will use a local cache managed by the SDK, so you don’t need to worry if the user doesn’t have any internet connectivity.

  • Or possibly do both (but possibly overkill!)

There’s no need since the RevenueCat SDK is effectively doing the local caching you were doing yourself before 😀.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings