revenuecat-sdk-compatibility

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

RevenueCat SDK compatibility

RevenueCat SDK兼容性

Use the RevenueCat MCP server for all tool calls here.

所有工具调用请使用RevenueCat MCP服务器。

Check feature compatibility

检查功能兼容性

Call

list-sdk-feature-gates

before making any SDK compatibility claim. Find the gate that matches the user's feature and use its minimum version for each relevant RevenueCat SDK.

If the relevant feature gate cannot be identified, say so and explain which gates looked close instead of guessing. Consult the docs linked in the tool output to disambiguate.
When more than one gate could apply, prefer the most specific gate. For example:
- Existing-customer experiment enrollment:
```
experiment-existing-customer-enrollment
```
- Experiment exposure status or reporting:
```
experiment-exposure-tracking
```
- New-customer experiment enrollment:
```
experiment-new-customer-enrollment
```
If multiple gates jointly matter, evaluate and name each one.

在做出任何SDK兼容性声明之前，请调用

list-sdk-feature-gates

。找到与用户功能匹配的限制条件，并获取每个相关RevenueCat SDK对应的最低版本。

如果无法确定相关的功能限制条件，请如实说明，并解释哪些限制条件看起来较为接近，切勿猜测。可参考工具输出中链接的文档来区分。
当多个限制条件都可能适用时，优先选择最具体的那个。例如：
- 现有客户实验注册：
```
experiment-existing-customer-enrollment
```
- 实验曝光状态或报告：
```
experiment-exposure-tracking
```
- 新客户实验注册：
```
experiment-new-customer-enrollment
```
如果多个限制条件共同相关，请逐一评估并列出每个条件。

Analyze SDK adoption

分析SDK采用率

Call

list-sdk-versions

to assess upgrade impact or rollout risk from SDK versions observed in the project. Each row describes subscribers seen in the last 30 days and includes:

```
sdk_type
```
: RevenueCat SDK family.
```
sdk_version
```
: underlying native SDK version for native rows, or the native SDK bundled under a wrapper in
```
platform_flavor
```
rows.
```
sortable_sdk_version
```
: normalized value for ordering
```
sdk_version
```
.
```
platform
```
: native platform, such as
```
ios
```
or
```
android
```
, when grouped by platform or platform flavor.
```
platform_flavor
```
and
```
platform_flavor_version
```
: wrapper SDK family and version, such as
```
react-native
```
```
10.0.1
```
, when grouped by platform flavor.
```
subscribers_last_30days
```
and
```
pct_of_subscribers
```
: recent project usage counts and shares.

Choose the grouping that matches the question:

Use
```
sdk_type
```
for a high-level inventory by RevenueCat SDK family.
Use
```
platform
```
to compare native iOS and Android adoption.
Use
```
platform_flavor
```
for React Native, Flutter, Capacitor, Unity, Kotlin Multiplatform, and other wrappers where both the wrapper version and bundled native SDK versions matter.

To compute upgrade impact, filter to the relevant SDK family, compare observed versions with the feature gate's

min_version

, and sum

subscribers_last_30days

and

pct_of_subscribers

for rows below the requirement. State that these figures represent subscribers observed in the last 30 days, not the all-time install base.

Use

jq

for quick filtering or a code execution tool for version comparisons, grouping, and subscriber-share calculations when the output is too large to analyze reliably by inspection.

调用

list-sdk-versions

来评估SDK版本带来的升级影响或发布风险，这些版本数据来自项目中观察到的情况。每一行描述了过去30天内的订阅用户情况，包含以下字段：

```
sdk_type
```
：RevenueCat SDK系列。
```
sdk_version
```
：原生行对应的底层原生SDK版本，或
```
platform_flavor
```
行中包装器所捆绑的原生SDK版本。
```
sortable_sdk_version
```
：用于对
```
sdk_version
```
进行排序的标准化值。
```
platform
```
：原生平台，例如
```
ios
```
或
```
android
```
，按平台或平台变体分组时显示。
```
platform_flavor
```
和
```
platform_flavor_version
```
：包装器SDK系列及版本，例如
```
react-native
```
```
10.0.1
```
，按平台变体分组时显示。
```
subscribers_last_30days
```
和
```
pct_of_subscribers
```
：项目近期使用量统计及占比。

根据问题选择合适的分组方式：

使用
```
sdk_type
```
按RevenueCat SDK系列进行高层级统计。
使用
```
platform
```
比较原生iOS和Android的采用率。
使用
```
platform_flavor
```
针对React Native、Flutter、Capacitor、Unity、Kotlin Multiplatform及其他包装器，这些场景下包装器版本和捆绑的原生SDK版本都很重要。

计算升级影响时，筛选出相关的SDK系列，将观察到的版本与功能限制条件的

min_version

进行比较，然后汇总版本低于要求的行的

subscribers_last_30days

和

pct_of_subscribers

。需要说明这些数据代表过去30天内观察到的订阅用户，而非所有历史安装用户。

当输出内容过大无法通过人工检查可靠分析时，可使用

jq

进行快速筛选，或使用代码执行工具进行版本比较、分组和订阅用户占比计算。