Conversation

New name: The app has always done a ton of work to support WordPresses hosted anywhere, using the XML-RPC API included in core WP since WP 2.6 was released in 2008. That's why we called it "WordPress" and not "WordPress.com" or "Jetpack."
3
230
I am a big believer in the sanctity of licenses. (Open source relies on licenses and copyright.) We agreed to this license when we signed up for (and stayed in) the app store, so going to follow and abide by the rules. Not looking to skirt it, hence doing what they asked us to.
10
179
I'm aware there are other apps with similar functionality to , and in the same market, that don't offer in-app purchase. My guess is they will get similar feedback soon so I'd encourage them to start making IAP plans.
5
76
Update:
Quote Tweet
I am very grateful that folks at Apple re-reviewed @WordPressiOS and have let us know we do not need to implement in-app purchases to be able to continue to update the app. Bad news travels faster than good, usually, so please consider sharing that they reversed course.
Show this thread
3
51
Show replies
Hey Matt, When I open the Help Center from the app, I can get guidance about upgrading to one of your paid plans. If I tap on “Plans” as seen the screenshot, the app opens Safari and shows the plans. This is a violation according to App Store Review Guidelines.
Image
Image
4
50
Here is the relevant term that your app violated: 3.1.3(a) Apps may allow a user to access previously purchased content or content subscriptions […] provided that you agree not to directly or indirectly target iOS users to use a purchasing method other than in-app purchase
Image
6
8
Show replies