Code-Only Promo for Ten Indie Apps

Make a similar video

The vertical film starts with privacy/local-use copy, moves through several app screens inside phone frames and ends with an icon collection. Consistent framing and pacing turn separate apps into a series.

Your goal: Make a roughly 25–30-second multi-product reel, showing one representative action per product. This work belongs to the Claude Opus 5.5 video collection. Select Claude Opus 5.5 in an AI coding tool that supports it and submit the assets and requests below in stages. The model plans, writes and edits code; the actual project handles preview/export. Voice and music need suitable tools or supplied audio.

The creator names Claude Opus 5.5 + Remotion, actual screenshots, beat cuts and contact-sheet review, without sharing a generation prompt. Build a composition for a few products before expanding.

Prepare your assets

• Each app’s icon, name, actual screenshot and one value line.
• Consistently framed footage/screens and the desired product order.
• A shared collection theme, music and final action.

Put files in a directory AI can read, such as assets/, and explain each filename and purpose. Specify ratio, duration and publishing destination. If you supply only a URL, ask what content is accessible before assuming any functionality.

Replace elements for your product

Element in the sample or creator brief	Your replacement
Ten app icons	Your product list
Actual phone screens	One main screen per product
Local-first/privacy theme	Positioning genuinely shared by your products
Beat-aligned cuts	Your music and readable pacing

An education collection can connect preparation, learning and revision tools; modules within one SaaS can share one interface frame without needing ten apps.

Do not force every feature into the reel; apply privacy/data-handling claims only to products that support them.

Start with this shot plan

This is an editorial draft, not a frame-by-frame reconstruction. Approve assets and copy for each scene, adjusting durations to the information load.

1. 0–4s: shared theme.
2. 4–19s: three to five representative products.
3. 19–24s: icon collection and remaining products.
4. 24–28s: collection action.

Make it with AI in four steps

Editorial suggestion; not reproduction-tested. Fill in brackets and approve each preview before continuing. The creator’s film is not a downloadable project template.

1. Check assets and plan shots.

I am using Claude Opus 5.5 to make a video for [my product].
Goal: Make a roughly 25–30-second multi-product reel, showing one representative action per product.
Audience: [people]. Ratio and duration: [requirements]. Assets: [directory].
Read my product brief, identity and assets. List confirmed features and missing files.
Use the draft above to plan visuals, short headings, asset files, durations and transitions.
Do not force every feature into the reel; apply privacy/data-handling claims only to products that support them.
Provide the shot list before producing the full film.

2. Make one sample. After approving the plan and file paths, send:

The shot list is approved. Preview a switch between two apps with a stable phone frame and verify title/icon matching.
Production approach: The creator names Claude Opus 5.5 + Remotion, actual screenshots, beat cuts and contact-sheet review, without sharing a generation prompt. Build a composition for a few products before expanding.
Check dependencies and assets in this environment and provide the actual preview method.
Identify missing tools, models or audio rather than presenting placeholders as finished work.
Deliver this sample preview first, then list the files needed for the full film.

3. Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:

Complete the other shots using the approved sample's visual rules.
Do not force every feature into the reel; apply privacy/data-handling claims only to products that support them.
Match headings, actions and audio cues. If audio is unavailable, provide a silent preview first.
Keep product name, logo, screen assets, colors and final action in easily editable configuration.
Provide full playback and key transition stills, identifying unfinished parts.

4. Review and export. Check copy and assets on a phone, then send:

Apply the approved changes and export, retaining editable source and asset references.
Provide this project's actual export command, prerequisites and output file location.
Check final MP4 duration, ratio, text clipping and audio instead of relying only on browser preview.
Deliver a contact sheet and list remaining limitations.

Remotion uses frame-driven animation; export needs your actual entry point, composition ID and output path. See animation fundamentals and the render CLI.

Revise the film and fix problems

Name the shot and change instead of requesting vague improvements that reset approved pacing:

Change only the order to [list], keeping one main screen and heading per app. Provide a shot-ordered contact sheet before full export.

For a 9:16 version, recompose headings, the main subject and final action. Preview the new layout rather than cropping the sides. To shorten the film, remove secondary shots or sentences before retiming.

• Products are hard to distinguish: show the matching name and icon during each switch.
• Beat cuts are too fast: reduce the product count or extend duration without sacrificing readability.

Creator source and reproduction limits

The post describes ten apps, real screenshots, Remotion and frame review. This description is removed from the author-prompt area; the requests below are editorial. View the original post.

Visual descriptions come from the collected video; production details come from the stored request and post. They do not constitute testing of the current product. Shot plans, adaptations and expanded requests are editorial suggestions and have not been generated or tested. Supply your own assets and production environment when the original project is unavailable.