Document Browser App Review checklist

Define document types and ownership

List each supported file type, import type, export type, preview type, and custom extension. A file type advertised in metadata should be openable from Files and share routes without special setup.

If the app creates a proprietary format, provide sample documents and a clear route for users to export or recover their work.

Test the full document lifecycle

• Create a new file, edit it, save it, close it, and reopen it.
• Import from Files, iCloud Drive, local storage, and share sheet where supported.
• Export to a standard format and verify the exported file opens elsewhere.
• Rename, duplicate, move, delete, and recover documents.
• Handle corrupted, unsupported, locked, and too-large files gracefully.

Plan cloud and conflict behavior

Document apps often interact with iCloud Drive, third-party file providers, and local files. Test editing a file while offline, changing it from another device, and returning to the app after the provider updates the file.

AppReviewReady interpretation: conflict messages should help users protect work, not expose implementation details. If the app chooses last-writer-wins, make sure that is a conscious product decision.

Protect document content and thumbnails

1. Check whether document contents, filenames, thumbnails, and metadata leave the device.
2. Verify autosave, crash recovery, recent documents, and thumbnails do not expose private files after logout.
3. Test password-protected or encrypted files if supported.
4. Confirm account deletion and local deletion behavior are clear.
5. Check App Store screenshots use owned or fictional documents.

Prepare document review evidence

Provide a sample document when the app's value depends on non-obvious content. The reviewer should not need to author a complex file just to test the main workflow.

After every schema change, test older documents from the previous public version. Reviewers may open sample files created by older builds, and users will expect their documents to migrate without data loss.

If documents can contain private media or client data, decide whether recent-document thumbnails should be hidden after sign-out or account deletion.

For collaboration or shared folders, test revoked access while a document is open. The app should save local recovery data only when that matches the product's privacy promise.

For template-based products, separate sample templates from user documents in the review path. A reviewer should be able to tell which files are safe examples and which actions create persistent user content.

Document app review path:
Supported types: [types]
Sample document: [included or steps]
Create/edit/save route: [steps]
Import/export route: [steps]
Conflict behavior: [summary]
Private content handling: [local/cloud]
Recovery behavior: [autosave/backups]