« Google's rumoured Android TV dongle could launch soon | Main | Apple iPhone 12 Pro might miss out on 120Hz screen »
Monday
Aug242020

Apple issues apology for dispute with WordPress

Old versions of the WordPress app on iOS had Plans tab, but in-app purchases aren't available on the app

While Apple's legal battle with Epic Games rages on, it is resolving its issue with WordPress. The tech giant even issues a rare on-the-record apology to the blogging platform after it forced WordPress to monetize its free app. If WordPress offers in-app purchases, it would be giving Apple 30% of what it earns from these.

Apple's full statement reads: "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."

As The Verge points out, Apple is wording this as the developer having worked the issue out by removing the "display of their service payment options from the app." While that might be true, that removal happened weeks or months ago. The WordPress app on iOS doesn't sell anything or make any mention of paid "WordPress.com" plans. Older versions of the app once had a dedicated "Plans" tab, which showed the different options available for premium customers. But you can't purchase any plans on the app. 

The news and succeeding outrage broke when WordPress developer Matt Mullenweg shared that Apple successfully forced him to add Apple's in-app purchases. He was going to be locked out of updating the app unless he added the feature within 30 days. 

Mullenweg said he even offered previously to take out other mentions of paid plans from the app, only to have Apple reject the suggestion.

So, while Apple is framing this as WordPress caving, it would seem like Apple has just decided it's not worth getting additional flak by forcing WordPress to include in-app purchases.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>