Your language choice makes it confusing. You should've named "Entitlements" "Access Levels", "Products" "Skus", and "Packages" "Products". It doesn't make sense to name a group of the same thing a package. A group of different things is a package. It should be called a Product. Within that product should a set of Skus. The word entitlement is weird and should just be access level. A user is entitled to certain things is a very awkward way of saying the user has access to certain things. "gold_access_level" is much more intuitive than "gold_entitlement".
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 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
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.
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
1 year of integrating RevenueCat into mobile app and 0 customers. 😂 Earning a livelihood as a developer is a myth 🤣🤣🤣 Selling IT as a career by all these so-called tech bros online is nothing but a BIG scam 🤣
That last slide was crystal clear, perfect recap and very well done!
No Launched intro song? - My brain is confused.
Happy to see Charlie as part of the RC fam... best of luck!
Excellent video, great clear explanation. Please make more like this for Experiements and A/B testing :)
Crystal clear! Thanks a lot Charlie.
Superb succinct explanation!
your t-shirt matching with the RevenueCat color's, this is strong
wow, impressive product and tutorial, congrats!
Nice structure and great explanation 👍
Your language choice makes it confusing. You should've named "Entitlements" "Access Levels", "Products" "Skus", and "Packages" "Products".
It doesn't make sense to name a group of the same thing a package. A group of different things is a package. It should be called a Product. Within that product should a set of Skus.
The word entitlement is weird and should just be access level. A user is entitled to certain things is a very awkward way of saying the user has access to certain things. "gold_access_level" is much more intuitive than "gold_entitlement".
Why i cant have 3 monthly packages?
Could you explain the best practises for non renewing products?
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
Is it possible to allow users to subscribe to other premium users?
Incredible!
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?
You don't need to create a RevenueCat entitlement if you're managing that yourself using user credits purchased through 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
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?
You would want to use a Custom App User Id - www.revenuecat.com/docs/customers/user-ids#logging-in-with-a-custom-app-user-id
How do you handle ask to pay, billing retry, grace, network error etc edge case scenarios in ios?
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.
Very complicate for purchase single product!!! Per example, i have a library of books, an the user would like to purchase a single book...
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
offering, product, entitlements, pacgages...
Promo'SM 😓
1 year of integrating RevenueCat into mobile app and 0 customers. 😂
Earning a livelihood as a developer is a myth 🤣🤣🤣
Selling IT as a career by all these so-called tech bros online is nothing but a BIG scam 🤣