Prototyping for the flight deck

Jenny Xie, an editor at Figma, documents how Lufthansa Systems adopted Figma Make to build more dynamic prototypes for user testing of cockpit software. The work sits within Figma's broader Maker Stories series.

Lufthansa Systems' Lido Pilot Apps run on iPads mounted on both sides of the cockpit, carrying pilots and copilots from takeoff to landing at more than 250 airports, with over 100,000 pilots relying on them daily. The map is the centerpiece: it layers airways, waypoints, alternate airports for emergencies and turbulence data for situational awareness, plus an airport moving map (AMM) that guides aircraft from the parking stand to the runway.

Kristjan Gomboc, Head of Design, and Lead Product Designer Pankaj (Pank) Juvekar describe how the team moved from static mockups to dynamic, data-driven prototypes during an internal hackathon called Innovation Week.

Designing for a cockpit full of experts

Access to users is unusually direct at Lufthansa Systems: more than 100 pilot sessions this year, mostly remote, plus in-person workshops, and every product designer joins at least one observation flight annually to run a study from the cockpit. Pilots are enthusiastic about explaining their work, Gomboc says, but the barrier is expertise. "You have to be an expert to talk to experts," he notes; novice questions lose the room, while on-point ones produce useful feedback. In-house former pilots and air traffic controllers supplement that learning, and Juvekar describes the curve as steep even after nearly seven years.

Serving hundreds of airlines sharpens the design problem. Rather than build for a single requesting customer, the team shows an idea to about 10 others to avoid bias, since airlines differ by region, short- versus long-haul, and fleet. Each request is weighed against industry-wide pain, whether the team can solve it satisfactorily, and the minimum viable step within technical and regulatory constraints. Some ideas are paused when the achievable solution isn't good enough yet.

Why a dynamic map resisted prototyping

The app's maps are dynamic, but the prototypes historically were not. The team moved from Sketch to XD to Framer in search of a live map; Framer proved difficult for everyone to use, so work reverted to static designs and manual prototyping. A screenshot can prompt pilot feedback, Juvekar acknowledges, but it doesn't feel like the real thing.

During Innovation Week, he tested whether Make could pull in a dynamic map. The starting point was an in-house web version of the map built on Mapbox, sharing the same data as the iPad app. Connecting it through the web version's API, and later an open link, both worked well with Make, yielding a map close in look and behavior to the production app. Top bar, bottom bar and layer icons followed, copied and pasted straight from Figma files into Figma Make — a step Juvekar credits with removing much of the friction.

Traffic, weight classes and zoom thresholds

To give pilots greater situational awareness — and ultimately support safety — the team prototyped traffic display. Juvekar connected Make to the OpenSky Network and instructed it to show sample aircraft markers only within 500 nautical miles of the simulated position. Tapping a marker surfaces what pilots asked for: call sign, aircraft type, speed, altitude relative to the user's, departure and destination. Pilots understood it immediately.

Their next request was size-differentiated markers, as in consumer flight-tracking apps. Juvekar had Make apply FAA aircraft weight classes to the icons — super, heavy, large, small — and reports that a few keywords sufficed for Make to infer the intent without further prompting; an Embraer 195 renders smaller than a Boeing 737. Iteration became faster.

The gain was testing anything interaction-dependent. The team could zoom in and out to find the threshold at which traffic should appear without cluttering the map, and pilots could describe expected zoom-scale behavior. With cartographer teammate Agata, Juvekar experimented on the AMM, where aircraft on the runway change color at the moment of takeoff — a regulatory requirement separating ground traffic from air traffic that has to be seen in motion. Flight trajectories appeared as an unplanned byproduct and generated a fresh round of feedback. All of this happened before any implementation: the apps are built in SwiftUI, where such experimentation isn't feasible on every iteration, so upstream exploration gives developers a more considered handoff.

What surprised the team — and where adoption stands

Beyond connecting to open-source and third-party platforms via API credentials, including internal developer-focused ones, Juvekar highlights Make's ability to recommend rather than merely execute: it suggests multiple approaches, often ranked by complexity as easy, medium or hard, which he frames as a collaborative thinking partner rather than just a prototyping tool.

The team built templates pairing the app frame with the dynamic map so other designers can start experimenting, and several design teams now use Make. Because maps are central across web, iPad and desktop apps, the approach resonates widely. Gomboc reports steady growth among Lido designers, to the point that some projects are Make-only; the biggest benefit lands on complex interfaces — map interactions, or data-heavy UI expressing particular business logic or app behavior — that would otherwise be hard to prototype and test. Growing pains remain, which he expects to be resolved over time.

Advice for teams designing for specialists

Gomboc's guidance is to invest in deep domain knowledge and stay exposed to users. Many of the company's designers and developers are aviation enthusiasts, and most product owners and internal experts know how to fly; onboarding is steep, but it enables substantive conversations with users and meaningful problem-solving. The stakes are unchanged at 35,000 feet — clear, reliable information — but the team can now put realistic, data-driven prototypes in front of pilots repeatedly, before production code exists.