Case 04 · An AI video platform for filmmakers
A project that stays organized
The problemOn an infinite canvas I lose everything I generate. And when I export, I spend an afternoon renaming files.

Notes · Case 04
In short
A mood board to ideate before committing to a story, an asset history that ties every generation to the element or shot it came from, naming that the user controls at every level, and comments so the team reviews in place.
- Role
- Designed and built the mood board, asset history, naming and comments
- Client
- An AI video platform for filmmakers
- Year
- 2026
- Stack
- platform UI · export pipeline · image and video models on fal
What came out
- Every generation is reachable from the element or shot that produced it, with its full history
- Users name elements, shots and files in the product, and exports match their convention
- Review comments live on the shot, with the people who need to see them
Where it started
Two complaints kept coming from working teams. First, generation produces a lot of files, and the tools that treat the workspace as an infinite canvas leave you hunting for the one you liked an hour ago. Second, those tools name files for you. A post house with a naming convention gets a folder of random ids and a junior spends the afternoon renaming.
What I built
Four things that add up to one answer.
A mood board at the front of a project, so the team can gather references and try directions before anything becomes a story. What works gets promoted into the story with its lineage kept.
Asset history on every element and shot. Every generation is attached to the thing that produced it, in order, with what made it. Pick an older take, compare, promote it back.
Naming the user owns. Takes can be named in their history cards, and that name carries into the download. A take saved as SC01_SH02_v02 downloads as SC01_SH02_v02-Seedance_2.5.mp4, with the model added at the end. In the folder above I’ve trimmed that suffix.
Comments on the shot, so review happens where the work is, with the people on the project.
What was hard
None of it is flashy, and all of it is the difference between a demo and a tool a team uses every day. The discipline was keeping the structure strict enough that nothing gets lost and loose enough that a creative never feels filed.
