0
0 Comments

Submitted

But rejected.

Our monetization plan was to use consumable In App Purchases for unlocking certain features. We knew that will most likely be not approved by Apple, since when a user "unlocks" something, it has to be made available forever, so a non-consumable IAP has to be used.

The idea was that we have platform-specific accounts, so a person might want to create several accounts, which is not possible with non-consumables. So we tried our luck with consumables.

Surely enough, we got rejected. So we reworked our logic a little to make use of non-consumables like this:

  • If you're purchasing, activate the feature on the current account.
  • If you're restoring purchases on the same account (due to a reinstall, for example) you'll end up not calling Apple's servers at all, since the account is marked on our server as having the features unlocked.
  • If you're trying to purchase again on another account, you'll get a failure, with a message saying that you already purchased this and you should login with x*****y to use the features.
  • If you're restoring purchases on another account, you'll end up doing the same thing as above.

It's not perfect: users will be able to upgrade only one account, but that's what the vast majority of users will do anyway.

We submitted again and waiting on Apple's answer.

Premature optimization and premature thinking of all scenarios is bad. You might end up not needing any of it.

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 49 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 18 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments