Apple HIG: Content Components

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

Adapt to different sizes and contexts. Content components must work across screen sizes, orientations, and multitasking configurations. Use the layout system appropriate to the framework (SwiftUI layout or Auto Layout), and use size classes where available.
Make content accessible. Provide chart summaries and appropriate accessible data navigation; Swift Charts includes a default Audio Graphs implementation. Give meaningful images descriptive accessibility labels and hide decorative or redundant images. Collections need a logical VoiceOver navigation order.
Maintain visual hierarchy. Use spacing, sizing, and grouping to establish clear information hierarchy. Primary content should be visually prominent.
Use system components first. Evaluate UICollectionView, SwiftUI Charts, WKWebView before building custom. System components provide accessibility and adaptation defaults; still test labels, interactions and supported platform versions.
Respect platform conventions. A collection on tvOS uses large lockups with parallax. The same collection on iOS uses compact cells with touch targets. On visionOS, content gains depth and hover effects.
Handle empty states. Show a meaningful empty state with guidance on how to populate it, not a blank screen.
Optimize for performance. Use lazy loading, cell reuse, pagination, and prefetching for large datasets.