Skip to main content

UX-MOBILE-AND-TASK-TIER-POLICY.md

This document defines device and workflow policy for Evalium frontend delivery.

Purpose:

  • support field-heavy iPad/mobile usage without degrading high-complexity authoring quality
  • define what is intentionally mobile-first vs desktop-optimized
  • prevent ambiguous UX behavior by using explicit task tiers and handoff rules

Capability Baseline (Validated 2026-02-25)​

Use this policy with explicit backend awareness:

  • backend APIs support mobile-compatible execution for runtime, assignments, and review primitives
  • complex authoring controls exist in backend but require careful frontend treatment (buckets, weighted structures, propagation)
  • offline sync is target-state and must be prepared for now in UX contracts

0. Device Doctrine (MUST)​

  1. Evalium is not desktop-only.
  2. Device strategy is task-based, not viewport-only.
  3. Simple and high-frequency tasks must be mobile-safe.
  4. High-complexity tasks may be desktop-optimized, but must provide explicit handoff with no data loss.

1. Task-Tier Model (MUST)​

Tier A: Quick Tasks (Mobile-First)​

Examples:

  • update question stem/metadata/tags
  • archive/restore low-risk items
  • create/basic edit of users and assignments
  • runtime launch/answer/submit
  • simple review and triage actions

Contract:

  • fully supported on mobile and iPad
  • touch-optimized controls and clear primary actions
  • minimal typing and strong defaults

Tier B: Guided Tasks (Responsive)​

Examples:

  • assignment issuance with policy options
  • taxonomy filtering and usage inspection
  • publish actions with impact confirmation

Contract:

  • usable on iPad and larger phones in responsive layouts
  • advanced options remain collapsed by default
  • clear status, validation, and retry behavior

Tier C: Full Tasks (Desktop-Optimized)​

Examples:

  • complex evaluation builder configuration
  • weighted bucket design and deterministic preview tuning
  • deep impact propagation choices across many assets

Contract:

  • full capability in desktop view
  • mobile can inspect context and perform safe sub-actions
  • when editing is restricted, provide explicit handoff actions

2. Handoff Contract for Complex Tasks (MUST)​

When a Tier C action is opened on a constrained device:

  • do not hard fail or silently hide state
  • show explicit reason in plain language
  • provide these actions:
    1. Continue on desktop
    2. Send me a link
    3. Save and exit

Rules:

  • preserve user intent/draft where possible
  • maintain audit context for high-stakes actions
  • avoid ambiguous wording like "unsupported"

Example copy:

  • "This action needs the full editor to avoid mistakes."

3. Mobile and Field Requirements (MUST)​

3.1 Runtime and Delivery​

  • sticky primary action for next/submit behavior
  • explicit sync states: pending, syncing, synced, failed
  • reconnect/offline banner with recoverable next action
  • large touch targets and glare-friendly visual choices

3.2 Operations in the Field​

  • monitor buckets and status chips remain readable at small widths
  • action menus are thumb-reachable and keyboard reachable on iPad keyboards
  • no dense table interaction that depends on hover-only affordances

3.3 authoring on Mobile​

  • permit safe metadata/content updates (Tier A)
  • gate complex structure editing with handoff contract
  • preserve work when transitioning between device classes

4. Accessibility and Mobile Interlock (MUST)​

Mobile policy does not weaken accessibility requirements:

  • keyboard access remains required (especially iPad keyboard usage)
  • VoiceOver/TalkBack paths must be valid for Tier A and Tier B flows
  • dynamic text and zoom must not break core actions

Refer to /docs/ux/UX-ACCESSIBILITY-STANDARDS-AND-GUARDRAILS.md for enforcement gates.

5. Performance and Resilience (MUST)​

  • reduce initial payload for mobile-critical routes
  • avoid blocking scripts before primary interaction
  • autosave and resume state for runtime and in-progress forms
  • design for intermittent connectivity and retry-safe writes

6. Initial Priority by Surface​

  1. Runtime candidate delivery (mobile-first)
  2. Assignments monitor and basic operations (mobile-safe)
  3. Users/subjects core actions (mobile-safe)
  4. authoring quick edits (mobile-safe) and full builder desktop-optimized
  5. Insights and governance dense analysis surfaces (desktop-first with responsive read access)

7. Source Docs​

This file complements:

  • /docs/ux/UX-GOVERNANCE.md
  • /docs/ux/UX-FRONTEND-CONVENTIONS.md
  • /docs/ux/UX-AUTHORING.md
  • /docs/ux/UX-OPERATIONS.md
  • /docs/ux/UX-RUNTIME-CANDIDATE-DELIVERY.md
  • /docs/ux/UX-CHECKLIST.md