Skip to content
AppDues
Log in
Contact salesSign up

Implement Apple Family Sharing in your iOS app

Apple's Family Sharing lets one purchase reach several people, but for subscriptions and other in-app purchases the engineering details matter: which products can be shared, how a family member's transaction arrives, how to tell a shared entitlement from a direct one, and what you cannot test before release. This guide walks through the product decision, the App Store Connect toggle, the receipt fields you must respect, and the user-experience gaps that appear when someone receives access without ever seeing your paywall.

What Family Sharing covers

Family Sharing is an Apple platform feature for sharing digital purchases among members of an iCloud family group. Movies, books, TV shows and apps were shareable before in-app purchases were. That gap mattered: a free app with a subscription could display the Family Sharing badge on its App Store page while the subscription itself could not be shared, which could leave buyers feeling misled. Apple changed this in December 2020, and in-app purchases, including subscriptions, became shareable.

Two compatibility rules shape what you can offer:

  • Only non-consumables and subscriptions are shareable. Consumables are excluded, so a pack of coins bought by one person does not multiply across the household.
  • Shared purchases work on older iOS and macOS versions, but the interface for managing shared subscriptions appears only on more recent macOS and iOS releases. tvOS and watchOS do not yet provide that management interface.

How a family group shares a purchase

An iCloud Family account can include up to six people. The "Share with Family" control lives in Settings on iOS or macOS, or on icloud.com. The purchaser can share every eligible subscription at once or pick individual subscriptions.

When sharing begins, whether because a new shareable product was bought or because an existing purchase was switched to shared, a transaction is added to the payment queue for each family member. Your app should start observing that queue as early as possible in its lifecycle, validate the incoming transaction, and unlock content for the recipient.

Trade-offs to weigh before you enable it

Family Sharing is enabled per product, and the setting is permanent for that product. That single fact should drive the decision more than any short-term engagement argument.

Potential benefits include more people using premium features within one household, stronger perceived value and loyalty, informal recommendations between family members, additional ratings and reviews, and a simpler catalogue because you do not need a separate family plan alongside individual plans. The purchaser makes one purchase and chooses whether to share it; that choice can change later without altering the original transaction.

Potential costs include fewer subscriptions sold per household, which can offset engagement gains, and a hard geographic limit: sharing does not work when family members are in different countries. For transnational families, the feature simply will not deliver.

A practical pre-flight checklist:

  1. Confirm the product is a non-consumable or subscription, not a consumable.
  2. Model the revenue effect of one purchase serving up to six people.
  3. Check whether your audience includes cross-border families.
  4. Accept that the per-product toggle cannot be reversed.
  5. Decide how the paywall will explain sharing before you switch it on.

Enabling the product in App Store Connect

Open App Store Connect, locate or create the product, and turn on Family Sharing for it. The switch is per product. Apple does not allow it to be turned off afterward, and the reason is continuity: a family that relies on a shared subscription should not lose access mid-term because the developer changed their mind.

After enabling, existing subscribers who already have an iCloud family configured receive a notification that their subscription can now be shared. Your paywall should say so explicitly. The isFamilyShareable property on SKProduct lets you show a callout only for products that qualify, so the message never appears on a product that cannot be shared.

Granting access and handling revocation

A minimal implementation needs no special code: Apple designed the feature so most apps keep working. A complete implementation handles two moments.

Granting. Observe the transaction queue early, validate the transaction with the /verifyReceipt endpoint, and unlock the content for the recipient.

Revoking. Apple added paymentQueue(_:didRevokeEntitlementsForProductIdentifiers:) to SKPaymentTransactionObserver. It fires when a shared purchase stops being available to the user, for example when someone leaves the iCloud family or sharing is turned off for that purchase. Revoke access when it fires. The same purchase also appears as expired in /verifyReceipt, so a receipt refresh can catch users who never reopened the app at the moment of revocation.

Timing differs by scenario. A newly purchased subscription does not appear on family members' devices immediately; roughly 60 minutes pass before it becomes available to them. The pause gives the purchaser room to reconsider, for instance when the content is not appropriate for children. Turning on sharing for a subscription that was already purchased has no such delay, because the intent to share is already explicit.

Counting revenue without double-counting

Shared transactions arrive for each family member, so naive counting inflates revenue. The receipt distinguishes the two cases through in_app_ownership_type.

  • The purchaser's receipt carries in_app_ownership_type with the value PURCHASED.
  • Each family member receives a transaction with a new web_order_line_item_id and original_transaction_id, and in_app_ownership_type with the value FAMILY_SHARED.

Count only transactions where in_app_ownership_type = PURCHASED when calculating revenue. Do not attempt to reconstruct the family structure on your backend: Apple deliberately makes that difficult to protect privacy, and there is no benefit to doing it. After the receipt is in hand, the usual work continues: refresh receipts, track expiration dates, and so on.

A worked example: one subscriber buys a Pro subscription. Their receipt shows PURCHASED. Three family members each receive a transaction marked FAMILY_SHARED, each with its own identifiers. If you counted all four, you would report four sales for one payment. Filtering on PURCHASED keeps the figure accurate while still granting access to all four people.

The user who never saw your paywall

A direct buyer passes through the paywall, reads the benefits, and may even see a tutorial. A family member who receives shared access skips all of that and can open the app with premium features already unlocked, without knowing what those features are. Use in_app_ownership_type from /verifyReceipt to tell them a family member shared access and to explain what they now have.

Introductory pricing needs the same care. When you compute eligibility, do not filter out FAMILY_SHARED transactions. If the purchaser already used an introductory offer and shared the subscription, the family members should not become eligible for that same introductory price.

What you can and cannot test

Family Sharing does not function in the Sandbox environment. There is no faithful way to rehearse it before production.

The nearest approximation produces a new transaction in the payment queue: purchase a subscription, let it expire naturally, then go to Settings > App Store > Sandbox Account > Manage Subscriptions and subscribe again. Reopening the app surfaces the new transaction, which resembles the queue event a family member generates. This checks that your queue observation does not miss events, but the receipt will not carry in_app_ownership_type set to FAMILY_SHARED.

Revocation cannot be simulated at all. Treat the revocation callback as code that must be correct by inspection: confirm you subscribe to the payment queue and that paymentQueue(_:didRevokeEntitlementsForProductIdentifiers:) is implemented and wired to remove access.

Field and control map

The following map connects each decision point to the artifact that carries it. Use it as an implementation checklist rather than a code sample.

  • Product eligibility: App Store Connect per-product Family Sharing switch; non-consumables and subscriptions only.
  • Paywall visibility: SKProduct.isFamilyShareable, exposed through the Package in each Offering.
  • Purchaser receipt: in_app_ownership_type = PURCHASED.
  • Recipient transaction: in_app_ownership_type = FAMILY_SHARED, with its own web_order_line_item_id and original_transaction_id.
  • Revocation: paymentQueue(_:didRevokeEntitlementsForProductIdentifiers:) plus expired status in /verifyReceipt.
  • Revenue filter: count PURCHASED only.
  • Intro eligibility: include FAMILY_SHARED transactions in the eligibility computation.
  • SDK-level ownership: if your subscription SDK exposes an ownership_type field on its entitlement model, use it to distinguish a direct purchase from Family Sharing access. Confirm the exact field and minimum version in your own SDK's documentation before relying on it.

Frequently asked questions

Which in-app purchase types can be shared with a family?

Non-consumables and subscriptions. Consumables are excluded so that a single purchase of, say, a coin pack does not grant the same balance to every family member.

Can Family Sharing be turned off after it is enabled?

No. The switch is set per product in App Store Connect and cannot be reversed. Apple's rationale is that a family relying on a shared subscription should not lose it because the developer later changed the setting.

Why does a shared subscription take about an hour to appear?

New purchases are held for roughly 60 minutes before becoming available to family members, giving the purchaser time to decide whether to share. Turning on sharing for a subscription that was already purchased has no delay.

How do I avoid counting a shared purchase more than once?

Count only transactions whose in_app_ownership_type equals PURCHASED. Family members' transactions carry FAMILY_SHARED and should grant access but not add revenue.

Can I test Family Sharing in Sandbox?

No. Sandbox does not support it. A re-subscribe flow can exercise queue observation, but it will not produce a FAMILY_SHARED receipt, and revocation cannot be simulated.

Does Family Sharing work across countries?

It does not work when family members are located in different countries, which limits its usefulness for transnational families.