App Review

App review is the approval process another vendor puts between your integration and their public directory. Submitting is not publishing. A reviewer — a person, working from criteria you did not write — checks the scopes you request against what the integration demonstrably uses, how you store and transmit credentials, what happens to the customer's data when they disconnect, whether the listing describes the integration honestly, and whether your use of their name and marks follows their rules. The reason it belongs on a schedule risk register rather than a technical one is that none of it is in your control. The queue is theirs, the criteria are interpreted by a human, and a rejection typically arrives as a short note requiring a change and a resubmission — which puts you back in the queue. Review is therefore measured in rounds, not in a fixed waiting period, and a launch planned around a review date rather than around an allowance of rounds is the one that slips publicly. What passes more easily is consistent across platforms because it follows from what a reviewer can actually verify. Request fewer scopes and give a reason for each one. Provide a demonstration account a reviewer can use unaided, without scheduling time with your sales team. Make screenshots match the current product. Answer the disconnect and deletion question explicitly rather than leaving it to be inferred. And leave nothing important behind a flag the reviewer cannot reach, since anything they cannot exercise, they cannot approve. Over-scoping is the reliable thing to be caught on, simply because it is the easiest claim in a submission to check against behaviour. Treat the listing as maintained rather than achieved. Material changes are reviewed again, criteria are revised without consulting the people already listed, and an integration that has been live for years can be asked to change something to stay listed.