Google I/O 22 Announcements - RC Product Priorities

A
  • Anonymous
  • 0 replies

What features are you the most excited about?
What would you like to learn more about?

Many updates and changes have been introduced during Google I/O 22 and our team is busy deep diving into these topics and prioritizing them according to your needs. We would love to hear your thoughts and needs on these features.
 

  • New Subscription Model - is it all clear what that means or would you rather we just take care of it? 
  • Play Console – how does your setup look after the changes? does this create an opportunity for your app?
  • Flexible Offers - would you see yourself making a use of this? 
  • Prepaid plans - does this solve an issue for you? would you like to learn more about the payment landscape of recurring payments? 
  • Play Index - do you see yourself using the index moving forwards? If so, what kinds of communications would you expect from RevenueCat?


Excited to hear from you!

62 replies

R
Badge +2

Hey, thanks for the update. 

Seems to work fine. I hope this is stable enough for production, as we are shortly before launching our app and I’d like to skip the old subscription model altogether.

MarcosC
Rank
Userlevel 3
Badge +6

@Ralf Meyer we have just released a beta version of React Native with support for BC5 (6.0.0-beta.1).

Any feedback more than welcome

 

 

Marcos
MarcosC
Rank
Userlevel 3
Badge +6

@Ralf Meyer We are currently working on support BC5 on React Native. I’ll let you know once the beta is out

Marcos
R
Badge +2

Hey, what about React Native? Is this update included there?

M
Userlevel 3
Badge +3

@Maddie Does purchases-android v6 also support Observer Mode when using Billing Client 5? The migration guide doesn’t mention Observer Mode at all.

Thanks for pointing that out. I’ll get the guide updated. But yes, v6 supports observer mode as well.

F
Badge +5

@Maddie Does purchases-android v6 also support Observer Mode when using Billing Client 5? The migration guide doesn’t mention Observer Mode at all.

M
Userlevel 3
Badge +3

Hey everyone! The team is excited to announce that purchases-android v6 has been released, with support for BillingCilent 5, including multiple base plans per subscription and multiple offers per base plan. 

For details on how to start the migration, check out our guide here.

M
Userlevel 3
Badge +3

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.

G
Badge

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
Userlevel 3
Badge +3

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
Badge

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
Userlevel 3
Badge +3

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:

R
Badge +2

Hey, is there already an ETA on this?

kaitlin
Rank
Userlevel 4
Badge +6

Hi, any update regrading getting into the beta?

I would really like to get into it and design my app around the new system instead of working with the current one.

Thank you.

Hey @MonkeyDrone, Thanks for your interest! Shoot an email to anna@revenuecat.com for more information!

M
Badge +2

Hi, any update regrading getting into the beta?

I would really like to get into it and design my app around the new system instead of working with the current one.

Thank you.

M
Badge +2

Hello MoneyDrone, 

We are in currently in beta while completing the set of functionalities that we set out for the release. 

Are you interested in testing with us? 

We are excited to have you use multiple base plans and offers soon!

 

What do you require, pre-requisites for helping you do tests on my end?

I would love to help in anyway I can!

A

Hello MoneyDrone, 

We are in currently in beta while completing the set of functionalities that we set out for the release. 

Are you interested in testing with us? 

We are excited to have you use multiple base plans and offers soon!

 

M
Badge +2

Any updates on the testing and how is the new system coming along? Thank you.

sharif
Rank
Userlevel 5
Badge +9

@chea seed  Apple non-renewing subscriptions should work like any other in-app purchase. One limitation is that RevenueCat won’t calculate the expiration date, so it will function more like a consumable than a subscription. The workaround would be to check the purchase date of the non-renewing subscription and calculate the expiration date on the fly. If you’re not seeing products on iOS that’s probably a configuration error - check this guide out.

Sharif
C
Badge +4

On a related note, has anyone been able to get non-renewing subscriptions to work with RevenueCat/App Store ? I am seeing the same issues as with Android/PlayStore - the product cannot be located. Auto-renewing subscriptions of course work fine on both iOS and Android.

@AnnaToro - could you confirm one way or another about non-renewing subscriptions on the App Store? I am using the latest version of the Cordova plugin (3.3.2) if that matters

Appreciate your help

 

A

Update here and an open invitation to our closed beta test → 

 

A

Hello, 

Thanks for the kind response Michael. Looking forward to working on the beta together. 

Ismet, it’s going well. We are expecting to do an internal release in a couple of weeks with the purchase flow while already working on the events part of the project. 

Let me know if you would like to join our beta at the end of this quarter and also let us know if there is anything that we can help with in the meantime.

Michael Callahan
Badge 
How is the work going? @AnnaToro 

We will be working closely with the RevenueCat team once they are ready to beta the changes in Q4 2022 / Q1 2023.
As Anna kindly provided us a Q4 beta test estimation, I would expect an update from their team early next year. I would be happy to provide insight from a end user (developer customer) perspective once we have had a chance to test out the beta and sort out any potential bugs with the RevenueCat team.

I
Badge +2 
How is the work going? @AnnaToro 
Michael Callahan
Badge

Thank you for the update. It is much appreciated.

Reply


Terms & ConditionsCookie settings