What is the product context?
CRREO brings video creation tools into one product. Its public workflow moves from an idea to characters, scenes, timeline editing and export. The interface needs to explain both the current task and its place in the wider project.
I have worked with the team since March 2022. The contribution described here covers step navigation, character and scene flows, responsive layouts and related frontend interactions. This is a view of my contribution within a team product, not a claim of sole authorship.
Why does navigation matter beyond the stepper?
A stepper gives a workflow a visible order, but the user’s work is not always linear. Reviewing a character can mean returning from a later stage. Revisiting scenes can follow a first look at the video. A useful interface helps people understand where they are and what they can change.
When reviewing this type of flow, I separate orientation from action: the step label identifies the stage, the page explains the decision, and the primary control states what happens next. That distinction keeps a navigation control from becoming a substitute for clear page content.
- Identify the active step with a label as well as a visual treatment.
- Keep the current project context visible when moving between tasks.
- Explain any consequences before an action replaces existing work.
How do character and scene flows connect?
Characters and scenes express different decisions. A character library supports choosing a recurring identity; a scene workspace supports reviewing a particular moment. Giving them the same generic presentation can obscure what the user is selecting.
The design question is therefore about the object and the action together: what is selected, what can be edited, and which part of the project will change? Descriptive labels and clear selection feedback help make that relationship legible.
What changes on a smaller screen?
Responsive work includes access to controls, not just a narrower grid. Menus that are easy to reach with a pointer need an explicit touch interaction. Long titles, previews and selected states must remain understandable when fewer items fit on screen.
My scope includes responsive layouts throughout the Video Maker. A useful review follows a complete task at a narrow width: choose an item, inspect it, return to the flow and continue. Checking a static screenshot alone does not cover that sequence.
What can this case study demonstrate?
It documents the areas of the product I contribute to and the interface concerns that connect them. The public product provides context; the portfolio describes my role. Conversion uplift, completion-time improvements and other private product metrics are not reported here.
The next case study looks more closely at editing interactions. The accompanying workflow guide turns the broader questions into a practical review checklist.