Apple gave me the Hey” treatment in 2014

I’ve been reading the news this week about Hey, Apple, and in app purchases. Many people have offered their takes on the situation, and I can’t help but feel déjà vu.

To summarize the Hey situation:

  1. Hey submits their app, which is a paid service, to the App Store. There is no way to sign up for Hey from the app since Hey doesn’t want to give Apple 30% of all transactions.
  2. Apple approves version 1.0 of the app.
  3. Hey submits a bug fix update and is rejected because they do not offer a way for users to sign up with in app purchases.

In 2014, the same thing happened to my former company, Restocks. Restocks was a subscription-based shopping app for streetwear. We offered subscriptions to the service on our website using Stripe, and a companion app on the App Store.

Releasing Restocks 1.0

Apple’s approval email

Apple’s 1.0 approval email

In July of 2014, I submitted Restocks 1.0 to the App Store. The title of the app on the App Store was Restocks (for existing members only)”. Apple approved the app.

There was no way to sign up in the app. When you downloaded the app, the only thing you saw was a log-in form. All marketing happened outside of the App Store.

The bug, and the shakedown

A couple of months later, in October, I botched an update. Push notifications were now broken. I quickly identified the problem and submitted a new build to the App Store. Since App Review at the time took up to 7 days, I applied for and was granted an expedited review request.

Request for an expedited review

My granted request for an expedited review

This may have been my mistake. A couple of hours later, Apple sends me an email saying they have feedback for my App submission.

Apple’s “feedback” for me

Apple’s feedback” notification email

This is not the regular rejection email that Apple sends. This may have been because of the expedited review, but I wonder if it means that our review got escalated to a different team internally.

Now, I can’t show you what Apple said to me, because Apple purges old Resolution Center” communications1. But here’s my memory of what happened:

  • Apple rejected my app for not implementing their In App Purchase APIs
  • I pointed out to Apple that I didn’t allow users to sign up via the iPhone, only on the website — the name of the app even included (for existing members only)”!
  • Apple replied that they didn’t care, because there needed to be a way for people to sign up in the app, since the app was useless without signing in. We had to implement In App Purchases to get the update approved and to ensure the current version of the app was not removed from the App Store.

What happened next?

The obvious thing happened next. I wasn’t prepared to fight against Apple. So, I capitulated and feverishly spent all night implementing in app purchases. There wasn’t much of a choice — remember that this began with trying to fix a critical bug in the app, and users were unhappy.

The only surprising thing to me about this Hey controversy is that someone is finally calling out Apple for something they’ve been doing for years. I hope it changes soon.

Discuss this post on Hacker News

  1. After I realized that they do this, it made perfect sense to me why Apple doesn’t directly communicate about app issues via email. They only contact developers over the phone where there isn’t a log, or via their own communication tools where they scrub old messages. This definitely lets Apple control a narrative.

June 18, 2020