Skip to content
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.

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

[WEB-2015] Rename "RevenueCat Billing" to "Web Billing" #618

Merged
merged 14 commits into from
Jan 31, 2025

Conversation

antoniobg
Copy link
Contributor

@antoniobg antoniobg commented Jan 28, 2025

Motivation / Description

Rename "RevenueCat Billing" to "Web Billing"

Changes introduced

Linear ticket (if any)

Additional comments

Copy link

Preview this PR here: https://dev-docs.revenuecat.com/pr-618/

@antoniobg antoniobg changed the title Rename "RevenueCat Billing" to "Web Billing" [WEB-2015] Rename "RevenueCat Billing" to "Web Billing" Jan 28, 2025

RevenueCat provides a backend and a mobile and web SDKs to to make implementing in-app and web purchases and subscriptions easy. With our SDK, you can build and manage your app business on any platform without having to maintain your own backend infrastructure. You can read more about [how RevenueCat fits into your app](https://www.revenuecat.com/blog/growth/where-does-revenuecat-fit-in-your-app/) or you can [sign up free](https://app.revenuecat.com/signup) to start building.

With the RevenueCat Web SDK and our billing engine RevenueCat Billiing, you can easily implement subscriptions in your web app or build a web subscription page for your mobile app. RevenueCat handles the recurring billing logic, manages what entitlements customers have access to, and automatically recovers payments in the case of billing issues. RevenueCat Billing uses Stripe as a trusted payment gateway and supports all payment methods supported by Stripe.
With the RevenueCat Web SDK and our Web Billing (formerly known as RevenueCat Billing) engine, you can easily implement subscriptions in your web app or build a web subscription page for your mobile app. RevenueCat handles the recurring billing logic, manages what entitlements customers have access to, and automatically recovers payments in the case of billing issues. Web Billing uses Stripe as a trusted payment gateway and supports all payment methods supported by Stripe.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added "formerly known as RevenueCat Billing". Not sure how often we want to add this. Should it be done in all pages, just in the main page?

@antoniobg antoniobg marked this pull request as ready for review January 28, 2025 11:34
@antoniobg antoniobg requested a review from a team as a code owner January 28, 2025 11:34
@antoniobg antoniobg requested review from a team and MrEdwardo January 28, 2025 11:34
@antoniobg antoniobg force-pushed the WEB-2015-web-billing-rename branch from 6ecfaf3 to 42e1769 Compare January 29, 2025 14:19
@antoniobg antoniobg force-pushed the WEB-2015-web-billing-rename branch 2 times, most recently from 6a70e87 to 451c340 Compare January 31, 2025 08:42
@antoniobg antoniobg force-pushed the WEB-2015-web-billing-rename branch from 451c340 to ca6249d Compare January 31, 2025 08:42
@@ -128,7 +128,7 @@ try {
const offerings = await Purchases.getSharedInstance().getOfferings({currency: "USD"});
if (offerings.current && offerings.current.monthly) {
const product = offerings.current.monthly.rcBillingProduct;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that this property will be marked as deprecated and replaced by webBillingProduct.

We plan to change this once a new version of the SDK is released, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, there's a task for it. But we would also need to update the purchases-js version used in the docs (currently 0.7.0, and latest is 0.15.1)

Copy link
Contributor

@vicfergar vicfergar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG!

I guess that API V2 specs will be updated once the renaming is done in the endpoints, right?

@antoniobg
Copy link
Contributor Author

LG!

I guess that API V2 specs will be updated once the renaming is done in the endpoints, right?

They're part of a khepri PR. To clarify, the endpoints won't be renamed, just some strings in the spec.

@antoniobg antoniobg merged commit 72febdd into main Jan 31, 2025
4 checks passed
@antoniobg antoniobg deleted the WEB-2015-web-billing-rename branch January 31, 2025 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants