Family Sharing for iOS Subscriptions: Should You Enable It?

Family Sharing lets a customer share an eligible auto-renewable subscription with their family group, so one purchase can cover up to six people. You turn it on per subscription in App Store Connect, and from then on StoreKit tells your app whether a customer's access came from their own purchase or from a family member who bought it. Enabling it is a real product decision: it can lift conversion and retention, but it also means fewer individual sales, so it is worth thinking through rather than toggling on by reflex.

This post covers what can be shared, how to enable it, how to detect family-shared access in StoreKit 2 and RevenueCat, how it interacts with free trials, and the revenue tradeoff behind the decision.

On this page

• What Family Sharing covers
• Enabling it in App Store Connect
• Detecting shared access in code
• How it interacts with trials and offers
• The revenue decision
• Common gotchas
• FAQ

What Family Sharing covers

A Family Sharing group is up to six people: one organizer and up to five members. When a purchase is shareable, everyone in the group gets access without paying again. For in-app purchases, two kinds are eligible: auto-renewable subscriptions and non-consumable purchases. Consumables cannot be shared, since they are used up by whoever buys them.

Sharing is not automatic for subscriptions. You mark a subscription shareable in App Store Connect, and only then does one member's purchase extend to the rest of the family. The customer still manages and pays for the subscription as an individual; Family Sharing only changes how many people the single purchase unlocks. For the wider lifecycle, see how an iOS subscription works end to end.

Enabling it in App Store Connect

Family Sharing is a per-product toggle. On the subscription (or non-consumable) in App Store Connect, turn Family Sharing on. Once you do, purchases of that product are shared across the buyer's family group.

One thing to know before flipping it: turning Family Sharing off later only affects future purchasers. Family members who already have shared access keep it. So treat enabling it as a decision you are comfortable living with, rather than something you will freely toggle back and forth, and make the call deliberately per subscription.

Detecting shared access in code

Most apps should unlock the same features whether access is owned or shared, but you often want to know which it is, for example to hide "manage subscription" controls from a family member who cannot change the plan. StoreKit 2 exposes this through the transaction's ownership type:

import StoreKit
 
enum AccessSource { case owned, family, other, none }
 
func accessSource(inGroup groupID: String) async -> AccessSource {
    let statuses = try? await Product.SubscriptionInfo.status(for: groupID)
    guard let status = statuses?.first(where: {
        $0.state == .subscribed || $0.state == .inGracePeriod
    }), case .verified(let transaction) = status.transaction else {
        return .none
    }
 
    switch transaction.ownershipType {
    case .purchased:    return .owned
    case .familyShared: return .family
    default:            return .other
    }
}

You can also check whether a product is even shareable before you show any family-related messaging:

if product.isFamilyShareable {
    // Safe to mention "share with your family" on the paywall.
}

RevenueCat surfaces the same distinction on the entitlement, so you do not track transactions yourself:

import RevenueCat
 
let info = try await Purchases.shared.customerInfo()
if let pro = info.entitlements["pro"], pro.isActive {
    switch pro.ownershipType {
    case .purchased:    break // the customer's own purchase
    case .familyShared: break // shared by a family member
    default:            break
    }
}

How it interacts with trials and offers

Family Sharing and introductory-offer eligibility are linked in a way that surprises people: introductory offers are shared across the family group too. If one family member uses the free trial on a subscription, the rest of the family is no longer eligible for a trial on any product in that subscription group.

That is the same per-group, per-family eligibility rule described in how to add a free trial and subscription groups, upgrades, and downgrades. The practical effect: do not promise a trial to a family member who cannot receive one. Always gate trial messaging on the actual eligibility check rather than assuming every viewer qualifies.

The revenue decision

This is the part worth actually thinking about, because Family Sharing is not free money in either direction:

• The case for it. One subscription covering a household is a strong selling point that can raise conversion, and shared access makes cancelling harder because more than one person relies on it, which helps retention. For a family-oriented app (kids' content, household utilities, health, media), it can be a genuine differentiator.
• The case against it. For an app that would otherwise sell several individual subscriptions to members of the same household, sharing replaces those sales with one. If your product is used solo (a professional tool, a single-user tracker), Family Sharing gives away revenue for little conversion benefit.

The honest rule of thumb: enable it when your app is naturally used by more than one person in a home, and be cautious when it is a single-user tool where each person would have paid on their own. It pairs with your broader pricing strategy, since the value of one shared subscription is different from several individual ones.

Common gotchas

• Consumables cannot be shared. Only auto-renewable subscriptions and non-consumables are eligible. Do not build a family feature around a consumable.
• Turning it off is not fully reversible. Disabling Family Sharing later keeps existing shared access intact and only stops new purchases from sharing. Decide deliberately.
• Trial eligibility is shared. One family member's trial spends the whole family's eligibility for that group, so gate trial copy on the real eligibility check.
• Do not assume owned access. If your UI shows account or plan-management controls, check ownershipType first, because a family member cannot manage the subscription they did not buy.
• It is off by default. A new subscription is not shareable until you enable it, so no sharing happens unless you opt in per product.

FAQ

How many people can share an iOS subscription?

A Family Sharing group is up to six people (one organizer and five members). If a subscription is marked shareable, one purchase can unlock it for the whole group.

How do I enable Family Sharing for a subscription?

Turn on the Family Sharing toggle for that subscription (or non-consumable) in App Store Connect. It is off by default, and once enabled, purchases of that product are shared across the buyer's family.

Can I tell if a customer's access is shared or their own?

Yes. StoreKit 2 exposes Transaction.ownershipType as .purchased or .familyShared, and RevenueCat exposes the same on the entitlement. Use it to tailor UI, such as hiding plan management from family members.

Does Family Sharing affect free-trial eligibility?

Yes. Introductory-offer eligibility is shared across the family group, so if one member uses the trial for a subscription group, the others become ineligible for a trial in that group.

Will enabling Family Sharing reduce my revenue?

It depends on your app. For household or family apps it can raise conversion and retention enough to be worth it. For single-user tools where members of a home would each have subscribed, sharing replaces several sales with one.

Can I turn Family Sharing off later?

You can, but it is not fully reversible: family members who already have shared access keep it, and only future purchases stop being shared. Treat enabling it as a lasting decision.

Whether or not you enable Family Sharing, the subscription underneath it still has to be created, priced, and wired to a paywall that reflects the entitlement, which is the slow part. Spaceport handles it: it creates and prices your subscription products in App Store Connect through the API, matches them in RevenueCat, and generates a SwiftUI project with the paywall, purchase, and restore flow already in place and reading the entitlement (which honors family-shared access automatically). Flipping Family Sharing on then becomes a single App Store Connect toggle on a product that already works. And when you are lining up a waitlist and launch-day audience for the app, our sister tool Lighthouse covers that side.

From an indie iOS dev, for indie iOS devs.

Read more at spaceport.build