apple-interface-writinglisted

# Apple interface writing Use language as part of the interaction. Make each screen's purpose, choice, and result understandable with minimal text. ## Protect interaction truth - Preserve the actual action, consequence, permission, data state, and recovery path. - Do not make a destructive action sound reversible. - Do not claim data is saved, private, secure, or recoverable without evidence. - Respect supplied character, localization, platform, and accessibility constraints. ## Define voice, then adapt tone Choose a stable app voice from its audience and purpose. Adapt the tone to the moment: - Routine action: neutral and direct. - Success: specific and proportionate. - Delay or interruption: calm and informative. - Error or loss risk: serious, plain, and recovery-focused. - Permission request: transparent about purpose and user benefit. Do not copy a recognizable corporate personality. Apply the interaction principles to the product's own voice. ## Write each screen 1. State the screen's single purpose and the decision or action it supports. 2. Put the most important information before explanation. 3. Use a verb for an action label and make the label predict the result. 4. Keep terminology and navigation labels consistent across the flow. 5. Use supporting text only for a consequence, requirement, unfamiliar concept, or choice that the label cannot carry. 6. Make completion, cancellation, and the next step explicit. ## Write errors and alerts - Name the proble