I like to have as little UI elements as possible: since these in-App Purchases can be “ re-bought” for free, I didn’t implement a Restore button.Īfter explaining my logic above, the App Review replied: That’s too bad, because these in-App Purchases were the reason of the new rejection.Īll my in-App Purchases are non-consumable: once the user buys one, this purchase can be “ bought” (again) as many times as the user wants, for free. While waiting for each review, I kept adding more and more features to the app, at some point I even added some non-consumable in-App Purchases. Time for another submission! Third Rejection My two additions to comply with App Store Review 14.3 Guideline Luckily for me, Twitter API offers everything I need: Lesson learned: if your app shows user generated content, implement a flag/moderator/block mechanism, even if the content is not created within your app. The App Review Board replied to my appeal within a few hours. I felt that the Guideline 14.3 didn’t applied to my case so I wrote an appeal with the reasons above: If a user were to flag a Tweet, that Tweet would be old already: it would never be displayed on the App again, ever! My app doesn’t let the user generate any content: it just shows you Twitter’s content (where you can report/flag/block anything/anyone you want).Įven if I were to implement what I was asked to, the App uses only real time data, it would be of no use to the app itself. This time the App Review Team summoned the App Store Review 14.3 Guideline (under the Personal attacks chapter):ġ4.3 Apps that display user generated content must include a method for filtering objectionable material, a mechanism for users to flag offensive content, and the ability to block abusive users from the service Luckily there’s no need to change the App binary, let’s change the description and re-submit the app! Second Rejection The App Store Review 3.1 Guideline is as clear as it gets: this rejection is completely my fault. Android”:ģ.1 Apps or metadata that mentions the name of any other mobile platform will be rejected It turns out, the App Review Team didn’t even have to launch the app in order to reject it: naively, in the app description, among other keyword comparison examples, I put “iOS vs. My app was pretty simple: I was quite surprised when I woke up with a rejection in my mailbox.
See the little email above? This is the very kind way Apple uses to let you know that no, your app is not going to the App Store just yet. It’s the standard Twitter App with real-time functionalities: just input any keyword you're interested in and let the Tweets flow on your screen as they’re posted! ( here’s a 50-seconds video of the app in action). Quick description of the App I’ve submitted:
Swift is an amazing language and, after dealing with the fact that I can’t know everything there is in Cocoa Touch, there was nobody to stop me building and launching my app.
#PRETTY SIMPLE ITUNES APP STORE SOFTWARE#
Last year I finally made the jump: I bought a Macbook and started learning Swift and iOS App Development.Ībout 3 months later I submitted my first app to the App Store: I couldn’t be so proud!ĭisclaimer: I’m a Software Engineer, your mileage might vary. FebruFederico Zanetello tale of three months of Apple Review Rejections
0 kommentar(er)
