One experience.
Three surfaces.

Resi is Pushpay's live streaming and video product — a separate platform with its own team, design system, and roadmap. The opportunity: an on-demand content experience that let churches offer congregants a branded, distraction-free place to watch past services, sermon series, and media.

The challenge wasn't building a media player. It was designing an experience that felt native across three very different surfaces — a standalone product (Resi On Demand / Media Sites), an embedded feature inside the Church App, and an admin configuration flow inside App Studio.

I was the sole designer on the end-user experience — working directly with the Resi product and engineering team, while continuing my work in App Studio and the Church App.

Each surface had a different user, context, and definition of success. The design had to work for all three without compromising any of them.

Designing across Resi and Pushpay meant navigating two design systems, two engineering teams, and two roadmaps — simultaneously. Every decision had downstream implications across at least two surfaces.

Resi sat with its own team, design system, and roadmap. My remit was the end-user side of two surfaces — the standalone Resi On Demand product, and how that experience lived inside the Church App. Five features anchored the work: playlists, live, search, tags, and recommendations.

Resi On Demand shipped as a fully branded, searchable content destination — live and on-demand unified in one place. Churches could offer their congregants a streaming experience they owned entirely, without competing algorithms or third-party interference.

The Church App integration brought that experience into the app congregants already used for giving, groups, and events — making media part of the community experience, not a separate destination.

The App Studio configuration flow gave admins a clear, self-serve path to set up and embed their media library — removing dependency on support for what should be a simple task.