Skip to content

[in_app_purchase] Updates handling of subscription price changes in README. #4643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 4, 2023
Merged

[in_app_purchase] Updates handling of subscription price changes in README. #4643

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions packages/in_app_purchase/in_app_purchase/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
## 3.1.8

* Updates documentation on handling subscription price changes to match Android's billing client v5.

## 3.1.7

* Fixes unawaited_futures violations.
Expand Down
49 changes: 18 additions & 31 deletions packages/in_app_purchase/in_app_purchase/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,40 +239,27 @@ InAppPurchase.instance

### Confirming subscription price changes

When the price of a subscription is changed the consumer will need to confirm that price change. If the consumer does not
confirm the price change the subscription will not be auto-renewed. By default on both iOS and Android the consumer will
automatically get a popup to confirm the price change, but App developers can override this mechanism and show the popup on a later moment so it doesn't interrupt the critical flow of the App. This works different for each of the stores.
When the price of a subscription is changed the consumer will need to confirm
that price change. If the consumer does not confirm the price change the
subscription will not be auto-renewed. By default on both iOS and Android the
consumer will automatically get a popup to confirm the price change. Depending
on the platform there are different ways to interact with this flow as
explained in the following paragraphs.

#### Google Play Store (Android)
When the subscription price is raised, the consumer should approve the price change within 7 days. The official
documentation can be found [here](https://support.google.com/googleplay/android-developer/answer/140504?hl=en#zippy=%2Cprice-changes).
When the price is lowered the consumer will automatically receive the lower price and does not have to approve the price change.

After 7 days the consumer will be notified through email and notifications on Google Play to agree with the new price. App developers have 7 days to explain the consumer that the price is going to change and ask them to accept this change. App developers have to keep track of whether or not the price change is already accepted within the app or in the backend. The [Google Play API](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions) can be used to check whether or not the price change is accepted by the consumer by reading the `priceChange` property on a subscription object.

The `InAppPurchaseAndroidPlatformAddition` can be used to show the price change confirmation flow. The additions contain the function `launchPriceChangeConfirmationFlow` which needs the SKU code of the subscription.

```dart
//import for InAppPurchaseAndroidPlatformAddition
import 'package:in_app_purchase_android/in_app_purchase_android.dart';
//import for BillingResponse
import 'package:in_app_purchase_android/billing_client_wrappers.dart';

if (Platform.isAndroid) {
final InAppPurchaseAndroidPlatformAddition androidAddition =
_inAppPurchase
.getPlatformAddition<InAppPurchaseAndroidPlatformAddition>();
var priceChangeConfirmationResult =
await androidAddition.launchPriceChangeConfirmationFlow(
sku: 'purchaseId',
);
if (priceChangeConfirmationResult.responseCode == BillingResponse.ok){
// TODO acknowledge price change
}else{
// TODO show error
}
}
```
When changing the price of an existing subscription base plan or offer,
existing subscribers are placed in a legacy price cohort. App developers can
choose to [end a legacy price cohort](https://developer.android.com/google/play/billing/price-changes#end-legacy)
and move subscribers into the current base plan price. When the new
subscription base plan price is lower, Google will notify the consumer via
email and notifications. The consumer will start paying the lower price next
time they pay for their base plan. When the subscription price is raised,
Google will automatically start notifying consumers through email and
notifications 7 days after the legacy price cohort was ended. It is highly
recommended to give consumers advanced notice of the price change and provide a
deep link to the Play Store subscription screen to help them review the price
change. The official documentation can be found [here](https://developer.android.com/google/play/billing/price-changes).

#### Apple App Store (iOS)

Expand Down
2 changes: 1 addition & 1 deletion packages/in_app_purchase/in_app_purchase/pubspec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: in_app_purchase
description: A Flutter plugin for in-app purchases. Exposes APIs for making in-app purchases through the App Store and Google Play.
repository: https://github.com/flutter/packages/tree/main/packages/in_app_purchase/in_app_purchase
issue_tracker: https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+in_app_purchase%22
version: 3.1.7
version: 3.1.8

environment:
sdk: ">=2.18.0 <4.0.0"
Expand Down