1 comment

[ 2.9 ms ] story [ 11.5 ms ] thread
Hi HN,

I've been working on a problem that frustrates me with current "Screenshot-to-Code" tools: they are static. They capture the layout, but they miss the behavior (animations, loading states, navigation flow).

So I built a pipeline that treats video as the source of truth.

Instead of analyzing a single frame, the engine parses the video timeline to extract a rudimentary state machine before writing any code. This allows it to reconstruct:

The initial state.

The trigger (click/scroll).

The resulting state (modal open, menu slide-in).

It outputs a clean React + Tailwind project that actually functions, rather than just looking like a picture.

The Update: High-fidelity video inference is expensive (GPU costs), so I had it gatekept. I just optimized the backend and opened up 2 free reconstructions for everyone because I need to stress-test the model with diverse, real-world edge cases.

You can try it here (no credit card): [LINK DO REPLAY]

I’m looking for feedback specifically on the generated component structure – does the code feel "human-written" to you, or does it still smell like AI spaghetti?

Bash away!