Google I/O 22 Announcements - RC Product Priorities

Show first post

55 replies

M
Rank
Userlevel 2
Badge +2

Hey, is there already an ETA on this?

Hey @Ralf Meyer we have a beta out! See the  post below if you’re interested in joining:

G

Hi there,

I’m curious. Right now, we’re advised not to make multiple base plans for our subscription. In the future, when this is supported, will this fix the problem where some users are able to subscribe to both monthly/yearly subscriptions (and be double charged) for the same product? We have this issue and are looking for solutions.

M
Rank
Userlevel 2
Badge +2

Hi there,

I’m curious. Right now, we’re advised not to make multiple base plans for our subscription. In the future, when this is supported, will this fix the problem where some users are able to subscribe to both monthly/yearly subscriptions (and be double charged) for the same product? We have this issue and are looking for solutions.

Hey @Gabe Jacobs , great question! You’re correct - attempting to purchase any base plan within an already-purchased subscription will no longer result in being doubly-charged. It would not be possible to have more than one base plan active at a time.

The new library will allow switching between base plan durations, if that is something you wish to offer.

You can use CustomerInfo to find out which entitlement is currently active, and ensure any products belonging to the same entitlement are purchased as an upgrade/downgrade rather than a normal purchase. You can do this by passing UpgradeInfo into the purchase flow.

G

Hi there,

I’m curious. Right now, we’re advised not to make multiple base plans for our subscription. In the future, when this is supported, will this fix the problem where some users are able to subscribe to both monthly/yearly subscriptions (and be double charged) for the same product? We have this issue and are looking for solutions.

Hey @Gabe Jacobs , great question! You’re correct - attempting to purchase any base plan within an already-purchased subscription will no longer result in being doubly-charged. It would not be possible to have more than one base plan active at a time.

The new library will allow switching between base plan durations, if that is something you wish to offer.

In both the current and upcoming versions of the SDK, it would be best practice to avoid giving the user the option to re-purchase a currently active subscription. You can use CustomerInfo to find out which entitlement is currently active, and hide any associated products from your paywall. Let me know if this makes sense!

Hey Maddie,

So if a user has purchased a monthly subscription, would you suggest making it impossible for them to sign up for the yearly option? Or perhaps when they sign up for the yearly option we mention they must manually cancel the monthly subscription? 

M
Rank
Userlevel 2
Badge +2

Hey Maddie,

So if a user has purchased a monthly subscription, would you suggest making it impossible for them to sign up for the yearly option? Or perhaps when they sign up for the yearly option we mention they must manually cancel the monthly subscription? 

 

Actually, I didn’t speak correctly. Thank you for clarifying. You could hide it, but then users wouldn’t be able to switch between durations.

Instead of hiding it, just make sure you perform that purchase as an upgrade/downgrade. You can do this by passing UpgradeInfo into the purchase method, and add the oldProductId to the UpgradeInfo. 

 

I’ll go ahead and update the comment above so it’s correct for others.

Reply


Terms & ConditionsCookie settings