https://developer.apple.com/design/human-interface-guidelines/machine-learning

What this source teaches

  • Cross-check existing capability, agency, uncertainty, privacy, and feedback contracts against Apple's ML design considerations — in particular: show only high-confidence results, provide easy correction, and design graceful degradation.
  • Do not use the existence of an ML capability as justification for a feature; require a clear user benefit and a tested degraded-state.
  • Add privacy considerations for on-device vs. server-side ML as a capability disclosure requirement.

Where AwesomeDS applied it

Implementations and artifacts

No directly linked artifacts.

Caveats & anti-imitation

Transfer product-level ML design considerations (capability, privacy, correction, degradation); do not import Apple platform APIs or iOS-specific interaction patterns as cross-platform requirements.

Evidence: first-party-guidance · Verified 2026-07-16 · Cadence 90d