Atlas · DS189 · Interaction pattern: States

Offline-First UI

The experience continues without a network and reports sync and conflicts.

• Status in 2026: Active. In current use.
• Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
• The term: Known technical term or standard.

Definition

The experience continues without a network and reports sync and conflicts.

Traits

• sync status
• local queue

Typical settings: Point of sale, Industry, Field work.

When to use it, and when not

Consider it when the task and motivation match: workers on unstable networks. Typical settings: point of sale, industry, field work.

Be careful when the risk below would hurt the main task: silent conflicts and stale data.

UX risk and how to reduce it

Risk: Silent conflicts and stale data.

Mitigation and accessibility: Show origin, queue and resolution.

How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.

Evidence

Indirect: the sources support underlying principles, not a preference for this style.

The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.

• W3C Web Accessibility Initiative 2021 (Standard or guideline): Cognitive accessibility guidance.
• Hassenzahl 2004 (Supported): Pragmatic and hedonic qualities.

Heuristic scales

Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.

Visual complexity heuristic

2 / 5 (1 is few visual elements, 5 is many layered elements)

Expressiveness heuristic

2 / 5 (1 is restrained, neutral, 5 is highly expressive)

Information density heuristic

4 / 5 (1 is sparse, 5 is dense)

In our library

No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.

Prompt for your AI

Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.

Design this interface in the "Offline-First UI" direction (interaction pattern, states): The experience continues without a network and reports sync and conflicts.
Visual and interaction traits to use: sync status, local queue.
Main UX risk: Silent conflicts and stale data. Mitigate it: Show origin, queue and resolution.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.