Product launch video, made in code
Turn your app or website into a polished launch or product overview video. The AI reads your links and screenshots, plans a storyboard, then builds and renders the video with React and Remotion.
A storyboard, the Remotion project and a rendered 16:9 MP4 Claude Code, or any AI coding agent that can run code About 10 minutes to fill in
The prompt
Highlighted parts are for you to fill in (33)
PRODUCT VIDEO PROMPTFill in the [brackets] below. Delete any line you don't know; the more you give, the better the video.Attach screenshots, screen recordings, your logo and any brand files to the same message.ROLEYou are a senior motion designer and creative developer. Your job is to make a polished, professional product video entirely in code using React and Remotion, the kind of video a good studio would charge for.Treat this as a real motion design project, not a coding exercise. Composition, typography, pacing and storytelling matter as much as the code.PART 1: ABOUT MY PRODUCTProduct name: [NAME]One-line description: [WHAT IT IS AND WHAT IT DOES, IN ONE SENTENCE]Links (read every one of these before planning anything):- Website: [URL]- App Store: [URL]- Google Play: [URL]- Demo video, walkthrough or launch post: [URL]- Other useful pages (pricing, docs, changelog, Product Hunt): [URLS]Who it's for: [BE SPECIFIC, e.g. "solo founders who've launched an app but can't get users", not "everyone"]The problem they have before using it: [IN THEIR WORDS, IF YOU CAN]The main benefit, the one thing they should remember: [ONE BENEFIT]Features to show (2 or 3 max), and where each one lives in the product:1. [FEATURE]: [WHAT IT LETS THE USER DO] (screen: [WHICH SCREENSHOT OR PAGE])2. [FEATURE]: [WHAT IT LETS THE USER DO] (screen: [WHICH SCREENSHOT OR PAGE])3. [FEATURE]: [WHAT IT LETS THE USER DO] (screen: [WHICH SCREENSHOT OR PAGE])What makes it different from alternatives: [YOUR EDGE]Proof I can honestly use (real numbers, real reviews, awards; leave blank if none): [PROOF]Price or offer: [e.g. "free to start", "7-day free trial", "launching Tuesday"]PART 2: MY BRANDBrand colours (hex): [e.g. #233137, #3f7385, #f7f1e8]Fonts: [FONT NAMES, OR "match my website"]Logo: [ATTACHED / FILE NAME]Brand personality in 3 words: [e.g. calm, clever, honest]Things to avoid: [e.g. "no neon", "no stock-footage feel", "no exclamation marks"]Videos or brands whose style I like, and what I like about each: [LINK + WHAT YOU LIKE]PART 3: MY ASSETSList what you've attached and what each one shows:- [screenshot-home.png: the dashboard after sign-up]- [screenshot-feature.png: the moment the user gets their result]- [recording.mp4: 20s of someone using the main feature]- [logo.svg]If I haven't attached something you need, tell me what it is before you build.PART 4: THE VIDEOType of video: [LAUNCH TEASER / PRODUCT OVERVIEW / SINGLE FEATURE DEEP DIVE / AD]Where it will be posted: [e.g. Instagram Reels, TikTok, X, YouTube, website hero, Product Hunt]Aspect ratio: 16:9 landscape (1920x1080). [OPTIONAL EXTRA VERSIONS: 9:16 / 1:1 / 4:5, or delete this bracket]If I ask for more than one aspect ratio, build each as its own composition with its own layout. Never just crop or letterbox one into another.Length: [e.g. 15 to 25 seconds]Sound: [SILENT WITH CAPTIONS / MUSIC ONLY / VOICEOVER + MUSIC]Voiceover: [NO / YES: write the script and time each line to its scene]Call to action at the end: [e.g. "Try it free at yoursite.com"]Final frame text or tagline: [TAGLINE]Approval: [STOP AFTER THE STORYBOARD FOR MY OK / GO STRAIGHT TO BUILDING]STEP 1: UNDERSTAND THE PRODUCT FIRSTBefore planning anything:1. Open every link above and study every attached asset.2. Write a short summary of your understanding: what the product does, who it's for, the main benefit, and the 2 or 3 features you'll show, each with the screenshot you'll use.3. If something essential is missing or unclear, ask me up to 5 short questions. If it's minor, make a sensible assumption and say what you assumed.Never invent features, numbers, testimonials, logos of customers or results. Only show what the product actually does.STEP 2: STORYBOARDPropose a storyboard as a numbered list of scenes. For each scene give:- What the viewer sees (layout, device or crop, motion)- What the viewer should understand from it- The exact on-screen copy- The voiceover line, if any- Duration in seconds- How it hands off to the next sceneStart from this structure and adapt it to the product and length:1. Hook (first 1 to 2 seconds): a short line about the problem or the benefit. The very first frame must make sense on its own, with no animation needed, because many people will only see that frame.2. Product reveal: show the product cleanly in a phone or browser frame. Say what it is, nothing more.3. Feature moments: one scene per feature. Zoom or crop into the exact part of the interface that matters and link it to a concrete benefit.4. Close: product name or logo, the call to action, and the URL. Hold it for at least 2 seconds so it can be read.Don't add scenes just to fill time. Shorter and clearer beats longer.If I asked you to stop for approval, stop here and wait for my reply.STEP 3: CREATIVE DIRECTIONLook and feel- Clean, modern and premium. The product is the hero; copy and motion support it.- Use my brand colours and fonts. Keep the palette restrained, the backgrounds simple, and the spacing generous.- Create depth with soft shadows, layering and changes of scale, not effects.- Vary the framing between scenes: a full product view, a close-up on a detail, and a wider layout with supporting text.- Keep one visual language throughout. Transitions, text styles, device frames and colours should feel like one piece.Showing the product- Use my real screenshots and recordings. Keep their proportions and keep the important parts sharp and readable.- Guide the eye with framing, a slow push-in, a crop or a subtle highlight on the relevant part of the interface.- A well-chosen crop beats a full screen of tiny details.- If an asset is missing, you can build a simplified interface element, but it must match the product and my description. Say which elements you recreated.Motion- Every movement should introduce information, show hierarchy or connect scenes.- Use smooth eased entrances and exits, gentle position and scale changes, text that reveals in reading order, and transitions that carry an element from one scene into the next.- Vary the rhythm: some beats quick, others still so the viewer can take them in.- Time text and visuals together. When a line names a feature, the matching visual appears at the same moment.- No constant motion, spinning, bouncing for its own sake or effects that fight the content. Let key frames settle.Typography and copy- Short, specific lines. Benefits over buzzwords. Speak the audience's language.- One idea per scene. If a line needs a long pause to read, cut it or split it.- Clear hierarchy: headline, supporting line, small label.- Use the width of a 16:9 frame: side-by-side compositions (headline on one side, product on the other) usually work better than stacking everything in the middle.- Size text so it's still readable when the video is watched on a phone. On a 1920x1080 frame, headlines at least 80px and supporting text at least 40px.- Keep important text and visuals at least 80px in from every edge.- If I asked for a 9:16 version too, keep its text and key visuals out of the top 14% and bottom 35% of the frame, where the app's buttons and captions sit.- Check every line break. No single words left alone on a line.Sound (if requested)- Write the voiceover so it sounds like a person talking, not an advert. Time each line to its scene.- If the video will often be watched muted, add burned-in captions that match the voiceover.- Leave music low enough that the voice is always clear.STEP 4: BUILD- Build in React with Remotion. The main Composition is 1920x1080 at 30fps. Add one more Composition for each extra aspect ratio I asked for.- Put all editable content in one config file: copy, colours, fonts, asset paths, scene order and scene durations. Changing a line or a colour should never require touching the animation code.- Make each scene its own component, plus a few reusable pieces (device frame, text reveal, highlight, transition).- Load fonts properly (for example with @remotion/google-fonts) and reference local files through staticFile().- Build the full sequence roughly first and check the story works end to end. Only then polish individual moments.STEP 5: REVIEW BEFORE HANDING OVERRender still frames from every scene, including frame 0 and the last frame, and actually look at them. Check that:- The first frame communicates on its own.- Each scene has one clear focal point.- All text is readable on a phone and stays up long enough to read.- Screenshots are sharp and not stretched.- Nothing is cut off, overlapping or sitting in the unsafe areas.- Transitions feel connected and the ending feels deliberate.- Any voiceover and captions are in sync.Fix anything that feels rushed, empty, repetitive or crowded, then render again.DELIVERABLES1. Your summary of the product and any assumptions you made.2. The storyboard.3. The complete Remotion project.4. The rendered 16:9 MP4, plus one for each extra aspect ratio I asked for.5. A short guide covering how to change the copy, colours, assets and timing, how to preview, and how to re-render.Use any reference videos as guidance for quality and mood only. Create your own compositions and animations rather than copying them.
UserClimb
Made the video? Now know what to post next.
Paste your app's link and UserClimb makes 15 posts for your app in three formats, built from your app, your demo and this week's top app posts. Your first 6 posts free, no card.