Journy: launching an AVOD app across every major OTT platform

Company

Ovation TV

Role

Digital Content Manager

When

Jul 2017 to Aug 2019

Scope

AVOD app launch + FAST distribution

Overview

Journy was Ovation's AVOD app for travel, art, and culture content. Free to watch, ad-supported, available on the platforms a casual streaming viewer actually used. We launched it across iOS, Android, Roku, Apple TV, Fire TV, and through FAST partners including Xumo, Plex, VEWD, and Samsung TV Plus. This was my first end-to-end product experience: platform certifications, content workflows, ad operations, and the full app lifecycle from "we want to launch" through "we launched and now we have to support it."

The problem

A new AVOD app trying to land on every major OTT platform at roughly the same time. Each platform had its own submission requirements, its own QC rules, its own metadata expectations, its own ad implementation, and its own clock. The content side had its own complexity: travel and lifestyle programs were coming in from multiple producers, getting packaged and metadata-tagged, and feeding out to all of those endpoints. The team that did all of this was small.

Context

AVOD as a category was just starting to mature. Audiences were used to Netflix and Hulu. They weren't used to free streaming apps with the polish of paid services. The bar for the app experience was higher than the brand could afford to chase by brute force, so the work had to be efficient.

Multiple stakeholders depended on the launch working:

• Content partners and producers needed their work to look right and reach audiences
• Advertisers and ad operations needed the ad inventory to behave consistently across platforms
• The platforms themselves (Roku, Apple, Amazon, Samsung, others) had their own certification standards that had to be met before the app would go live
• Internal leadership needed the launch to land on time across all platforms, not staggered over six months

My role

I worked across the content side and the product side:

• Coordinated with content partners and producers on content delivery, asset specifications, and the QC process
• Ran quality control on incoming digital content, catching and fixing audio, video, and metadata issues before they hit the apps
• Managed digital assets in the CMS and coordinated with media services on ingestion and storage
• Prepared content for FAST channel distribution and built the schedules and program guides for each partner
• Worked with the social media team to align content promotion with the FAST and AVOD calendar
• Reported to the Sr. Director of Content Partnerships and supported broader departmental goals

Mentored throughout by Elba Flamenco, who would later refer me to the Nexstar role.

What the operation looked like

Product decisions and trade-offs

• One content pipeline, many destinations. Building a single intake and metadata flow that served the apps AND the FAST partners meant we didn't duplicate the work for each surface. The alternative would have been one team per surface, which we didn't have.
• FAST as a real distribution strategy, not an afterthought. AVOD apps reach the viewers who already know to look for the app. FAST reaches viewers flipping through a channel grid. Building real schedules and program guides for the FAST partners (versus dumping a library) was the difference between "we're available" and "we're actually being watched."
• Platform certifications as a first-class part of the plan. Each platform has its own certification process. Treating those as part of the project plan from day one meant we didn't get surprised in the final weeks.
• Metadata as the connective tissue. If the metadata was right at intake, every downstream surface had what it needed. If it was wrong, every downstream surface had a problem.

Outcomes

Journy launched as the AVOD app for travel, art, and culture across iOS, Android, Roku, Apple TV, and Fire TV, plus FAST distribution through Xumo, Plex, VEWD, and Samsung TV Plus. The content pipeline supported all of those surfaces from a single workflow.

For me personally: this was the role that taught me what end-to-end product work in a streaming app actually feels like. Specs, vendors, certifications, content operations, support readiness, post-launch iteration. Every later role built on what I learned in this one.

What I learned

Multi-platform launches reward boring infrastructure. The interesting product decisions are upstream, in the content and metadata layer. The platform-specific work is mostly executional. Investing in the shared layer pays back across every platform.

FAST is its own product, not a side channel. Treating a FAST channel like a flat library dump is the easiest way to fail at FAST. Real scheduling and program guide work is what makes a channel feel like a channel.

Mentorship matters. Elba's guidance during the Journy launch shaped how I think about product work years later. The referral to my current role is downstream of that relationship. Worth saying out loud.

---

Back to all work