Apple plans to reduce the commission it collects on paid apps and in-app purchases through the Taiwan storefront from 30% to 26%, effective October 31. The change applies to transactions on iOS and iPadOS and follows discussions with the Taiwan Fair Trade Commission (TFTC).
For game developers selling premium mobile games, virtual currency, subscriptions, battle passes, expansions, or other in-app content in Taiwan, the practical change is simple: Apple’s share of each covered transaction will be four percentage points lower than the previous standard 30% rate. Developers do not need to accept updated terms by October 31 to receive the reduced rate.
What the 26% commission means
An App Store commission is the portion of a qualifying transaction retained by the platform operator before the developer receives its proceeds. It is not the same as a separate fee charged directly to a player at checkout. In broad terms, under a 30% commission, a developer retains 70% of a covered sale before other possible costs. At 26%, that share becomes 74%.
For every 100 units of local-currency revenue from a covered Taiwan transaction, the difference between the two rates is four units:
- At a 30% commission, Apple retains 30 and the developer receives 70.
- At a 26% commission, Apple retains 26 and the developer receives 74.
That arithmetic does not establish what any developer will do with the difference. A studio could retain the additional revenue, spend it on development or support, adjust regional pricing, invest in marketing, or make another business decision entirely. Nothing in the announced change promises lower player prices, more content, or a specific change to a game’s monetization.
Still, the policy matters because mobile games commonly rely on in-app transactions rather than a single upfront purchase. When a title’s Taiwan revenue comes from optional purchases inside an iPhone or iPad game, a smaller platform commission increases the developer’s portion of every eligible sale at the listed price.
The timing and regulatory context
The new Taiwan rate begins October 31. Apple tied the change to discussions with the TFTC, Taiwan’s competition authority. The available details do not describe a new developer sign-up process, and Apple has said developers will not need to sign revised terms by the effective date to obtain the 26% commission.
That is an important operational detail. A reduction that required developers to opt in could create uncertainty over eligibility, paperwork, timing, or a decision to move to a different contractual arrangement. Here, the stated position is that the lower commission arrives without a requirement to sign updated terms by October 31.
The announcement identifies two transaction types: paid apps and in-app purchases. A paid app is a product bought before it can be downloaded or used in full. An in-app purchase is a transaction made within an app, such as a game’s consumable currency, permanent unlock, cosmetic item, season pass, subscription, or add-on content. Those labels describe payment categories, not genres, so the policy has implications beyond games as well.
Taiwan joins other markets with altered rates
Apple has already adopted a 26% commission rate in Japan and the European Union. In China, it negotiated a 25% commission after discussions with the State Administration for Market Regulation. Taiwan’s reduction therefore fits into a wider pattern in which Apple’s familiar 30% standard rate has been adjusted in particular markets following engagement with national or regional authorities.
The numbers are close but not identical. Taiwan’s 26% rate matches Japan and the European Union, while China’s negotiated rate is one percentage point lower at 25%. A one-point gap may look small in isolation, but it is material at scale: on 100 units of eligible transaction revenue, a 25% commission leaves 75 with the developer, compared with 74 at 26% and 70 at 30%.
That comparison should not be read as evidence that all storefront rules, developer obligations, payment options, or app-distribution conditions are the same in these territories. The information available establishes the commission figures and the regulatory discussions; it does not provide a complete, market-by-market account of the terms surrounding them. Commission percentages are a significant part of a platform relationship, but they are not the whole relationship.
What remains unclear for Small Business Program developers
Apple normally offers a lower commission rate to members of its Small Business Program. However, the Taiwan announcement does not say how the new 26% rate interacts with that program.
That omission is meaningful because a standard-rate reduction and a small-business rate are different mechanisms. One revises the ordinary commission that applies to covered storefront transactions. The other is a program that normally provides a reduced rate to qualifying developers. Without specific Taiwan details, it is not possible to state whether Small Business Program members will see any change, whether their existing rate remains in place, or how Apple will present the Taiwan terms to those accounts.
Developers should therefore avoid assuming that “26% for Taiwan” necessarily describes their own effective rate. The announced figure clearly replaces the previously stated 30% commission for paid apps and in-app purchases in the Taiwan storefront, but the available information does not spell out the Small Business Program treatment. Studios with questions about their particular account status, products, or proceeds will need to rely on the applicable App Store materials and communications rather than extrapolating from the headline percentage.
Why mobile-game businesses will pay attention
Storefront fees are a core part of mobile-game economics because they sit between consumer spending and a developer’s recognized proceeds. A premium game that costs money upfront is affected once at purchase. A free-to-download game supported by optional in-app purchases can be affected repeatedly across its revenue lifecycle, from a player’s first cosmetic purchase to a recurring subscription or ongoing content spending.
The 26% rate does not say anything about whether a particular game is successful in Taiwan. It does, however, change the share retained from qualifying App Store sales in that market. For teams managing regional budgets, live-service support, user-acquisition spending, or revenue forecasts, a four-point change is concrete input rather than abstract policy.
It also arrives in a period when platform business models remain a major industry issue. Questions over what storefronts charge, which transactions are subject to commissions, and how digital marketplaces communicate their terms extend well beyond Apple’s ecosystem. For another look at platform-policy debate in games and PC distribution, see this discussion of Steam AI labels and PC storefront claims.
What players should and should not expect
Players in Taiwan should not treat the commission reduction as an automatic discount notice. Apple’s announcement concerns the platform’s revenue share from paid apps and in-app purchases. It does not direct developers to reduce prices, prohibit price changes, or require games to offer extra currency, content, or benefits.
In practice, players may see no immediate visible change at all. App pricing is determined by developers and publishers, and games differ in how they structure purchases. Some use fixed-price premium downloads; some depend on many low-cost optional transactions; others use subscriptions or mixtures of several models. The same four-point commission reduction can therefore have different financial significance across different titles.
For developers, the clearest confirmed takeaway is narrower: starting October 31, covered paid-app and in-app-purchase transactions through Apple’s Taiwan iOS and iPadOS storefront will use a 26% commission rather than 30%, with no updated-terms signature required by that date. The announced details leave the Small Business Program question unresolved, so developers should be careful not to infer terms that have not been specified.








