Apple HIG: Interaction Patterns

Read .claude/apple-design-context.md if the project provides it; treat it as project context, not a required global configuration. Ask only for missing platform, task and user constraints.

Key Principles

1. Minimize modality. Use modality only when it is critical to get attention, a task must be completed or abandoned, or saving changes is essential. Prefer non-modal alternatives.

2. Provide clear feedback. Important state changes need perceivable feedback; combine accessible visual/status text with optional sound or haptics, without announcing every incidental interaction. Activity indicators for indeterminate waits, progress bars for determinate, haptics for physical confirmation.

3. Support undo over confirmation dialogs. Destructive actions should be reversible when possible. Prefer undo when an action is genuinely reversible. Irreversible deletion, payments or external sharing may still need clear scope and confirmation.

4. Launch quickly. Display a launch screen that transitions seamlessly into the first screen. Avoid branding-only launch screens; a brief optional splash after launch can be appropriate if it does not obstruct the task. Restore previous state.

5. Defer sign-in. Let users explore before requiring account creation. Support Sign in with Apple and passkeys.

6. Keep onboarding brief. Keep the flow as short as the task permits; three screens is a heuristic, not an Apple requirement. Let users skip. Teach through progressive disclosure and contextual hints.

7. Use progressive disclosure. Show essentials first, let users drill into details. Don't overwhelm with every option on one screen.