Mobile App Requirements

ALPA Mobile App Strategy & Redesign — Screen & Component Requirements
Last Updated: 2026-07-13 • Source: interactivestrategies.teamwork.com (Space 4173) • 33 pages
Regenerate: TEAMWORK_API_KEY="..." python3 docs/requirements/tw-ingest.py mobile
← Back to Component Index

Screen and component requirements sourced from the ALPA Mobile App Strategy & Redesign Teamwork Space. Each entry shows the page Overview plus its UI/UX, Component Fields and Data Source rows, and a link to the Figma design where present. Regenerate from source using the command above.

Top Utility Bar

Updated 2026-06-18

The Top Utility Bar is a global navigation element that persists across all screens in the app. It contains 5 icons; each icon triggers a distinct screen or overlay.

Figma design ↗

Profile

Updated 2026-06-15

The Profile page is accessible via the person icon in the Top Utility Bar. It displays the authenticated pilot's personal information and provides access to account settings, notification preferences, and log out. The page is divided into two sections: the profile card and Settings.

UI/UX
  • Profile Card displays Pilot name,
  • Member Number
  • PAC Contributions
  • Pilot Group links (MEC, LEC): navigate to respective group pages
  • View Contract link: opens contract file
  • An "Edit Profile" secondary button appears at the bottom of the card, by clicking it will navigate the user to profile editing flow.
  • Settings Section: Below the profile card. Contains a "Notification Settings" row (tap navigates to sub-page) and a "Log Out" primary button.Notification Settings: navigates to Notification Settings sub-page
  • Log Out: ends session and returns user to login screen.
Component Fields
Needs review — non-standard or conditional
  • PAC Contributions: Display only. TBD — Confirm data source.
  • Pilot Name: Display only. Auto-populated from authenticated user profile.
  • Member Number: Display only. Auto-populated from authenticated user profile.
  • Pilot Group (MEC / LEC): Display only. Links navigate to the respective MEC and LEC pages.
  • Contract Link: Display only. Navigates to the pilot's contract file.
Data Source
Needs review — non-standard or conditional
  • TBD — Which system provides pilot name, member number, PAC contributions, and pilot group assignment?

Figma design ↗

Notification Settings

Updated 2026-06-15

No requirements documented.

Favorites

Updated 2026-06-15

Notifications

Updated 2026-06-15

Search

Updated 2026-06-15

Hamburger Menu(☰)

Updated 2026-06-15

Bottom Tab Bar

Updated 2026-06-18

The Bottom Tab Bar is the primary navigation element of the app, persistent across all primary screens. It contains 5 tabs; the active tab is visually highlighted to reflect the user's current section.

Figma design ↗

Home Page

Updated 2026-06-15

No requirements documented.

Jumpseat

Updated 2026-06-18

This section contains 4 tabs, Etiquette & Courtesy and Mission are static content pages displaying text and optional video — no user interaction beyond scrolling.

Flight Finder

Updated 2026-06-15

This section contains a search form and 3 sub-views accessible via the bottom sub-navigation: Recent Searches, Saved Searches, and Saved Flights.

Figma design ↗

Recent Searches

Updated 2026-06-15

No requirements documented.

Saved Searches

Updated 2026-06-15

No requirements documented.

Saved Flights

Updated 2026-06-15

No requirements documented.

Airline Policies

Updated 2026-06-15

No requirements documented.

Static Content Pages

Updated 2026-06-15

No requirements documented.

KCM - Know Crewmember

Updated 2026-06-15

KCM contains 4 items. Airlines and Airports are interactive list pages with search functionality. Requirements links to an external URL and opens in the browser. Usage Procedures is a static document page.

Airlines

Updated 2026-06-15

Airports

Updated 2026-06-15

Static Content Pages

Updated 2026-06-15

No requirements documented.

FTDT - Flight Time Duty time

Updated 2026-06-15

No requirements documented.

Cumulative Limitations

Updated 2026-06-15

No requirements documented.

Duty Periods

Updated 2026-06-15

No requirements documented.

Archived Logs

Updated 2026-06-15

My MEC

Updated 2026-06-18

My MEC is a personalized dashboard that surfaces content and tools specific to the pilot's assigned MEC. The page is scrollable and organized into distinct sections, each presenting a different type of content or action.The page includes the following elements:

Pilot Card

Updated 2026-07-08

The Pilot Card is a personalized banner that greets the pilot by name and provides a direct link to their contract file.

UI/UX
  • It appears in two visual variants depending on the screen context.Light version on home tab: Light blue background, right-pointing chevron arrow
  • Dark version on My MEC tab: Dark navy background, no chevron
  • The card contains two elements:Pilot Name: Displays a personalized greeting using the pilot's name (e.g., "Welcome Captain Johnson").
  • Contract Link: A link that navigates the pilot to their contract file.
Component Fields
  • Pilot Name: Display only. Auto-populated from the authenticated user's profile.
  • Contract Link: Display only. Dynamically generated based on the pilot's assigned contract; not editable.
Data Source
  • Pilot name and contract data are retrieved via API, using the same integration approach as the ALPA website profile. Specific API details to be confirmed and provided by the ALPA dev team.

Call to Action

Updated 2026-07-08

The Call to Action (CTA) Button is a full-width button used to prompt the pilot to take a specific action. It appears in three variants, each with a distinct visual style and behavior to communicate priority and context.

UI/UX
  • Full-width button spanning the content area.
  • Label is centered, all caps.
  • Three variants: Primary: solid filled background.
  • Secondary: outlined style with no fill.
  • Emergency Hotline: solid filled background, with right-pointing chevron arrow, appears on Home tab only
  • Primary and Secondary buttons appear stacked vertically when both are present on the same screen.
  • Interaction & Behavior:Primary / Secondary → triggers navigation or action defined by the link target.
  • Emergency Hotline → triggers native iOS/Android call modal (tap-to-call link); no in-app navigation.
Component Fields
  • Button Label: Configured. Fixed text per screen instance (e.g., "FILE A PDR"); set by development.
  • Button Variant: Configured. Visual style (Primary / Secondary); set by development.
  • Link: Configured. Navigation destination or action triggered on tap; set by development.
Data Source
  • NA

PDR Form

Updated 2026-06-15

The PDR (Pilot Data Request) form allows pilots to submit a request to authorize the UAL MEC to disclose their pilot data. The form requires explicit consent before submission. Accessible via the "File a PDR" button on the My MEC homepage or through the hamburger menu "PDR" button.

UI/UX
  • The form is accessed as a full-screen page with a back arrow in the top navigation bar
  • Authorization consent is displayed as a toggle (on/off). Default state is ON
  • Interaction & BehaviorToggle "OFF": Give no consent
  • Tap "SUBMIT PDR": Submits form
  • Tap "CANCEL": Returns user to previous screen without saving
Component Fields
  • Authorization Consent: Toggle (Yes/No)
  • Must be ON to submit
  • Name: Required, Text Input, Auto-filled from user profile
  • Position: Required, Text Input, Auto-filled from user profile
  • ALPA Number: Required, Text Input, Auto-filled from user profile
  • Employee Number: Required, Text Input, Auto-filled from user profile
  • Domicile: Required, Text Input, Auto-filled from user profile
  • Confirm which is the complete version (App/Design)
Data Source
  • Name, Position, ALPA Number, and Employee Number are pre-populated from the authenticated user's profile

Figma design ↗

3-Up Icon

Updated 2026-07-08

The 3-Up Icon is a row of three icon shortcut tiles displayed on the My MEC homepage. Each tile links to a dedicated internal page within the app.

UI/UX
  • Three equal-width tiles arranged in a single horizontal row.
  • Each tile contains a centered icon and a text label below it, tile is fully tappable
  • A heart/favorite icon appears in the top-right corner of each tile.Favorited: heart icon filled.
  • Unfavorited: heart icon outlined.
  • Tap navigates to the corresponding internal page: Committees → searchable list of MEC committees grouped by name.
  • Reps → contact cards for MEC representatives (role, name, phone, email) with tap-to-call and tap-to-email actions.
  • Hotels → alphabetically grouped hotel listings with search.
  • Note: destination pages are existing app UI.
Component Fields
  • Icon: Configured. Fixed icon per tile; set by development.
  • Label: Configured. Fixed text label per tile (e.g., Committees, Reps, Hotels); set by development.
  • Link Target: Configured. Internal destination page; set by development.
  • Favorite Toggle: User-controlled. Heart icon state stored per user account.
Data Source
  • NA

Link List

Updated 2026-07-08

The Link List is a vertical stack of navigation rows displayed on the My MEC homepage. Each row consists of a thumbnail image, a text label, and a favorite toggle. Tapping a row opens the destination in a webview within the app.

UI/UX
  • Vertical list of full-width tappable rows, row fully tappable.
  • Each row contains: Thumbnail image on the left
  • Text label to the right
  • Heart/favorite icon at the far rightFavorited: heart icon filled.
  • Unfavorited: heart icon outlined.
  • Tap opens destination in a webview within the app. Current items and their destinations: Quick Reference Guide → ALPA member login page.
  • UP-PAC Sign Up → UP-PAC form, pre-populated with user profile data.
  • Help Hub → United Airlines login page.
Component Fields
  • Thumbnail Image: Configured. Fixed image per list item; set by development.
  • Label: Configured. Fixed text label per item (e.g., Quick Reference Guide).
  • Link Target: Configured. Destination URL or form; set by development.
  • Favorite Toggle: User-controlled. Heart icon state stored per user account.
Data Source
  • NA

Image Slider

Updated 2026-07-08

The Image Slider is a horizontally scrollable card carousel driven by a CMS taxonomy selection.

UI/UX
  • Section header on the left (e.g., "Latest Media", "Events").
  • Text link on the upper right (e.g., "View All" / "View Media Hub")By clicking it navigates to the full repository for the selected taxonomy/content type
  • Horizontally scrollable row of cards. Cards partially reveal the next item to indicate scrollability.
  • Each card contains: Image
  • Eyebrow
  • Heart/favorite iconFavorited: heart icon filled.
  • Unfavorited: heart icon outlined.
  • Title text
  • Tap a card opens the linked file
  • Max cards: 8
Component Fields
  • Section Title: CMS-managed. Displayed as section header (e.g., "Latest Media")
  • Taxonomy Selection: CMS-managed. CMS user selects the taxonomy grouping that drives card content.
  • Card Item FieldsImage: CMS-fed. Variable crop and aspect ratio.
  • Eyebrow: CMS-fed. Taxonomy label displayed above the card title.
  • Title: CMS-fed. Variable length; maximum 2 lines. Text exceeding 2 lines is truncated with an ellipsis (…).
  • Link: CMS-fed. Each card links directly to its page.
  • Favorite Toggle: User-controlled. Heart icon state stored per user account.
Data Source
  • CMS-managed.
  • Content is dynamically pulled based on the configured taxonomy grouping, ordered by most recent.

Text Sliders

Updated 2026-07-08

The Text Slider is a horizontally scrollable card carousel that displays content without images. It operates in two modes: taxonomy-driven (same logic as Image Slider) and manually populated.

UI/UX
  • Section header on the left.
  • Text link on the upper right (e.g., "View All")By clicking it navigates to the full repository for the selected taxonomy
  • Horizontally scrollable row of cards. Cards partially reveal the next item to indicate scrollability.
  • Each card contains: Optional Eyebrow
  • Heart/favorite iconFavorited: heart icon filled.
  • Unfavorited: heart icon outlined.
  • Title text
  • Body Text
  • Tap a card opens the linked page
  • Max cards: 8
Component Fields
  • Section Title: CMS-managed. Displayed as section header (e.g., "Latest Documents")
  • Eyebrow: Optional. Behavior depends on variant Taxonomy-driven: Eyebrow is auto-populated from the content's taxonomy label. Not editable by content manager.
  • Manually populated: Content manager can toggle eyebrow on or off. If enabled, eyebrow text is manually entered by content manager.
  • Card Item Fields:Title: CMS-fed. Variable length; maximum 2 lines. Text exceeding 2 lines is truncated with an ellipsis (…).
  • Body Text: CMS-managed. Supporting description text. maximum 3 lines. Text exceeding 3 lines is truncated with an ellipsis (…).
  • Link: CMS-fed. Each card links directly to its page.
  • Favorite Toggle: User-controlled. Heart icon state stored per user account.
Data Source
  • Taxonomy-driven: Dynamically pulled from CMS based on configured taxonomy, ordered by most recent.
  • Manually populated: Configured directly by content manager in CMS.