pricing-display

Pricing Display Rules

Use these rules for an app's own subscriptions and in-app purchases.

Source Of Truth

Paywall, upgrade prompts, onboarding price mentions, and subscription metadata must use live StoreKit or RevenueCat data. Do not hardcode price, period, trial duration, or savings claims in Swift.

Banned Patterns

let yearlyPrice: Decimal = 29.99
Text("$29.99")
Text("$2.50 / month")
Text("Save 60%")
Text("7-day free trial")
Text("Was $59.99").strikethrough()
String(format: "$%.2f / mo", monthly)

Allowed Patterns

Text(package.storeProduct.localizedPriceString)

if let trial = package.storeProduct.freeTrialDescription {
    Text(trial)
}

if let savings = annual.savingsPercent(comparedTo: weekly) {
    Text("Save \(savings)%")
}

The helper methods may compute values from StoreKit/RevenueCat package data, but the view layer should not invent pricing strings.

Release Audit

Before submission, scan Swift source for:

• Numeric price literals.
• Hardcoded currency symbols in paywall copy.
• Hardcoded /mo, /month, /yr, /year, /week labels attached to prices.
• Hardcoded savings percentages.
• Hardcoded trial durations.

All matches must be derived from StoreKit/RevenueCat data or replaced with generic copy.

Metadata Copy

App Store metadata should avoid price literals unless the team is prepared to verify and update them before every release. Prefer generic copy such as "Choose annual for the best per-month value" over specific numbers.

Apple Review

Auto-renewing subscriptions must clearly disclose subscription length, price, and renewal terms. The safest implementation is to display the values returned by StoreKit or RevenueCat for the current storefront.