Use wearable glance when a watch, band, or small wearable surface needs a few-second status tile, complication, or widget that answers one immediate question and hands off deeper work. Use notification center for durable event history, summary box for in-page summaries, dashboard layout for multi-metric workspaces, progress bar for measurable duration, and notification preferences for durable delivery controls.
Use wearable glance when a watch, band, or small wearable surface needs a few-second status tile, complication, or widget that answers one immediate question and hands off deeper work. Use notification center for durable event history, summary box for in-page summaries, dashboard layout for multi-metric workspaces, progress bar for measurable duration, and notification preferences for durable delivery controls.
Practice the judgment: Imagine this situation: A tiny watch complication tries to show a full dashboard with multiple charts and filter controls. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | Wearable glance | Notification center | Summary box | Dashboard layout | Progress bar | Notification preferences |
|---|---|---|---|---|---|---|
| UI or UX | UI + UX - Few-second wearable status surface with safe handoff | UI + UX - Durable user-opened notification history and action drawer | UI + UX - Highlighted region for key information from a longer page | UI + UX - Page-level arrangement of coordinated status, metric, and analysis widgets | UI + UX - Measurable system-operation progress indicator | UI + UX - User-controlled rules for notification type, channel, frequency, timing, privacy, and exceptions |
| UI guidance | Render a wearable glance as one compact answer with a clear subject, current value, priority, freshness, privacy state, and tap destination that works in a tiny complication, Wear OS tile, widget, or wearable card. | Provide a persistent notification entry point, usually a bell or inbox control, with a count that represents new unseen notifications rather than every unread item forever. | Render a summary box as a labelled region with a specific heading, short body, scannable key points or next steps, and only links that directly support the summarized page task. | Arrange dashboard widgets into a purposeful page hierarchy with a named dashboard, scope, freshness, global filters, primary KPIs, secondary analysis, exceptions, and supporting tables or links placed according to monitoring priority. | Show a labeled bar with a track, filled value, and nearby helper text that reports the measurable unit such as percent, bytes, rows, files, records, or stages. | Render notification preferences as a structured matrix or grouped settings surface that shows notification type, source, delivery channel, device, frequency, quiet-time rule, preview privacy, override, and current saved state. |
| UX guidance | Keep wearable interactions short: one glanceable answer, one safe action when necessary, and a clear handoff to phone or app for complex review, input, destructive choices, payments, or privacy-sensitive detail. | Use a notification center when users receive enough asynchronous system or collaboration updates that they need a durable place to review, triage, and act later. | Use summary box when users need the essential facts, eligibility notes, deadlines, documents, or next steps from a longer page before reading every detail. | Use dashboard layout when users need one page to monitor several related signals, compare current state against targets, spot exceptions, and decide which detailed view or workflow to open next. | Use a progress bar when the system can honestly report movement toward a known finish and users need to decide whether to wait, cancel, retry, continue elsewhere, or return later. | Make consequences explicit: what stops, what still arrives, which devices and channels are affected, when changes apply, and which admin, OS, or workspace policies override the user's choice. |
| Good UI | A medication complication shows Next dose 8:30, due in 12 min, taken state, and opens the medication app for details. | A bell opens a drawer with Unread and All filters, showing comment mentions, approval requests, export results, and background-job failures in newest-first order. | A benefits guide has a summary box headed Before you apply with deadline, required documents, and Start application link above the detailed eligibility rules. | An operations dashboard opens with date range, region filter, last updated time, four KPI cards, an exception panel, a trend chart, and a priority table in a stable grid. | A document upload card says Uploading evidence.zip, shows 64%, 32 of 50 MB, a Cancel action, and keeps the rest of the form usable. | A notification preferences page groups Mentions, Assigned work, Followed threads, Security, Digest, and Marketing, with columns for In-app, Email, Push, Banner, and Digest frequency. |
| Bad UI | A watch tile compresses five dashboard charts, filters, and drill links into tiny unreadable panels. | Users ignore the center because duplicate low-value messages inflate the badge. | A pale box repeats the entire page introduction, every related link, and several unrelated policy notes. | A responsive dashboard collapses filters and alerts below the fold while leaving decorative charts above the operational exceptions. | A progress bar reads 100% complete while virus scanning and server acceptance are still pending. | A preference changes email only but the label implies all notifications stopped. |
| Good UX | A user raises their wrist, sees that boarding starts in 9 minutes at Gate B12, and taps to open the boarding pass only when needed. | Opening the notification drawer clears the new-notification badge while unread items remain available for later triage. | A user scans the box, learns they need photo ID and proof of address, then continues into the detailed instructions with the same terms repeated in context. | A manager changes Region to West, sees every tile show the same filtered scope and updated timestamp, then opens the exception table from the SLA breach card. | A user uploads evidence.zip, sees progress move from 12% to 64%, cancels before commit, retries after a network error, and gets a completed receipt only after server processing succeeds. | A user keeps mentions and assigned-work banners on, moves repository watch updates to daily digest, mutes marketing email, and sees a preview of what will still notify them during quiet hours. |
| Bad UX | A user tries to act from a tiny complication and accidentally dismisses an important alert. | Users mark all notifications read and lose the only record of an export job they still need to download. | Users treat static summary guidance as a current alert because the styling mimics alerts. | A dashboard hides stale or partially refreshed widgets and users compare incompatible numbers. | Users leave after 100% transfer even though server processing later rejects the file. | A user disables email for a noisy project and still receives duplicate push and desktop banners because those channels live in separate hidden settings. |
| Best fit | A wearable surface can answer a status, next-step, or current-metric question in seconds. | Users receive multiple asynchronous updates across objects, jobs, collaborators, approvals, or reminders. | A longer page has a small set of key facts or next steps that users need early. | Users need to monitor several related metrics, exceptions, and analyses together. | A system operation has a measurable total or bounded progress value. | Users receive enough notifications that they need control over type, channel, device, frequency, timing, or source. |
| Avoid when | The task requires long reading, comparison, filtering, editing, authentication, payment, or destructive review. | The product has only occasional current-action feedback that a toast or inline status can handle. | The highlighted content is an urgent status, outage, validation result, or severe consequence. | Only one chart, table, status message, or record list is needed. | The wait is short and only needs scoped activity feedback. | The product has only a few low-volume notifications that can be handled by defaults and inline controls. |
| Required state | Configured and unconfigured complication, tile, or widget state. | Closed entry-point state with zero, new-unseen, and unread-but-seen counts. | Default summary box with heading, concise body, key points or next steps, and optional task-specific link. | Default dashboard with name, purpose, global scope, active filters, freshness, KPI tier, sections, and widget grid. | Idle state before the operation starts. | Default notification preferences state. |
| Accessibility burden | Support large text, high contrast, reduced motion, screen reader summaries, and short localized strings. | Announce new notification arrival with status semantics when appropriate, but avoid interrupting users repeatedly for low-priority center items. | Expose the box as a labelled region or group with a heading that fits the page heading hierarchy. | Give the dashboard a heading, purpose, filter summary, refresh status, and section headings that screen-reader users can navigate. | Provide an accessible name that identifies the operation and affected object. | Group preferences with headings and fieldsets for event type, delivery channel, device, and frequency. |
| Common misuse | Shrinking a mobile dashboard or full card list into a watch tile. | Treating the badge count, unread count, and total notification count as one number. | Repeating the whole page in a highlighted box. | Filling a page with charts before defining dashboard purpose, audience, hierarchy, and decisions. | Fabricating progress values just to make users feel movement. | Offering one master notification switch for a complex collaboration product. |