Why it matters
A missing usage description crashes the app when it asks for permission, and vague text is a common App Review rejection.
Tick what your app uses and adjust the generated wording.
How to use it
- Type or paste your input; the example shows the format.
- Press Build keys. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
What makes a good description?
Say which feature needs it and why, e.g. 'to scan receipts'.
Where does the XML go?
Inside the top-level dict of Info.plist, or in Xcode's Info tab.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.