Resi × Pushpay · 2023–2024

Resi On Demand:
streaming built into white-label community apps

Designing Resi On Demand end-to-end: from the viewing experience itself, to how it lives inside the community app, to how admins configure it in App Studio. One product. Three audiences. No seams.

My role

UX Designer (UX2)
Sole designer across end-user experience, community app integration, and App Studio admin configuration

Teams collaborated with

Resi Product & Engineering · App Studio Engineering · community app team

Surfaces designed

Resi On Demand (end-user) Community app integration App Studio (admin)

Status

Shipped · Live

Surface 01

Resi On Demand

The viewing experience: browsing, playlists, on-demand content for end users (members)

Surface 02

community app

How Resi On Demand is embedded and experienced within the community app ecosystem

Surface 03

App Studio

How community admins configure, connect, and embed the Resi media library into their app

The brief

A Netflix-style media library.
Built into white-label community apps.

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 communities offer members a branded, distraction-free place to watch past broadcasts, 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 community app, and an admin configuration flow inside App Studio.

"No redirects. No competing algorithms. No distractions. One destination where your audience can watch live and explore past content, all in one place."

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 community app.

View Resi On Demand live ↗

The work

Same product.
Three design problems.

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

Surface 01 · End user

Resi On Demand

The core viewing experience for members. A branded, searchable content library where live streams auto-save and on-demand content is organised into playlists and series. Designed to feel familiar, like a streaming service, while remaining distraction-free and entirely owned by the community.

  • Browse, discover, and watch on-demand content
  • Playlist and series organisation
  • Live + on-demand unified in one destination
  • Branded experience: no third-party interference

Surface 02 · community app

In-app integration

How Resi On Demand lives inside the community app. The challenge: integration without the seam showing. Content needed to feel native to the app, not a webview dropped in. Members shouldn't feel like they've left the app to watch a video.

  • Seamless embed within community app navigation
  • Consistent visual language across both products
  • Minimal friction from app to content

Surface 03 · Admin

App Studio config

The admin-facing configuration flow: how community admins connect their Resi account, set up their media library, and embed it. Close collaboration with App Studio engineering kept the flow clear enough for non-technical admins to complete without support.

  • Resi account connection and authentication
  • Media library configuration
  • Embed and publish flow

Design challenges

Working across
two product systems.

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

01
Two design systems, one coherent experience. Resi had its own visual language. The community app had Prism. The integration had to feel native in both without creating a third, undefined aesthetic.
02
Different users, shared content. Admins configure what members see. Every admin decision has a direct end-user consequence, which meant designing both sides with that dependency always in mind.
03
Familiar but not generic. The "Netflix-style" reference set expectations. The design needed to feel intuitive, leveraging familiar patterns, without looking like it was just copying a consumer streaming app for a community context.

Deep-dive

Resi On Demand, up close.
The end-user surfaces I designed across two products.

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 community app. Five features anchored the work: playlists, live, search, tags, and recommendations.

"What admins curate upstream becomes what members browse, search, and play."

Surface 01: Resi On Demand

Landing built for short attention.

Live takes precedence when active. Playlists and series carry the experience the rest of the time. Recommendations run alongside, tuned for sparse libraries: most communities have hundreds of items, not thousands, so the logic deprioritises freshness in favour of completeness.

home page default.png
Resi On Demand desktop landing page
Resi On Demand · Desktop

Live, playlists, and recommendations on one shelf.

home page default mobile.png
Resi On Demand mobile landing page
Resi On Demand · Mobile

Same hierarchy, restacked for thumb reach.

Surface 01: Resi On Demand

Search results, not search misses.

Most viewers don't type full titles. Results prioritise partial matches across title, series, and tag. Tags surface near the content, not buried. Admin-applied tags become member-discoverable filters in the same view.

result page.png
Resi On Demand desktop search results
Resi On Demand · Desktop

Tag filters live alongside results: one view, no extra page.

result page mobile.png
Resi On Demand mobile search results
Resi On Demand · Mobile

Filters fold into the same scroll, not a separate flow.

Surface 02: community app

Same content, native shell.

Resi On Demand inside the community app had to feel native to the app, not like a webview dropped in. Players, controls, and navigation align with the rest of the community app so members don't feel like they've left.

Watching state · 01
community app Resi VoD watching state
community app · 01

Resi content, community app chrome: same household.

Watching state · 02
community app Resi VoD watching alternate state
community app · 02

Player + adjacent content laid out for in-app continuity.

Pattern worth noting

Two-sided design discipline.

Every end-user feature has an admin control upstream: a playlist someone built, a tag someone applied, a recommendation rule someone tuned. I designed the visible side, knowing the invisible one shapes every choice. The pattern: design for what the user does, while respecting what the admin needs to be able to do.

What shipped

Live, branded,
distraction-free.

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

The community app integration brought that experience into the app members 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.

View the live product ↗

Next case study

Unified Ecosystem: Staq Modernisation →
↗