Optimise for the workflow, not the demo
Why Reverie is built around production workflow rather than impressive demos — and what's next for clip creation UX.
There's a version of AI filmmaking that looks impressive in a demo and falls apart the moment you try to use it seriously.
The problem is almost always the same: the tools were designed around generation, not creation.
Generating a clip is easy. Knowing how to create that clip — what character is in it, where it sits in the story, what happened in the previous scene — that's the hard part. And most tools just hand you a prompt box and wish you luck.
Reverie is built the other way around. The story structure, the characters, the scene planning — that's the product. Generation is what happens at the end, once you know what you're making.
This week there are no new features to announce. What there is: a quiet week of work on making the existing features genuinely better to use.
🔭 Coming next: UX improvements to clip creation and scene planning flows.
The Scene Planner is genuinely powerful. But power without clarity is just friction. The next sprint is about reducing that friction — making it faster and more intuitive to go from a story idea to a generated clip, without losing any of the structural control that makes Reverie different.
Clip creation in particular is getting a rethink. The goal: you describe what you want, and the tool helps you get there — without requiring you to already know exactly what prompt will produce the right result.
📣 Early access open — 300 free credits for early adopters → reveriemovies.com?utm_source=linkedin
#Filmmaking #AIFilmmaking #IndieFilm #BuildingInPublic #GenAI #ScenePlanner #UX
What shipped
- Clip creation UX rethink in progress
- Scene planning friction reduction
- Story-first approach over generation-first