Screen Mapping Status

Flight Card family — one domain control, five Figma masters (D15)

The 2026-06-17 file restructures all flight card masters under a single Flight Card domain control. flight card-og (5452:679, 353×111) is confirmed as the renamed flight segment card — identical dimensions and styling, adds a swipe variant. The full variant set:

Notifications screen — two-tab segmented layout

The Notifications screen uses a two-tab segmented control (tab group) as its primary navigation, splitting the feed into:

• Flight Finder tab — flight-status notifications. Driven by JSFF saved-flight subscriptions (GetAllSubscriptionsForUserAsync / ToggleSubscriptionAsync). Uses notification card flight status.
• Comms tab — ALPA Internal Comms notifications. Driven by GetNotificationListAsync → NotificationCenterMessage. Uses card-notification.

The card-notification component serves both tabs — the Comms variant is a content/style difference, not a separate component. The overlay-notification filters frame (modal sheet) applies filter options to whichever tab is active. Filter state is tab-scoped.

Overlay pattern — modal sheets, not routes

Three frames are explicitly annotated as overlays in the 2026-06-17 file. Designer annotation verbatim:

Frames prefixed overlay- are modal sheets layered over a base screen (filter / sort / notification-filter), shown on invocation and dismissed back to the screen beneath. Build as overlays, not separate routes. Applies to all overlay- frames (flight finder filter, notification filters, KCM filter).

Tablet screens — deferred-responsive tier (D12)

Two tablet-specific templates in the 2026-06-17 file. Designer annotation verbatim: "Tablet — adapted, not stretched. A considered tablet treatment, not the phone scaled up: dedicated type mode, purpose-built navs, and increased margins/padding. Tablet components live in the components-tablet section."

Home — data-gap deep dive ANALYZED

Screen 4099:5229 (393×852). The scrollable main-feed slot stacks, in order (from the Figma design context):

1. Welcome card — "Welcome Captain Johnson" / "View Contract" + chevron → Pilot Card
2. Carousel "UAL MEC · View My MEC" — horizontally-scrolling card-lg content cards
3. Emergency Hotline — Primary button + phone icon
4. Small-card row — card-sm tiles (DART, …)
5. Carousel "View All" — card-lg cards
6. Small cards — Flight Pay Loss · My Payments · Infor Expense Management
7. Content card "Hotel Request" — full-width card-lg
8. Small cards — Meeting Request · MPS
9. Carousel "Feed · View All" — card-lg (Press Release)

Chrome (not library): topNav (avatar · favorites · notifications · search · hamburger) · status bar · navBar-bottom (Home · Jumpseat · KCM · FTDT · My MEC). Every card carries a favorite/i-heart in Figma — rendered per D31 (2026-06-26).

Flight Finder IDENTIFIED

Results mock 4713:25168 repeats a flight card (353×111): origin/destination + times (DEN 12:00 → MIA 16:19), per-leg carriers (DL 302 / AA 1753 / AA 1186), layover chips, date, total duration / Multileg. Recent/Saved Searches use flight card-recent searches and flight card-saved searches; Saved Flights use flight card-saved flight.

MEC — data-gap deep dive ANALYZED

Reuses the Home controls and adds Secondary button, card-btn (3-up icon tiles) and confirms card-md (text content card) data. Full report: mec-screen-data-gap.html.

New data gaps surfaced: (1) Favorite / bookmark — heart on card-btn, card-md and the media card-lg; no API today (heart shown per D31, reverses D7 — MEC shows it across three controls). (2) card-md description — re-confirms the Description gap on the content item. Note: the card-md "new" count badge is client-side (local last-seen diff'd against the API), not a backend gap — API just needs stable item IDs.

KCM — data-gap deep dive ANALYZED

5 screens (home · Airlines · Airports/"Airline Policies" · Policies search · Filter overlay). Full report: kcm-screen-data-gap.html.

Data-complete — no backend gaps. Airlines map 1:1 to KCMAirlineItem { airlineName, pilots, attendants } (getkcmairlines); Airports to KCMAirportItem { airportName, airportCode, checkinNotes, mapUrl } (getkcmairports). Filter/search/sort are client-side. Confirm (×3): Requirements/Usage Procedures content source · Airports "NOTICE" source · eligibility-flag semantics. Presentation backlog: Master Form Field (+ check / radio / tab group / Underline Button) scaffolds.

Jumpseat Flight Finder — data-gap deep dive ANALYZED

9 nodes (search · results · recent · saved searches · saved flights · airline policies). Full report: jsff-screen-data-gap.html.

Data-complete — no backend gaps. Search → FlightSearchAsync → FlightSearchResponse (Flight/Leg); airports → GetFlightSearchAirportsAsync (AirportLocation); detail → FindFlightInfoAsync; policies → GetAirlineJumpseatPoliciesAsync (PolicyViewModel) / GetJumpseatAirlinesAsync. The flight card (new marquee scaffold, 3 variants) binds Flight/Leg (codes · times · carriers · layovers · duration · KCM-per-leg). Confirm: saved/recent persistence (local vs sync) · flight-status notification subscribe API (saved-flight bell) · advanced-search field coverage. Client-side: saved/recent storage, sort/filter.

FTDT — data-gap deep dive ANALYZED

8 nodes (dashboard · op-type select · duty periods · archived · add unaugmented/segment/rest/note). Full report: ftdt-screen-data-gap.html.

Data & computation complete — no backend gaps. Mature local-first feature: DutyPeriod CRUD+sync (Create/Update/SoftDeleteDutyPeriodAsync, GetDutyPeriodsUpdatedAtAsync → DutyPeriodExpanded, FTDTDataBase/FTDTDataSyncHelper); op-type via DPOperationType (US + Canada). Max Duty Period / Ends / cumulative Flight & Duty-hour bars are all computed client-side (FAR-117 / Canadian rest calculators, CalculatorRest_CAN). Regulatory limit rules are all client-side (resolved — no backend rule config). Confirm: sub-entity collections (segments/rest/notes) · calc-input persistence. Presentation backlog: Duty Period Card · progress bar & labels · Master Form Field · toggle-settings.

FTDT component structure — 2026-06-22 exploration

Live Figma exploration of FTDT screens (via get_metadata + get_screenshot on nodes 4535:14038, 4544:5877, 4617:13876, 4325:6399, 4555:6566) confirmed the following component structure:

Member Resources — data-gap deep dive ANALYZED

2 nodes (resource nav · Submit a Pilot Data Request form). Full report: membership-screen-data-gap.html.

Resource list = MenuItem nav (In Case of Emergency · International Directory · Membership Card · Orange Card → existing pages). The PDR form pre-fills from Member (Name/Position/ALPA #). Out of mobile scope: the PDR submission is scoped to the web application and was accidentally surfaced in the mobile mock — no mobile endpoint; remove/hide on mobile. Not a mobile backend gap. Confirm: Employee-Number prefill source (not on Member).

Notifications — data-gap deep dive ANALYZED

Notifications list + settings (distinct from Comms). Full report: notifications-screen-data-gap.html.

Data-complete. COMMS list → GetNotificationListAsync → NotificationCenterMessage { Title, Message, SendDateTime, HasNotBeenRead, ContentType, DocType, FileID, Destination, RequiresLogin }; settings → GetAllSubscriptionsForUserAsync → MobileAudienceSubscription + ToggleSubscriptionAsync. Confirm: Flight-Finder-tab flight-status feed source (↔ JSFF saved-flight subscription) · mark-as-read mechanism. 2026-06-17 update: screen is segmented into two tabs (Flight Finder | Comms) driven by a tab group; overlay-notification filters is a modal sheet (not a route); card-notification serves both tabs. See 2026-06-17 Revision section above. Presentation: Notification Card (+ flight-status variant), segmented tab group, toggle-settings, overlay modal.

Comms — data-gap deep dive ANALYZED

Advocacy + Internal Comms (ALP Mag) — document-list screens, distinct from Notifications. Full report: comms-screen-data-gap.html.

Data-complete. Advocacy → GetPACMemberInfoAsync → PACMember { ContributionYTD, ClubStatus, AllPACContributions, pacDonationPageURL, pacMembershipInfoURL } + GetCallToActionLinksAsync → CallToAction; Internal Comms → GetDocumentListAsync → DocumentItem. External: "Submit Meeting Report" links to an online web form (no in-app submission). Confirm: CallToAction completion status · comms article date/summary fields.

Search — data-gap deep dive ANALYZED

Global search (typeahead). Full report: search-screen-data-gap.html.

Client-side — no backend gap. No global-search endpoint/VM in the codebase; search runs over already-loaded data (DocumentItem list · MenuItem · KCM airlines · content), results reuse existing per-entity navigation. Confirm: the searched corpus, and whether a server search is needed if the corpus outgrows what's on device.

FAQ / Did You Know — data-gap deep dive ANALYZED ABANDONED

"Did You Know?" list (listy). Full report: faq-screen-data-gap.html.

2026-06-24: This feature has been abandoned. The DYK/FAQ requirement has been dropped; no endpoint will be built and no mobile implementation is planned. The DidYouKnowListFactory scaffold spec and ListViewModel domain control remain in the library as a generic list, but the DYK-specific domain control is removed from scope.

Favorites — data-gap deep dive ANALYZED

2 nodes (rich "Favorites" view · condensed list). Full report: favorites-screen-data-gap.html.

Pending API client delivery (2026-06-24). The screens render the member's favorited items by their native control — card-lg (document) · card-sm (nav tile) · card-btn (button) — plus a condensed » list. Backend team is building the Favorites capability; do not pre-design the mobile contract. Wire FavoritesService to the shape and calls delivered in the backend API client. No favorites endpoint / service / model exists today.