watchos-design-guidelines

Provide Apple Watch interface design guidelines and evaluation checklists for watchOS apps.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/helmordev/litera-quest --skill watchos-design-guidelines-helmordev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watchos-design-guidelines
Source: https://github.com/helmordev/litera-quest/tree/main/.github/skills/watchos-design-guidelines
Command: npx skills add https://github.com/helmordev/litera-quest --skill watchos-design-guidelines-helmordev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

These guidelines solve the challenge of designing and evaluating Apple Watch apps that must communicate information instantly and support wrist-specific interactions. They help designers and engineers prioritize glanceability, efficient navigation, correct Digital Crown behavior, meaningful complications, and safe Always On handling so that watch experiences are fast, legible, and contextually relevant.

Core Features & Use Cases

  • Glanceability rules and metrics: Clear limits for what must be visible within two seconds, text sizes, and hierarchy guidance.
  • Digital Crown & interaction guidance: Best practices for Crown-driven scrolling, pickers, haptics, and non-conflicting system behaviors.
  • Navigation and structure: Recommendations for shallow hierarchies, TabView usage, and limiting modal interference.
  • Complications & timeline strategy: Family support, tinted vs full-color variants, timeline updates, and tap-to-context rules.
  • Always On, Workouts & Notifications: Rules for dimmed states, live metrics, haptics, Auto-Pause, and Short/Long Look notification design.
  • Evaluation checklist: Actionable checklist to assess glanceability, navigation depth, complication support, Always On design, workout UX, and notification brevity.
  • Use Case: Use this to review a new watch app screen, ensure the primary metric is glanceable, verify complication compatibility, and validate Crown-driven interactions.

Quick Start

Ask the guidelines to evaluate a watchOS screen for glanceability, Digital Crown behavior, complications compatibility, Always On handling, and notification suitability.

Frequently Asked Questions about watchos-design-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design glanceable Apple Watch interfaces?

Design glanceable Apple Watch interfaces by ensuring primary metrics are visible within two seconds, using clear text size limits and hierarchy rules. Apply shallow navigation structures to prevent modal interference and fast legibility.

What are the best practices for Digital Crown interactions in watchOS apps?

Digital Crown interactions should support Crown-driven scrolling and pickers without conflicting with system behaviors. Use proper haptics and ensure Crown inputs map cleanly to live metrics during workouts and list navigation.

How do I design complications for Apple Watch apps?

Design complications by supporting specific family templates, providing tinted and full-color variants, and updating timelines efficiently. Apply tap-to-context rules so users jump directly to relevant app screens from the watch face.

Can I evaluate my watchOS app for Always On state compliance?

Yes, you can evaluate Always On state compliance using a testable checklist to verify dimmed states, live metric visibility, and safe workout Auto-Pause handling. Ensure your UI degrades gracefully without persistent bright elements.

What is the recommended navigation depth for watchOS apps?

The recommended navigation depth for watchOS apps is strictly shallow hierarchies using TabView. Limit modal interference and ensure users reach core functionality with minimal swipes or taps on small screens.

How should I format Apple Watch notifications for brevity?

Format Apple Watch notifications for brevity by designing concise Short Look and Long Look interfaces. Prioritize critical information, limit text length, and use haptics to deliver context without forcing users to raise their wrists.