IFE Content Operations Platform Case Study

Problem

Airlines and the programming team were managing in-flight entertainment the hard way — content selection, licensing rights, proposals, budgets, metadata, and OEM deliveries across email, sheets, and scattered tools. They needed one cloud platform where studios, the programming team, and airline clients could browse a content library, build proposals, track deals and rights, push metadata to OEM systems, and keep programming cycles on track.

Solution

We built and keep developing a Laravel web app for the full IFE content lifecycle: searchable library (movies, TV, audio, podcasts/playlists), client proposals and content deals, licensing/rights and fleet setup, OEM metadata templates/exports, client portals, workflows/timelines, FlixPatrol rankings, 2FA, carts, and financials/reporting. Related work on the same account: a field-name and conditional formula system inside OEM templates, and a Next.js microsite on the Microsite API (tenant-by-subdomain, theme config, cycle-driven heroes and GUI sections, title detail, search, session-aware language).

IFE operations web app

Laravel, MySQL, role-based access

Passenger microsite

Next.js on the Microsite API

Integrations

FlixPatrol
OEM metadata templates (Panasonic-style packs)

Problem

IFE programming ran across email, sheets, and scattered tools: content selection, licensing, proposals, budgets, metadata, and OEM deliveries.

Solution

We built a Laravel web app for the IFE content lifecycle: library, proposals, rights, OEM metadata exports, client portals, workflows, FlixPatrol rankings, 2FA, carts, and reporting.

Results

Gave the programming team and airline clients one place to run IFE programming: faster browsing and proposals, clearer deal/budget visibility, cleaner rights handling, and automated metadata/OEM packing.

Proof note

This IFE platform: the source record did not include measurable outcomes or a client testimonial. Text under Results is copied from the engagement notes and is not presented as a verified KPI.

Related work on the same account

OEM templates needed dynamic field names and conditional formulas so labels and values could change by product, region, or rules without duplicate configs. We built a formula system inside OEM templates, reused in technical profiles. Recorded result: fewer manual template variants, faster setup for new OEMs, and consistent naming.

They also needed branded passenger microsites (titles, categories, promos, per-client theming and languages, cycle-based content) without a custom site for every client. We built a Next.js microsite on the Microsite API: tenant-by-subdomain, theme config, cycle-driven heroes and GUI sections, title detail, search, and session-aware language/route handling. Recorded result: faster client launches, consistent UX across tenants, and content updates through the admin hub instead of frontend redeploys.