One editing workflow, reusable across formats.
Rendomat is a visual editor that turns approved content into videos and carousels. I've been designing it at GoInvo since January 2026 so that a content change doesn't require rebuilding every layout and timeline.
The workflow
Designers, researchers and project leads needed to update numbers, themes and formats without specialist video-editing work. I chose Remotion for reusable, content-driven layouts behind a visual editor: choose a project, arrange scenes, preview and render.
Rendering decisions
One scene model
I separated editable scene data from rendering jobs and final media. Scenes are typed React components that keep content separate from layout and theme. The editor, the aspect-ratio variants and the After Effects export share that data instead of maintaining separate timelines.
Render only changed scenes
Content and render-setting hashes identify reusable clips. FFmpeg adds transitions when it stitches the clips together, so editing a transition doesn't force the scenes on either side to re-render. In the local renderer, a failed forced render keeps the last valid cached clip.
Keep the editor responsive
Rendering runs in a worker process outside the editor's event loop, so the editor stays responsive while a render runs. Job status is kept separate from the scene content and timeline.
Scan frequency and cost
The patient journey
Excerpts from Radiology 101, rendered with Remotion and published on GoInvo's Instagram. Watch the full reel
Testing the output
The After Effects export is editable, but has not met its visual parity target. Rendering the imported files exposed hidden scenes, oversized placeholders and incorrect fonts that code review missed.
A comparison harness checks a fixed frame from each slide against the Rendomat reference. Difference images locate failures, and layer checks reject fixes that flatten editable text and shapes. The saved seven-slide comparison averages 0.917 SSIM, a visual-similarity score where 1.0 means identical. No slide meets the 0.95 acceptance target, so the export remains under review.
Current status
Illustrative project content fills the cover image and the editor screenshot, and the cover's Generate control is prototype UI. The SSIM comparison doesn't check factual accuracy, and I haven't measured time saved, team-wide adoption or throughput.
Remotion and FFmpeg render locally. Cloud rendering is environment-gated and is not a production multi-user service, so the hosted app is editor-only, with no authenticated render service. Public installers remain blocked by an unfinished migration that separates desktop packaging from server-only authentication and persistence.
AI coding agents implemented the system under my product direction, architecture, review and testing. Rendomat is built with React, TypeScript, Next.js, Remotion, FFmpeg, Electron, After Effects ExtendScript and PostgreSQL.