One of the reasons I was confused is that the provided diagram makes me wrongly think that a given entitlement grants access to a given product, while it is the opposite. Buying any of the product associated with the entitlement unlocks the entitlement. Maybe, in order to be less ambiguous, instead of showing: entitlementA = [product1, product2] it should show it as product1 => entitlementA
I integrated Revenuecat and it's easy to use, but what if I want to offer a subscription, but a user has a google account? How do I manage the subscription?
These are handled by Apple. Developers do not have to (and cannot) handle the actual credit card transaction with the customer directly. You can subscribe to RevenueCat webhooks for some of these events though if you want to do something in-app in response to a billing error on a renewal or something for example.
I have a product that is a consumable, meaning the user buys it and I give the user credits (100), I manage the usage counter within the app and if it reaches 0 then I trigger another purchase. I don't need an entitlement because Revenuecat cannot handle the counter for me, so why do I need to create an entitlement for consumable purchases?
@@RevenueCat then how do i verify that the purchase was succesful? if there is not entitlement associated to the user? I am just looking fro a succesful purchase event, to make sure I release the credits
For something like that you would want to use a non-consumable in-app purchase. You can find more information about non-subscription purchases in our docs here www.revenuecat.com/docs/platform-resources/non-subscriptions
