HSLG Media

DeviceExperience.js

DeviceExperience.js

Source file: packages/app-ui/src/flows/DeviceExperience.js

Module: package-app-ui

Size: 99 lines

SHA-256: e330d07e59d407681c90d6ec5214e099d910e9157c0b7344e09c9d0e8d1f739a

Responsibility

Owns the shared customer screens, interactions, styles and approved brand assets.

Declared entry points

  • offline — source line 8.
  • blockedElements — source line 9.
  • host — source line 10.
  • announce — source line 11.
  • toast — source line 12.
  • dismiss — source line 16.
  • modal — source line 17.
  • show — source line 24.
  • already — source line 25.
  • overlay — source line 29.
  • noInternet — source line 32.
  • retry — source line 37.
  • button — source line 40.
  • state — source line 43.
  • service — source line 45.
  • btn — source line 50.
  • updateConnection — source line 52.
  • status — source line 54.
  • haptic — source line 59.
  • scanQr — source line 63.
  • result — source line 65.
  • route — source line 68.
  • scanNfc — source line 73.
  • result — source line 75.

Imports and dependencies

No direct import declarations detected in this file.

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

Offline UI orchestration

The module connects screen-level network state, API reachability, Retry and native capability feedback without importing platform plugins directly. It should keep a usable basket visible during an outage and avoid resubmitting an uncertain order automatically. Presenter and mobile runtimes provide different service adapters; tests must check that network reconnect does not become a fabricated payment or booking acceptance.

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.