Inspiration
Bartzilla creates videos. His strongest shot of a monument started on a miniature and pulled back to reveal the real structure. The creative decision happened while filming, before the edit. Creator Shot Guide asks: how could spatial references help a creator rehearse that decision while keeping attention on the scene?
What it does
Place camera start A, finish B and an independent look-at TARGET. Choose opening hold, movement and closing hold; rehearse the plan with a virtual cue. Save a reference, change a decision, and replay reference and current plans without silently overwriting the original. EDIT, FRAME and COMPARE pages separate the tasks. A labelled synthetic inset illustrates framing intent; it is not a connected phone camera.
Why spatial
Camera endpoints and the look-at target belong around the planned subject, rather than only in a list of notes. The intended benefit is less switching between notes and the scene. Camera targeting and previsualisation already exist: our contribution is the compact creator decision loop combining placement, timing, framing intent and explicit comparison, not a claim to have invented camera mathematics.
How we built it
Lens Studio 5.23.2, TypeScript, CLAD and the Lens Studio MCP, Spectacles Interaction Kit and UIKit. The concept and filmmaking priorities came from Bartzilla; detailed implementation defaults and AI-assisted development are disclosed in the repository's devpost/design-brief.md. Snap components and template resources are credited separately. No paid API, cloud vision or background filming is needed.
Challenges and what we learned
A successful input command is not proof that an application changed. Independent checks caught missed and duplicate actions. We replaced a dense control wall with three pages and added a one-second UI gesture lock. Reference snapshots copy values rather than retaining aliases to editable plans. Failed iterations were retained instead of being described as successes.
What is verified
The working project passed 49 native Preview assertions, including genuine marker drag, reference/current playback, cancellation and unchanged source hashes. Separately, 62 pure logic assertions cover calculations, immutable snapshots and invalid inputs; these passed again on a fresh clone of the public repository. The 94-second demo is a continuous real-time Preview recording with enlarged controls from the same frames and English explanations. It is silent by design. Source backups were restored and hash-checked.
Limits and next steps
Preview validation is not a headset field trial. No phone tracking or control, obstacle detection, scene recognition, persistent anchors or guaranteed filming improvement is claimed. References last for the current session. Framing is illustrative. No LEAF test pass is claimed; native Preview checks and Node logic checks are separate. The next useful study is to compare planned and captured reveals and record whether the spatial references help or distract creators.
Reproduce and inspect
The public repository includes the Lens project, scene, source, planning documents and reproducible logic tests. Snap binary dependencies are not redistributed under an assumed licence: dependencies.json records exact versions by file hash, with a tested helper to restore them from an existing licensed local package set. A fresh Lens import of that source distribution is not claimed. See README and THIRD_PARTY.md for setup and attribution.
Built With
- lens-studio
- typescript
Log in or sign up for Devpost to join the conversation.