Skip to content

The demo app isn't enough to represent a real-world scenario #643

@cihadturhan

Description

@cihadturhan

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 GetOfferings and GetProducts?
  • 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 GetOfferings and GetProducts again?
  • How to show price and free trial info on Paywall?

As you can see, your demo app doesn't answer any of these question.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions