← Component Specifications

Requirements, Design Gaps & Open Questions

ALPA Mobile UI Refresh — Reference Index
Updated: 2026-08-12 13:59 ET · Split from the Component Specifications index · Work Items: AB#1821 · AB#2429

Requirements & Content

UX/UI Requirements (Website)

Component and global UX/UI behavior requirements for the ALPA website redesign, sourced from Teamwork Spaces (Space 2305). Each entry surfaces the behavior requirements row — content fields and CMS config are omitted. Covers Global Requirements and all reusable components.

Refresh: TEAMWORK_API_KEY="..." python3 docs/requirements/tw-ingest.py website

Mobile App Requirements

Screen and component requirements for the ALPA mobile app, sourced from the ALPA Mobile App Strategy & Redesign Teamwork Space (Space 4173). Each entry surfaces the page Overview plus its UI/UX, Component Fields, and Data Source rows, with a Figma design link where present. Covers App Navigation — Top Utility Bar, Bottom Tab Bar, and all screens/components.

Refresh: TEAMWORK_API_KEY="..." python3 docs/requirements/tw-ingest.py mobile

Component Design Questions

Living tracker of open design-team-facing questions surfaced while mapping Figma to the component library — items needing a design decision before a spec is final (e.g. font overrides, card accent-color variants, DQ-14–DQ-16 pending responses).

Design Gaps — Review Hub

The single entry point for every screen where the Blazor Hybrid implementation ships without a Figma design source or has diverged from it — organized by app area, each gap linking a side-by-side XAML-vs-Blazor comparison page for design-team review. Absorbs what this index used to list piecemeal: the comms notification detail and Jumpseat gap pages, the XAML → Blazor coverage map, the design-source route inventory, the empty-state inventory, the flight-notification grouping proposals, and the My Pilot Group MEC coverage assessment, plus new comparison pages for Member Resources, MEC pilot-group lists, FTDT duty-period forms, KCM airport detail, and the document viewer.

D65 — Content-Only Pinch Zoom

Pinching zoomed the whole window, chrome included. Native WKWebView pinch zooms the visual viewport above the page, so no CSS can exempt the nav — chrome-locked zoom means suppressing the gesture and applying it ourselves. Records why interception is scoped per-region rather than switched off globally (a global switch would strip zoom from the 13 pages outside AlpaScreen and regress AB#2391), the measurements that ruled out the existing text scale, and those 13 pages listed for later review.

Communications Content

App copy, messaging, and content definitions maintained by the Communications department. Source: SharePoint (DEPT_DSS).

Refresh: download → docs/requirements/comms-content.xlsxpython3 docs/requirements/comms-ingest.py