Techdirt's think tank, the Copia Institute, is working with the Trust & Safety Professional Association and its sister organization, the Trust & Safety Foundation, to produce an ongoing series of case studies about content moderation decisions. These case studies are presented in a neutral fashion, not aiming to criticize or applaud any particular decision, but to highlight the many different challenges that content moderators face and the tradeoffs they result in. Find more case studies here on Techdirt and on the TSF website.

Content Moderation Case Study: Apple Blocks WordPress Updates In Dispute Over Non-Existent In-app Purchase (2020)

from the ok-landlord dept

Summary: Apple controls what apps get onto iPhone and iPads via its full control over the iOS App Store. Every app (and its updates) need to be reviewed by Apple staff before it’s allowed in the store -- and Apple puts in place its own rules for what is and what is not allowed.

One of those rules is that Apple takes a 30% cut of any sales. That fee has become somewhat controversial, especially among service providers who don’t rely on the App Store for discovery, but whose customers likely come on their own -- including Spotify and Epic Games. Spotify, in particular, has urged users to subscribe directly, to avoid having to pay the additional amount per month to cover Apple’s fees. In response, Apple forbade Spotify from even mentioning that it’s cheaper to subscribe outside of the App Store, which is now a central piece of an antitrust fight that is ongoing in the EU.

Perhaps because of all of this, Apple has had to make decisions about whether or not to allow apps in the App Store that seek to avoid paying Apple’s cut of the fees. In August of 2020, Matt Mullenweg, the CEO of Automattic, and the founder/lead developer of the WordPress content management system, announced that the iOS app for WordPress had been frozen by Apple. The given reason was that Apple believed that WordPress was trying to avoid the fees for in-app purchases.

This was the cause of much confusion, as many people noted that the app did not actually sell anything. While does offer paid hosting plans (and domain reselling), that was not a part of the WordPress app. However, as Mullenweg’s tweet showed, Apple was noting that because somewhere else in’s business, it sold things, that meant that WordPress had to pay it a 30% cut of those sales (even though they were outside of the app itself) in order to keep the app in the App Store.

Decisions to be made by Apple:

  • How thoroughly should the company be reviewing the business models of apps in the App Store to determine whether they can be included?
  • What actually constitutes an attempt to get around the App Store fee?
  • Will app developers take advantage of exceptions to the rules if Apple does not follow them closely?
  • Should the company allow alternative ways of getting apps on the phone outside of the App Store?
Questions and policy implications to consider:
  • When a company builds an entire device ecosystem, should it be able to set its own rules for what apps are allowed on the device?
  • Can content moderation decisions raise antitrust concerns?
  • Are there policy implications of a single entity reviewing what apps are allowed on a device?
Resolution: As this story got more attention, Apple apologized and restored the WordPress developer account. However, its statement on the matter implied that WordPress had “removed” an option in the app to pay for hosting plans:

We believe the issue with the WordPress app has been resolved. Since the developer removed the display of their service payment options from the app, it is now a free stand-alone app and does not have to offer in-app purchases. We have informed the developer and apologize for any confusion that we have caused.

But users of the app say it never had any in-app purchases at all. The only thing it had were descriptions of Premium offerings, but no way to buy them. Mullenweg said that, before going public, he had asked Apple if removing those mentions would restore the account, and Apple had said it would not.

The reinstatement appeared to take Mullenweg by surprise.

In January of 2021, Apple also moved to lower the cut it took for in-app payments from “small” developers (those making less than $1 million a year in annual sales) to 15%. It was also revealed that Apple quietly cut a special deal with Amazon to charge the retailer a 15% cut for Amazon’s Prime Video app.

Originally published on the Trust & Safety Foundation website.

Hide this

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

Filed Under: app store, content moderation, fees, in-app purchases, matt mullenweg, wordpress
Companies: apple, automattic

Reader Comments

Subscribe: RSS

View by: Thread

  1. icon
    Mike Masnick (profile), 28 Apr 2021 @ 11:17pm


    Apple has every legal right to do this. Doesn't mean that it's the right decision. I think there is plenty of evidence as to why this was a dumb move on Apple's part and worthy of criticism.

    I don't think it's an excuse to pass bad laws to block them from doing this.

    Either way, the case studies here are neutral and show the various difficult questions and decisions that every company has to make.

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here

Subscribe to the Techdirt Daily newsletter

Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Essential Reading
Techdirt Insider Chat

Warning: include(/home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/ failed to open stream: No such file or directory in /home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/ on line 8

Warning: include(): Failed opening '/home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/' for inclusion (include_path='.:/usr/share/pear:/home/beta6/deploy/itasca_20201215-3691-c395:/home/beta6/deploy/itasca_20201215-3691-c395/..') in /home/beta6/deploy/itasca_20201215-3691-c395/includes/right_column/ on line 8
Recent Stories


Email This

This feature is only available to registered users. Register or sign in to use it.