App rejected (3.1.1) use of codes to access content

So, my app got rejected 😟


I'm writing to ask if the reviewer is correct in rejecting the app for the reason given. I've replied to the reviewer in the Resolution Center but I've just been told to remove the functionality.


An extremely brief overview of the app functionality:


  • "Teacher" users create "interactive lesson" content. Lessons are saved on an external database.
  • "Student" users use the app to access lessons created by teachers.
  • (This is where the problem lies) In order to access the lesson content, students need a "Lesson ID". Students enter this ID upon loading the app and they are immediately presented with their teacher's lesson.


The reviewer gave the following reason for the rejection:


Guideline 3.1.1 - Business - Payments - In-App Purchase

Your app unlocks or enables additional functionality with mechanisms such as promo codes, data transfer codes, license keys, augmented reality markers, or QR codes, which is not appropriate for the App Store.


Here are the reasons I disagree with the rejection:


  1. Creating content and viewing content is completely free of charge. Although I understand this may be irrelevant in this context.
  2. All created content is accessible to all users. The “Lesson ID” mechanism could essentially be replaced with a list of all lessons but this would be inappropriate once there are many lessons in the database. Entering a “Lesson ID” is simply a user friendly way of finding your lesson.
  3. The code does not unlock or enable additional functionality as mentioned in 3.1.1. The code is simply referencing content stored on a database.


It's causing me a fair amount of stress because this isn't some missing metadata or something that can be easily altered. This functionality is the whole concept of the app. Users need to be able to reference content on a database.


My question is:


Is the reviewer correct? I feel I have a legitimate claim on the contrary. Is it possible that the functionality of my app has been misunderstood in this case? Do reviewers make mistakes or are they infallible, part silicone app deities? Is it worth submitting an appeal?

(This is where the problem lies) In order to access the lesson content, students need a "Lesson ID". Students enter this ID upon loading the app and they are immediately presented with their teacher's lesson.


If you are charging someone for those "Lesson Id"s then the reviewer is correct. You must charge through IAP.


If you are not charging anyone and instead are using the Lesson ID for other purposes then the reviewer is sort-of-wrong. An appeal is appropriate pointing out the reason for needing the Lesson ID and indicating that no charges are involved.


And.....if there are charges then you might be able to operate as a 'Reader App':


3.1.3(a) “Reader” Apps: Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, video, access to professional databases, VoIP, cloud storage, and approved services such as classroom management apps), provided that you agree not to directly or indirectly target iOS users to use a purchasing method other than in-app purchase, and your general communications about other purchasing methods are not designed to discourage use of in-app purchase.

Thanks very much for the reply. It's really helpful. I'm going to submit an appeal.


As you mentioned, all content is free to use and free to create. This is also in my terms of service.


I don't know much about reader apps to be honest. I imagine they wouldn't work because the activities in the lessons are all interactive - you have to drag and drop stuff around. I will definintely check them out.

Eventually has your app been accepted?

Don't get too stressed out about rejections. Sometimes rejections have valid reasons. But sometimes they are totally bogus. I don't recommend an appeal unless you have a very good reason. And in this case, you don't.


The App Store is just an ocean of scams. There is no way for Apple to distingish between scammers and honest people who haven't thought about all they ways there might be to try to run scams.


Please see PBK's post for an easy solution. Just setup a website where people can register for an account. (Don't forget to research the GDPR and other privacy regulations). Then allow people to use the app with a login. As an added bonus, you can track people's lessons and lots of other stuff.

App rejected (3.1.1) use of codes to access content
 
 
Q