We submitted a Lite version of our iPad book app a couple of weeks after the paid version was accepted into the app store. To our surprise, the Lite version was rejected by Apple. Our Lite version has just the 1st of the 8 chapters of our graphic novel, along with a call to action page to purchase the full app. Here’s part of what they wrote to us:
Developers “spamming” the App Store with many versions of similar apps will be removed from the iOS Developer Program
We found that your app provides the same feature set as other apps you’ve submitted to the App Store; it simply varies the content or language.
Apps that replicate functionality with different content create clutter in the App Store, hindering users’ ability to find apps, and do not comply with the App Store Review Guidelines.
Additionally, apps that use the same - or very similar - icons also make it difficult for users to find apps and are considered a form of spam. For information on Application Icons, please see the iOS Human Interface Guidelines.
Apps based on a common feature set should be combined into a single container app that uses the In App Purchase API to deliver different content. For example, it would be appropriate to consolidate the following apps, using In App Purchase:
Be Confident in Who You Are: A Middle School Confidential™ Graphic Novel
Be Confident in Who You Are (Lite): A Middle School Confidential™ Graphic Novel
To be in compliance with the App Store Review Guidelines, it would be appropriate to revise your app to use the In App Purchase API to provide content purchasing functionality.
They then provided links to give more info on in-app purchases.
I asked for the decision to be appealed and got a call from an Apple representative a week later. He told me that our Lite version would still not be accepted and that this has been Apple’s policy since August (I assume when in-app purchasing was started).
I told him that there were 38 newly released Lite versions in the iPad Books section of the app store in April alone. He was really surprised and asked me to supply him with the list (which I did). He was going to forward that to people in Apple to research and find out why the policy wasn’t being consistently carried out (though I did notice that there were no new versions after April 24, which is about when mine was rejected). I don’t think this affects updates to Lite versions that have been released earlier.
It’s possible that the policy was in place before but not enforced until around April 22nd.
I asked if this was the same case for other types of apps, and got an unclear answer back.
I actually think this is a good policy. I was just frustrated that I didn’t know about it beforehand (or that it hadn’t been consistently enforced before). Our main problem is in coming up with a solution on how to convert our paid app into a free one that has the first chapter available, with the rest accessible via IAP.
If someone purchased the app before, and then does an “upgrade” to the IAP enabled version, I want to make sure they don’t get asked to pay again for the locked content.
I have a partial solution, and wanted to see if anyone else has gone through this process, and also kept the previous owners of the app happy!
In our current version, we save a file every time the app is exited which contains bookmark info on where the person was in the app. So it would be possible to detect that file on startup and unlock the content the first time (if the file is there but doesn’t contain a lite-version-specific value, it must be the earlier paid version).
The problems would arise if the person reinstalled the app (no file?), if they purchased the original app but never launched it, if they paid for it on one device and then reinstalled on another, etc. In those situations, I’d have to provide a way for someone to ask for help (email?), and then provide some sort of unlock code.
(Which brings up another question… If I create a sort of backdoor unlocking mechanism, then wouldn’t that mean I’d never need promo codes again? I’d have a reviewer download the app, and provide them with the backdoor code, and it would open it up for full use. How would Apple feel about that? I’d be providing the same functionality as a promo code, but handling it myself and wouldn’t be limited by the number of promo codes I could get.)
I’d have to make sure my unlock code was unique for each person so it couldn’t be posted on a message board for anyone else to use. No idea how to do that yet… unless I post the valid codes in a database on my server and cross off each one once it’s used…
One final note. I explained the above problem to the Apple rep. He suggested discontinuing our old app and launch a new free version that met their standards. That would mean no updates for the “orphaned” original version.
I’d really appreciate any thoughts you have, if you faced a similar situation, and how you handled it without upsetting your customer base!
Thanks!!
[import]uid: 9905 topic_id: 9642 reply_id: 309642[/import]