A peer-to-peer scheduling app for FedEx pilots

FedEx pilots lack an internal tool to coordinate with one another.

Pilots can't easily browse schedules, compare trip pairings, or communicate during rest periods. The company app handles logistics, not connections. So pilots rely on workarounds: group texts, scattered spreadsheets, too many apps, and word-of-mouth.

I'm building the tool that should already exist.

Before designing anything, I mapped how existing crew tools handle communication and scheduling. Pilots themselves have created these tools as third-party apps.

Most of the company's internal tools are built for dispatchers or ops managers, not pilots. The ones that do exist for crew members lack features pilots actually need: pairing comparisons, layover info, bidding, rest period awareness, and weather coordination.

I partnered with subject matter experts (actual FedEx pilots) to stress-test assumptions and surface real pain points. What came out of those sessions shaped the entire product direction: pilots need to find each other fast, share trip context without friction, and access hotel and ground transport info in one place.

- Pilot 2, FedEx Express​​​​​​​

Before jumping into Figma, I sketched out how the core flows might work. Pairings, bidding, and policies are the primary focus. Rough enough to stay flexible, detailed enough to pressure-test the logic before committing to higher fidelity.

Design

This isn't a concept. I'm actively developing Aviator Lounge as a React Native app with FedEx API integration. It's designed to scale beyond FedEx to other carriers eventually.

UX strategy 

Research

Brand identity

Information architecture

Visual design, and

Prototype development

React Native App using AI tools

All by myself. Sola. 🥲

Design: Figma, FigJam

Development: React Native, Expo, TypeScript, Bolt.new

Integration: FedEx API, Okta authentication