Skip to main content
Question

Consumable Permanent Feature Unlock (12-month term)

  • January 13, 2025
  • 2 replies
  • 17 views

Forum|alt.badge.img

I’m wanting to offer a non-renewing consumable unlock system for premium features in my app similar to Due and Working Copy. All features currently release and features for the next twelve months from the purchase date are unlocked. I read this thread which is similar to what I’m wanting to do: 

Because I’m wanting to do this as a consumable I know I will need to track the original purchase date of the consumable to ensure its not repurchased later. My main concern is related to restored purchases if the app is removed and downloaded again. I noticed in the support documentation this requires me to use a custom app user ID. 

My app does not have a login system but I noticed neither does Working Copy. I’m wondering if there’s a way to create this kind of custom app user ID, send it to RevenueCat and track it somehow without creating a login system? 

This post has been closed for comments

2 replies

Forum|alt.badge.img
jasonholtdigital wrote:

I’m wanting to offer a non-renewing consumable unlock system for premium features in my app similar to Due and Working Copy. All features currently release and features for the next twelve months from the purchase date are unlocked. I read this thread which is similar to what I’m wanting to do: 

Because I’m wanting to do this as a consumable I know I will need to track the original purchase date of the consumable to ensure its not repurchased later. My main concern is related to restored purchases if the app is removed and downloaded again. I noticed in the support documentation this requires me to use a custom app user ID. 

My app does not have a login system but I noticed neither does Working Copy. I’m wondering if there’s a way to create this kind of custom app user ID, send it to RevenueCat and track it somehow without creating a login system? 

Some progress in my research since I posted this. I figured out how to setup consumable purchases for both Android and Apple. But it seems a couple of things are required in order to get this system working: I need a backend like Firebase where I track a purchase and I need user authentication (some kind of sign in.) I could setup Firebase to track the purchase but user auth doesn’t make sense for my app. If anyone has any ideas or thoughts on implementation here, I’d appreciate it. 


jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 290 replies
  • January 21, 2025

@jasonholtdigital When configuring the RevenueCat SDK, we create an anonymous user for you. However, these users don’t persist if the app is deleted and reinstalled. The usual way of resolving this is restoring purchases, where we will alias together the new anonymous user and the original user that made purchases. But if you’re working with consumables, this is an issue as consumables aren’t present in the receipt. Would “Sign in with Apple” make sense for your app? It’s a fairly low-friction authentication system that iOS users are familiar with. This would allow you to “identify” your users and would fix the consumable receipt issue mentioned above.


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