RevenueCat
The demo app isn't enough to represent a real-world scenario
The demo app calls functions, but in fact, it does't represent any real-world scenario.
I'm having difficulties to understand in what order the functions to be called and which steps are optional/required. Could you make a demo app with a real case scenario?
What I would like to see from a real demo app:
Example Products for each type
- Weekly (with 3 days trial) - Infinite coins
- Yearly (no trial) - Infinite coins
- Lifetime (non-consumable IAP) - Infinite coins
- 1000 Coins (consumable)
Loading Screen
A very common case in most of the games and apps. I'm know I should register a singleton and call configure function here.
- But what about to
GetOfferingsandGetProducts? - When do I call
GetCustomerInfo? Before or after getting offerings? - To check user' purchases, which one should I use?
- Entitlements
- ActiveSubscriptions
- AllPurchasedProductIdentifiers
Home Screen
This page should show: "you're pro user yearly/monthly/lifetime" or "you're not pro user" There should be a button to open the paywall to buy IAPs or starts subscriptions and there should be Restore button.
- When paywall opens, should I call
GetOfferingsandGetProductsagain? - How to show price and free trial info on Paywall?
As you can see, your demo app doesn't answer any of these question.
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!
Hey @cihadturhan,
Thanks for that breakdown and suggestions, we really appreciate you laying all this out! These type of examples make a big difference for us, and that feedback is very much welcomed.
We’re always trying to make our SDKs (and sample apps) more useful, so I’ll pass this along to the team and we’ll see what we can do.
If you think of anything else or run into more pain points, just let us know. Thanks!
Reopening issue. It was closed due to a failing automation. Sorry about that.
