Wearable glance

Problem Context

• The surface is a smartwatch complication, tile, widget, band screen, wearable card, always-on display, ongoing activity, or quick wrist status.
• Users may be walking, exercising, commuting, working, driving, wearing gloves, in sunlight, in focus mode, under notification privacy, or viewing the watch for only a few seconds.
• Data may be live, cached, sensor-derived, privacy-sensitive, time-critical, battery-sensitive, app-provided, phone-dependent, or unavailable offline.
• Wearable glance sits near notification center, summary box, dashboard layout, progress bar, notification preferences, haptic feedback, and mobile handoff.

Selection Rules

• Choose wearable glance when a wearable surface should answer one immediate question in a few seconds.
• Use notification center when users need a durable, filterable history of many notifications and read states.
• Use summary box when the summary belongs inside a page or workflow rather than on a wrist surface.
• Use dashboard layout when users need multiple coordinated widgets, filters, drill paths, and comparison across metrics.
• Use progress bar when duration, percent, stages, cancellation, or retry is the main information need.
• Use notification preferences when users configure wearable routing, quiet hours, privacy, or channel rules.
• Keep visible content to one primary metric, label, or next step plus minimal context such as unit, source, or time.
• Show freshness or last-updated state whenever the value can be stale, cached, delayed, sensor-derived, or phone-dependent.
• Treat private messages, health values, payment details, location, and account status as sensitive on wrist surfaces.
• Provide handoff to phone or app for details, forms, destructive decisions, payments, account changes, and long reading.

Required States

• Configured and unconfigured complication, tile, or widget state.
• Normal glance state with one primary answer and short label.
• Ambient, dimmed, always-on, or wrist-down state.
• Fresh, stale, cached, unavailable, offline, and phone-disconnected states.
• Privacy-hidden or redacted state for sensitive content.
• Low battery or power-saving state with reduced updates.
• High-priority alert or due-now state with safe cue.
• Upcoming, active, completed, missed, and expired states for time-based events.
• Tap handoff state to app, phone, detail, route, or action review.
• One safe on-wrist action state such as mark done, pause, dismiss, or start.
• Action blocked or requires phone/authentication state.
• Wrong-size, unsupported slot, long text, and overflow handling state.
• Loading, refresh failed, permission-limited, and data-source unavailable state.
• Focus mode, quiet hours, and notification privacy state.
• Haptic or notification cue present but not required state.

Interaction Contract

• A wearable glance answers one primary question before any tap, scroll, or phone handoff.
• The glance never depends on tiny hidden controls, long text, dense charts, or multi-step input to be understood.
• Freshness, source, privacy, and unavailable states remain visible enough for a few-second check.
• On-wrist actions are safe, reversible, or clearly confirmed; complex and risky tasks hand off to a larger surface.
• Ambient and dimmed modes reduce detail without changing the meaning of the displayed state.
• Notification privacy, quiet hours, focus mode, and battery constraints can suppress or redact details without breaking the glance.

Implementation Checklist

• Define the one question the wearable surface answers, the update source, freshness rule, privacy level, tap destination, and allowed on-wrist actions.
• Design for the smallest supported slot first, including round screens, clipped corners, ambient mode, large text, and sunlight.
• Keep copy short, use stable units and icons, and test truncation for long names, times, values, and localized strings.
• Expose last updated, stale, cached, unavailable, phone disconnected, and permission-limited states when users could rely on the value.
• Respect notification privacy, focus mode, quiet hours, battery saver, reduced motion, haptics, and always-on display constraints.
• Provide phone/app handoff for details, authentication, forms, destructive actions, payments, and complex settings.
• Avoid frequent background updates unless freshness materially affects the user's decision.
• Test wrist raise, ambient mode, tiny slots, disconnected phone, stale data, privacy settings, one-handed use, screen reader, haptics off, and high-contrast mode.

Common Generated-UI Mistakes

• Shrinking a mobile dashboard or full card list into a watch tile.
• Showing stale data without a timestamp or unavailable state.
• Exposing private messages, health values, or payment details on the wrist.
• Using a wearable glance as a notification inbox.
• Putting complex forms, filters, or destructive controls on a tiny surface.
• Ignoring ambient mode, battery, and always-on display constraints.
• Using tiny unlabeled icons as the only explanation.

Critique Questions

• What single question can users answer after a brief wrist glance?
• What is hidden, reduced, or redacted in ambient mode, focus mode, and notification privacy?
• How fresh is the displayed value, and what does the user see when it is stale or unavailable?
• What happens when users tap the glance, and does it hand off safely for complex work?
• Is any private, health, financial, location, or account information visible to bystanders?
• Is this really wearable glance, or does notification center, summary box, dashboard layout, progress bar, or notification preferences own the main problem?