Thread by @jordibruin

I’ve been doing daily updates for the last few days for both the iOS and macOS versions of Navi and wanted to share a bit about how I minimise the changes of getting caught in App Review

👇🧵

For every update I write a short message to App Review explaining what’s been changed in this version. I link to a demonstration video that shows the general way the app is used, and also link to…

A notion page that I keep up to date with information about Navi.

- It includes demo videos of iOS and macOS.
- Information about previous rejections and the outcome
- Videos demonstrating where the IAP can be purchased

Since the app uses the SharePlay framework in a novel way, I want to be ahead of them by owning this with a clear instruction video:

Making a short recording with a VoiceOver of where the IAP can be purchased, what they give users, and any other information around it makes it a lot easier for the reviewer to understand your apps’ flow.

After a rejection in 1.1 I made some adjustments, and added those to the document as well so that the context remains visible later on.

Some written instructions on how to test the main use case of the app.

And finally, a Changelog of the previous versions (which the reviewer can also see in their own systems but it’s still useful for me).

If you have any suggestions on what I should add, or what has worked for you. Let me know!