Reely

The “video as a spec” idea is probably the most interesting part for me. It would be great if Reely could eventually detect when the app UI has changed and tell you which scenes need to be re-rendered. That could make launch videos much easier to maintain across releases.

The ability to create a polished promo video from just a screenshot or screen recording stands out to me. I especially like that Reely can match an app’s existing colors, typography, and interface instead of producing something that feels disconnected from the brand. Being able to create both portrait and landscape versions from one composition also seems genuinely useful for promoting an app across different platforms.

I build iOS apps and kept shipping features without a video. A decent one takes an afternoon, and the feature ships weekly, so it never happened. Every tool I tried wanted the same thing first. Get the app into the right state, perform the flow cleanly, do it again when you fumble, do it again when the UI changes. Reely has three ways in. You have screenshots, it builds the motion around them. You have a screen recording from any stack, your real app moves inside it. You have neither, and it works from the source: rebuilds the feature as a mock, runs it in the Simulator, records it. The third path turned out to matter more than I expected. Because Reely authored the run, it knows when every tap happened. It writes a timeline of labeled events next to the recording, so cuts and camera moves reference those events by name instead of by second. Re-record and every dependent beat retimes itself. Editing is natural language, in the app or through an agent. Renders locally. Happy to answer anything.