Percepto AIM screens: mission setup, pre-launch checks, live mission, and map views

Percepto · Remote ID

One flow cleared the rule blocking the US.

FAA Remote ID was about to stop Percepto's US business. I designed one mission flow across web, SMS, and the phone.

Senior Product Designer Web + mobile 2023
Problem
FAA Remote ID was about to block Percepto's US business.
Approach
I framed the end-to-end system with Product, Support and Engineering, then designed one mission flow across four surfaces.
Result
The flow shipped, met the FAA requirement and unblocked the US market.

One flow. Four surfaces. Cleared for the US.

  • USMarket unblocked
  • 4Surfaces connected
  • FAARemote ID compliance
  • 2023Shipped

Context

Start from the OKR, not from the wireframe.

Before user flows, I worked with Product to name the real business problem: without compliant sharing of operator and aircraft location, Percepto could not claim a complete US story. That framing turned "checkbox compliance" into a product and revenue constraint the whole squad could reason about.

The problem

Pre-launch failures were blocking missions before Remote ID was a factor.

GPS issues, heading errors, and sensor faults were stopping launches before the new rule even applied.

Power BI preflight failure analysis: bar chart showing technical failure frequency by category across flights

I paired operational data with field interviews. Power BI preflight reports showed which technical failures dominated real launches. We understood where risk concentrated for operators (heading, GPS, sensor checks), not only what felt slow in the UI.

That grounded problem definition in customer behaviour and failure frequency, not generic "bad UX."

User flow

Map every compliance path before committing to one.

Every potential compliance path (browser-based location, secondary mobile device, native app) had to be mapped against real field constraints.

Swimlane detail. Decision points, error paths, and constraints (e.g. takeoff disabled until user GPS is known).

Overview. End-to-end narrative flow, a fast read for the PMs and support leads who did not live inside AIM daily.

Cross-functional discovery

Three teams needed one picture of the failure.

Remote ID sits between policy, infrastructure, and frontline support load. I facilitated working sessions to get a shared picture of triggers, failures, and responsibilities: who owns the SMS, what happens when GPS is weak, how operators recover without abandoning the drone on the pad.

Solution and risk matrix: three direction options with value, viability, usability, and feasibility analysis

Three directions stress-tested. Each path evaluated against value, viability, usability, and feasibility, exposing hidden constraints before any implementation decision was made.

Key decision

Start from shared system truth, not from screens.

The default

Start with interface mockups for the Remote ID flow: build the screens, agree on the UX, then surface the cross-team dependencies as they appear.

The decision

Map the complete system model first (all surfaces, all owners, all failure modes) so the design work has a stable foundation and the team argues from one shared structure, not four separate mental models.

"Starting with screens would have meant designing against assumptions none of the teams had yet agreed on."

Layout exploration

Three architectures evaluated before one direction was committed to.

SMS link journey, two dedicated URLs, desktop browser path. Each was stress-tested against value, viability, usability, and feasibility before any implementation decision was made.

Three directions emerged from that mapping, each with a different tradeoff between speed to ship and quality of the field experience:

Secondary control: password entry with invalid credential state
Secondary control: connecting to secondary state
Secondary control: pre-launch Remote ID check state
Remote ID: location permission prompt from drone.percepto
Remote ID: ID indication false, connection failure state with map view

Explored three compliance paths. SMS link (fastest UX, required patience), native app (best UX, requires download), dedicated URL (middle ground).

Design

One mission flow across web and mobile surfaces Percepto did not fully own.

The UX had to hold together across AIM on desktop, an SMS handoff, a mobile browser, and native OS permission prompts, each with different constraints and different owners. That is the design problem: coherence across platforms, not polish on a single screen.

Design system

New Remote ID components, shipped into the AIM kit.

Location prompts, SMS confirmation states, and connection flows, built in Percepto's design language.

AIM UI kit: CTAs and interactions design system sheet: primary and outlined buttons, loading and success states, grouped layouts, ratings, and system controls on dark background

Outcome

Shipped, and cleared for the US market.

The flow shipped. The cross-device Remote ID journey met the FAA compliance requirement that had been blocking Percepto's US story, which unblocked the market it was built for. The outcome here is not a vanity metric. It is a regulated product that was delivered and approved, across web and mobile, under a real deadline.

The harder result is the one that does not show on a screen: three teams that did not fully own the same surfaces shipped one coherent journey because the system model was agreed before the design work started.

Reflection

The first design task is making the problem visible.

The first design task is often making the problem visible. In ambiguous product spaces, the most valuable thing is not drawing screens. It is making the problem clear enough that the team can stop debating it and start building against one direction. That framing is design work.

Systems that cross platforms need a shared model before they need a screen. Remote ID sat between policy, AIM on desktop, mobile, SMS, and OS prompts. Solving it meant getting the whole journey visible first, not as a design artifact but as the foundation the web and mobile work could stand on.

Research density matters more than research volume. A small number of operator conversations, mapped carefully against the system model, was more useful than a large study with no clear direction. The goal is not coverage. It is the insight that changes what gets built.