Design the meeting experience
Build browser-based rooms with branding and presenter/guest roles for different session contexts.
Connected video experiences
Branded, browser-based meeting spaces that connect a live conversation with the wider digital service around it.
Group product · demonstrations by arrangementExperience design · Real-time video · Recording workflows · Operator tools
01 / The problem
A live session often sends people away from the service they came to use. The meeting, recording and follow-up become separate experiences, with a different set of controls for the team operating them.
We wanted video to feel like part of a business’s own product. Studio explores how branded rooms and the work around a meeting can be brought into a more connected experience.
02 / The work
Build browser-based rooms with branding and presenter/guest roles for different session contexts.
Develop recording management, transcripts and summaries around the live meeting.
Build administration for accounts and embed configurations, with recording retention and deletion controls.
03 / The system
The work connects a branded meeting experience with the operational system behind it: access, roles, recordings and the decisions about what happens to those recordings.
A lobby with camera preview and device selection before entering.
Browser-based video with presenter and guest roles, screen sharing and branding.
A recording workflow with transcription and summary processing.
Operator tools for accounts, embeds, recording access, retention and deletion.
Built around Cloudflare RealtimeKit, with Workers coordinating the application and storage services supporting recording workflows. Motivation develops the experience and integration around that infrastructure.
04 / Research & development
Separate access to the lobby from the action that joins the room. Integrate device preview and selection with the meeting SDK’s own state.
Initialising a meeting and entering it are different events. Working through duplicate lobby and concurrent-join behaviour informed the two-step entry design.
Connect recording, transcription and summaries with storage and operator controls. Develop retention and deletion behaviour alongside the recording experience.
Capturing a file is only one step. Access, processing state, failed jobs and the lifecycle of the resulting information also need to be designed.
Develop presenter views and screen-share layouts around the meeting interface, including the space needed for participants and side panels.
The local meeting layout and the composition of a recording are separate concerns. Each needs its own checks rather than assuming one proves the other.
05 / Where it stands
The work covers the meeting interface, recording workflow and the operator’s experience. It is a practical example of connecting a customer-facing product with the systems needed to run it.
Studio demonstrates how we work across interface design, real-time systems and operations. A demonstration is the next step for assessing a particular deployment and its requirements.
Product readiness and the requirements of a specific deployment are assessed through an agreed demonstration. We do not make blanket claims about data residency or suitability for every organisation.
Our track record
Client delivery. Products of our own. The everyday work of making them run. Each gives us a different perspective on what makes technology useful.
Explore our delivery track recordOur team’s work connects brands, creators and educators with their audiences, through digital platforms and the systems behind them.
We live with the products we create. Supporting them beyond launch informs the decisions we make on the next one.
Recurring problems become reusable technology. The questions still unanswered become the starting point for our research.