Revio product walkthrough

Project Snapshot

Product
Revio
Product type
Video review and approval platform
Role
Product Designer
Timeline
Jan–Sep 2026 · 6 months
Scope / status
Research to Working MVP

I led the research and end-to-end UX/UI design, then developed the working MVP—including both frontend and backend—with assistance from Codex and Claude.

Problem

Scattered feedback. Unclear approval.

Editors received feedback through WhatsApp, Telegram, email, and other messaging channels. They manually gathered messages, voice notes, screenshots, and time references before turning them into editing tasks. Feedback could lose its connection to the correct moment or version of the video.

Clients also faced unfamiliar review tools, account creation, and unclear approval steps. When the workflow felt complicated, they often returned to the messaging apps they already used.

Research

Where review workflows broke down.

Reddit was my main channel for conversations with video editors. I also observed five users working with dedicated review platforms and interviewed three others who managed feedback through messaging apps.

I followed the full review cycle: receiving feedback, revising the video, sharing another version, collecting more comments, and reaching approval.

01

Feedback lost its context

Editors had to copy feedback from different conversations into their own notes and determine which request belonged to which moment in the video.

“Half my battle is copying and pasting unformatted chaos from client texts into my own notes.”

Reddit commenter, u/Upset-Animal1376Response received after I shared the proposed product; not a Revio usability-test observation.
02

Versioning was difficult to discover initially

Participants described that, when they first started using Frame.io, they uploaded revisions as separate files because they did not know how to group them as versions. After watching tutorial videos, they learned to drag a revision onto an existing video and were already using that workflow when I observed them.

03

Clients wanted less friction

Editors needed structure, while clients wanted a quick way to review and respond. Account creation, unfamiliar interfaces, and unclear approval steps could make clients avoid dedicated review tools.

Key insights

Product principles

Three principles guided the design:

  • Keep feedback in context. Feedback should remain traceable to the relevant version and moment, even when received outside Revio.
  • Make versions easy to manage. Adding and finding versions should be clear from the first use.
  • Keep client review simple. Give editors structure while minimizing setup and complexity for clients.
Design response

How these principles shaped the product

01

Bring scattered feedback into context

Editors can paste feedback or add screenshots from WhatsApp and other channels to the review workspace. Recognizable timecodes connect comments to video moments; unclear timing requires editor review. This accommodates clients’ existing communication habits while helping editors keep feedback together.

02

Make versions visible

An explicit Add Version action and a selectable version list make revisions easy to find, with playback, comments, and comparison close at hand.

03

Reduce client setup

A direct review link lets clients view, comment, and approve without creating an account, while editors manage versions and feedback in their workspace.

Concept testing and iteration

Three changes kept the review moving.

Keep commenting in the viewing flow

Early prototypes placed the comment input in the right panel. During usability testing, I observed reviewers pause the video and shift their attention away from the content before writing feedback. I moved the input directly below the player. In follow-up sessions, participants found it more directly and left comments with less interruption.

Add revisions without leaving Review

The earlier workflow required editors to leave Review and return to Project Details to add a revised file. I added Add Version inside the review workspace, beside the player and version list, so editors could continue the versioning workflow without leaving the active review context.

Separate feedback from approval

The early approval flow connected a formal decision with the comment interaction, leaving users unsure whether to send feedback or approve first. I kept commenting in the input and made Approve version a separate, explicit action.

Outcome and learnings

From research to a working MVP.

I led Revio from research and product definition through UX/UI design, testing, iteration, and a working MVP. All eight participants completed every assigned task without assistance, with no blocking usability issues observed. Repeat use and willingness to pay have not yet been evaluated.