Lapse
A proof of concept that put a product weaving photos into flowing video onto the canvas-builder engine through a single connector.
- 2026.05 ~ 2026.07
- Firstage
- Design and implementation (solo)
Core value
Confirmed that a product with no print specification can be edited on canvas-builder without changing the engine.
Outcomes
- Edited 16:9 video pages with no print margin through a single connector
- Timing details such as scene length and transitions remain in the engine document format
- The engine behaves the same whether or not timing details are present
Tech stack
Context
I built this experiment to see whether canvas-builder could hold a product other than photobooks. Starting from the idea of photos that flow like video, I set up a 16:9 video canvas and used the same engine to edit a product with no print specification.
Decisions and implementation
- The engine logic stayed untouched, and the product attached through a single adapter. Pages use a 16:9 video size with no bleed to describe a product that is never printed.
- Scene duration, scene transitions, and an audio track are optional fields in the document model. Engine code never branches on them, and I drew the boundary so that a product-side renderer interprets the timeline.
- The editor combines react-hook-form with the engine provider and adds an engine plugin that gathers changes into auto-saves.
Current state
I built the proof of concept in May 2026. Through July I only fixed what other changes broke, and no feature work followed. The renderer that turns the timeline into video is left for the next step. The timeline fields defined here remain in the canvas-builder document model.