Sr.UI/UX Designer – Tung Lam

menu icon
Logo
Available for work
Hanoi, Vietnam 🇻🇳
Case Study · UI/UX Design

Talora Web Admin

A multi-tenant administration portal for the Talora Electronic Flight Bag platform — giving airlines one place to manage users, devices, documents, and navigation charts across 7+ operational modules.

Multi-tenant SaaS Aviation · EFB Desktop · 1440px 6 months
Project snapshot
Type
Multi-tenant SaaS
Platform
Desktop, 1440px
Industry
Aviation — EFB
Team
1 UI/UX Lead, 2 UI/UX Designers
Duration
6 months
My role
UI/UX Designer
Background

One admin portal, two levels of control, seven modules

Talora Web Admin is the administration backbone of the Talora EFB platform. It spans 7+ core modules — Talora Admin (multi-tenant), User & Device Management, EDocs, EForms, EPlates, System Integration, and the Admin Integration Control Center — serving two very different kinds of administrators.

Internal

Central Admin Portal

  • Platform & tenant management
  • License & feature toggle control
  • Billing oversight across airlines
Airline-facing

Customer Admin Portal

  • User, role & permission management
  • EFB device registration & assignment
  • Document & chart distribution for their tenant
Talora Admin User & Device Management EDocs EForms EPlates System Integration Integration Control Center
Talora Web Admin dashboard — active users, module status, AIRAC compliance and ePlate sync at a glance
Tenant dashboard — compliance & fleet status at a glance
Research — Market

An industry pivoting to AI-augmented decision support

The EFB/EFF market is dominated by two ecosystems — Boeing/Jeppesen and Airbus/NAVBLUE — with deep integration moats. The market's direction of travel is AI-augmented, advisory decision support, not autonomous operation. Talora positions itself as a phased-AI, advisory-first platform focused on regional and mid-sized airlines that the incumbents price out.

"Regional and mid-sized airlines are underserved by incumbents whose solutions are expensive to license and complex to deploy — that gap is Talora's entry point." Key market insight
Research — Competitors

Seven incumbents, one open flank

We mapped the full-platform EFB vendors on product scope and AI maturity, then compared each Talora module against its direct rivals to locate where differentiation is realistic — and where integration beats building.

VendorProductStrengthAI status
Boeing / JeppesenFliteDeck Pro, Fleet InsightLargest ecosystem; production AI assistant ("Elrey", 2025); tail-specific fuel advisoriesAI in production
Airbus / NAVBLUEMission+ Flight AssistantEnd-to-end integration: charts, weather, performance, checklists, docsNo AI claim
Lufthansa SystemsLido mPilot, aiOCCStrong OCC side (aiOCC assistant); data-rich, integrated EFBAI in OCC
Thales / AvioBookAvioBook EFB SuiteConnected suite: flight deck, cabin, OCC, maintenanceNo AI claim
Collins AerospaceFlightHub EFB/EFFReal-time data; ML-based ETAs via FlightAware ForesightML in data layer
SITAeWAS Pilot, OptiClimbML climb optimization; weather & turbulence awarenessML fuel optimization
Bytron SkybookSkybook EFBDocument modules, briefing integrationNo AI claim

Capability matrix — where Talora wins

CriteriaJeppesenNAVBLUELH SystemsThalesCollinsSITABytronTalora
Multi-tenant SaaS
AI / ML features
E-Plates (charts)
E-Docs management
E-Forms builder
Configurable workflows
Regional airline focus
Cost flexibility
Strong Partial / limited Weak / none
Key findings

Four openings that shaped the design brief

Finding 01 — Segment gap

Regional airlines are priced out

Incumbent platforms are expensive and complex to deploy. Regional and mid-sized carriers need mainstream capability without enterprise overhead — the admin portal must feel approachable, not avionics-grade intimidating.

Finding 02 — Architecture edge

Multi-tenant is the cost story

A shared, multi-tenant SaaS architecture is Talora's clearest structural advantage. The design consequence: strict tenant isolation made visible, so airline admins always trust whose data they're touching.

Finding 03 — Feature gap

E-Forms & configurable workflows are open space

No incumbent offers a strong forms builder or truly configurable workflows. This became a differentiating module — airlines customize processes without custom development.

Finding 04 — Build vs. integrate

Charts come from Keyvan, not from scratch

Partnering with Keyvan Aviation for chart content cuts licensing cost versus Jeppesen. The admin's job shifts from content management to distribution control — assignment, sync monitoring, and audit.

Positioning

What sets Talora apart

Highly configurable SaaS

Airlines tailor workflows without custom development.

Multi-tenant architecture

Lower cost, scalable across many airlines on one platform.

Phased AI approach

Advisory-first; no over-promising autonomous features.

Legacy format support

PDF/HTML briefings for smaller airlines mid-digital-transition.

Cloud real-time integration

Live weather, navigation, and flight planning data.

AI-enhanced SSDLC

AI tooling embedded across the development lifecycle.

Research — Personas

Two administrators, two mental models

The two-tier architecture demanded two personas with different risk profiles: one manages the platform across airlines; the other manages one airline's operation under regulatory scrutiny.

Persona A — Central Admin Portal

The Platform Operator

Context

Internal Talora operations staff managing tenants, licenses, and feature rollouts across every airline customer.

Goals

  • Onboard new airline tenants quickly and safely
  • Control feature toggles & licensing per tenant
  • Keep billing and platform health visible at a glance

Pain points

  • One wrong toggle affects a live airline operation
  • Cross-tenant context switching invites mistakes
Persona B — Customer Admin Portal

The Airline Admin

Context

Flight-ops administrator or document controller at a regional airline, accountable to EASA/FAA compliance audits.

Goals

  • Keep crew accounts, roles, and EFB devices current
  • Distribute the right document version to the right fleet
  • Prove compliance with exportable audit trails

Pain points

  • An outdated manual on a pilot's tablet is a safety finding
  • Manual distribution tracking eats hours every AIRAC cycle
Design process

From market map to design concept

Market Research

Scoped the EFB/EFF landscape, its shift toward advisory AI, and where regional airlines are left behind.

Competitor Analysis

Benchmarked 7 full-platform vendors plus module-level rivals; built the capability matrix.

Define Personas

Modeled the platform operator and the airline admin — two risk profiles, two portals.

Design Concept

Translated findings into a two-tier admin concept and a token-based design system.

Design solutions

Module by module

Module 01

User & Device Management

A portal for airline admins to manage user accounts, roles, permissions, and EFB devices — the front door of every tenant's operation.

A
User lifecycleCreate, update, deactivate accounts; assign roles; search & filter across the crew roster.
B
Device registrationRegister, assign, and revoke tablets/EFB devices tied to individual users.
C
Audit & complianceEvery action logged; compliance reports generated on demand.
User Management screen — crew roster with roles, status and device assignment
User Management — roster, roles & device assignment
Module 02

EDocs — Electronic Documents

Document libraries for EFB users: upload, versioning, distribution, and compliance — where an outdated manual is a safety finding, not an inconvenience.

A
Upload, versioning & metadataPDF/Office upload with auto-increment versions, effective & expiry dates.
B
Folder structure & access controlNested folders; documents assigned by fleet, role, or user.
C
Distribution & notificationScheduled publication, staged rollouts, email & push notifications.
D
Audit trail & reportingComplete audit log with exportable compliance reports.
EDocs screen — document library with versioning and distribution controls
EDocs — library, versioning & distribution
Module 03

EPlates — Navigation Charts

Chart content and metadata are fully managed by Keyvan Aviation — so the admin experience focuses purely on distribution and access, not content authoring.

A
Chart package assignmentAssign Keyvan chart packages to fleets and roles; monitor distribution status.
B
AIRAC sync monitoringView sync status and manage AIRAC expiry — updated automatically from Keyvan.
C
Overlay & layer visibilityConfigure NOTAM, airspace, and weather overlay visibility per user group.
D
Audit & complianceAudit logs, AIRAC expiry reports, and a distribution dashboard.
Design decision: because content is Keyvan-managed, the UI removes every authoring affordance — admins see status, coverage, and expiry, never editable chart data.
EPlates screen — Keyvan chart package assignment and AIRAC sync monitoring
EPlates — chart packages & AIRAC sync
Across the system

Compliance Dashboard & Electronic Flight Folder

Compliance visibility and flight-folder workflows round out the admin experience — surfacing AIRAC status, device compliance, and briefing packages in one consistent design language.

Compliance Dashboard — AIRAC compliance and device status overview
Compliance Dashboard
EFF — Electronic Flight Folder management screen
EFF — Electronic Flight Folder
Deliverables

A design system built for scale

The Talora Web Admin Design System underpins every module — a token-based foundation in SF Pro, tuned for dense enterprise screens at desktop 1440px.

7+Core modules designed
2Admin portals (Central + Customer)
300+Semantic color tokens
6Interaction states per token set
Reflections

What this project taught me

01 — Compliance is the backbone

In aviation, audit trails aren't a feature — they're the product. Designing traceability into every module from day one shaped cleaner information architecture than retrofitting ever could.

02 — Multi-tenant changes every screen

One design serves many airlines' configurations. Every layout had to survive different feature toggles, role sets, and data volumes without breaking.

03 — Differentiate, don't imitate

Competing with Jeppesen and NAVBLUE on feature parity is a losing game. The design bets on configurability and clarity — the things incumbents structurally can't offer.