iOS apps monetization
With iOS apps and additional devices, the revenue distribution doesn’t change for Setapp developers. Here are the key points of the distribution logic.
- The Setapp's subscription revenue is calculated in the following way:
Let’s see that on a couple of examples.
Example 1. The monthly subscription revenue from a member who uses the Monthly plan and a single extra device is $9.99 + $2.49 = $12.48.
Example 2. The monthly subscription revenue from a member who uses the Annual plan and 2 extra devices is $8.99 + ($2.49 * 2) = $13.97.
-
The developer's revenue for an iOS app in Setapp is based on how often do the members use it — in the same way as with macOS apps in Setapp.
Since members use multiple apps, Setapp distributes 70% of the subscription revenue between all developers whose apps (macOS and iOS ones) the member opened within the billing period. For the detailed explanation and examples, see "Distributing revenue".
-
The price tier for an iOS app in Setapp is based on the price of the app’s paid functionality (in-app purchase) on the App Store — or the app’s subscription fee. See "Price tiers" for details.
If the desktop and the mobile apps are distributed with a single cross-platform subscription, the iOS app gets the same price tier as the macOS one.
Please note that the subscription fee for an extra device may be less than $2.49 — in cases when the covered period is less than 30 days. When a member starts an extra device subscription later than the 1st day of the regular subscription’s billing period, the person pays only for the remaining days until the next planned charge for the main subscription.
For example:
- IF a member’s billing period for the main subscription starts on January 1 and lasts till January 30,
- AND an extra device subscription starts on January 15,
- THEN the member pays only $1.25 (50%) at the moment of purchasing the extra device subscription.
- Still, on January 30, the additional device fee becomes $2.49 because it now coincides with the regular subscription timing.
Updated almost 2 years ago