hig-components-status

Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: "progress indicator", "progress bar", "loading spinner", "status bar", "activity ring", "progress display", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says "how do I show loading state," "should I use a spinner or progress bar," "what goes in the status bar," or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "hig-components-status" with this command: npx skills add raintree-technology/apple-hig-skills/raintree-technology-apple-hig-skills-hig-components-status

Apple HIG: Status Components

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

Key Principles

  1. Show progress for operations longer than a second or two.

  2. Determinate when duration/percentage is known. A filling progress bar gives users a clear sense of remaining work. Use for downloads, uploads, or any measurable process.

  3. Indeterminate when duration is unknown. A spinner communicates work is happening without promising a timeframe. Use for unpredictable network requests.

  4. Prefer progress bars over spinners. Determinate progress feels faster and more trustworthy.

  5. Place indicators where content will appear. Inline progress near the content area, not modal or distant.

  6. Don't stack multiple indicators. Aggregate simultaneous operations into one representation or show the most relevant.

  7. Don't hide the status bar without good reason. Reserve hiding for immersive experiences (full-screen media, games, AR).

  8. Match status bar style to your content. Light or dark for adequate contrast.

  9. Respect safe areas. No interactive content behind the status bar.

  10. Restore the status bar promptly when exiting immersive contexts.

  11. Activity rings are for Move, Exercise, and Stand goals. Don't repurpose the ring metaphor for unrelated data.

  12. Respect ring color conventions. Red (Move), green (Exercise), blue (Stand) are strongly associated with Apple Fitness.

  13. Use HealthKit APIs for activity data rather than manual tracking.

  14. Celebrate completions with animation and haptics when rings close.

Reference Index

ReferenceTopicKey content
progress-indicators.mdProgress bars and spinnersDeterminate, indeterminate, inline placement, duration
status-bars.mdiOS/iPadOS status barSystem info, visibility, style, safe areas
activity-rings.mdwatchOS activity ringsMove/Exercise/Stand, HealthKit, fitness tracking, color

Output Format

  1. Indicator type recommendation with rationale (determinate vs indeterminate).
  2. Timing and animation guidance -- duration thresholds, animation style, transitions.
  3. Accessibility -- VoiceOver progress announcements, live region updates.
  4. Platform-specific behavior across targeted platforms.

Questions to Ask

  1. Is the duration known or unknown?
  2. Which platforms?
  3. How long does the operation typically take?
  4. System-level or in-app indicator?

Related Skills

  • hig-components-system -- Widgets and complications displaying progress or status
  • hig-inputs -- Gestures triggering progress states (pull-to-refresh)
  • hig-technologies -- HealthKit for activity ring data; VoiceOver for progress announcements

Built by Raintree Technology · More developer tools

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

hig-foundations

No summary provided by upstream source.

Repository SourceNeeds Review
General

hig-patterns

No summary provided by upstream source.

Repository SourceNeeds Review
General

hig-platforms

No summary provided by upstream source.

Repository SourceNeeds Review
General

hig-technologies

No summary provided by upstream source.

Repository SourceNeeds Review