Your tool might actually do more than you planned.

When I started building Replay, the mission was specific: Behavior-Driven UI Reconstruction. I wanted to solve the problem where static screenshots fail to capture the flow, animations, and logic of a complex SaaS or mobile app.

But I got curious: "What happens if I feed the engine a video of a physical product instead of a digital interface?"

I grabbed a pack of wipes, recorded a 5-second clip, and dropped it into the pipeline.

The result? Watch the video.

Even though this isn't Replay's core function, the engine "understood" the product. It extracted the color palette, the brand vibe, and the context-generating a fully responsive, sales-ready Landing Page in one shot.

It turns out that Video-to-Code isn't just about UI flow; it's about context.

I am still laser-focused on polishing the core engine and shipping new features, but seeing the tool handle edge cases like this is the best part of the founder journey.

If you are curious to see what Replay looks like right now: Link to the tool in the first comment.