Vertical App Feature Walkthrough

Make a similar video

The vertical Motoseyir film shows route screens, stop ordering, a voice assistant and group riding, with graphics extending outside the phone. Screens and contextual graphics explain navigation use.

Your goal: Make a roughly 45–50-second vertical feature demo combining actual simulator recordings and surrounding motion. 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 stored request demands actual simulator recordings rather than fabricated UI. The post says music was handled with ElevenLabs. Confirm simulator access first; otherwise record and supply the clips yourself.

Prepare your assets

• Record each action, result and state change in the simulator.
• Feature names, demo data, app icon and brand colors.
• Music or a separate audio plan and target social format.

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
Routes and group-ride screens	Your actual core-action recordings
Routes outside the phone	External graphics related to the feature
Map distances and labels	Values actually visible in your demo
Navigation identity and vertical format	Your app identity and output format

A travel planner can show destination selection, ordering and route sharing; a task app can show filtering, opening and assignment. Surrounding graphics should explain actual behavior.

Keep each feature visible for at least the requested 2.5 seconds, avoid social-platform controls and use metrics from the footage.

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–5s: product positioning.
2. 5–15s: first real action.
3. 15–27s: second feature and result.
4. 27–39s: third feature or collaboration.
5. 39–48s: recap and download 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 45–50-second vertical feature demo combining actual simulator recordings and surrounding motion.
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.
Keep each feature visible for at least the requested 2.5 seconds, avoid social-platform controls and use metrics from the footage.
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. Start with a five-second filter-to-result recording, then add graphics outside the phone.
Production approach: The stored request demands actual simulator recordings rather than fabricated UI. The post says music was handled with ElevenLabs. Confirm simulator access first; otherwise record and supply the clips yourself.
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.
Keep each feature visible for at least the requested 2.5 seconds, avoid social-platform controls and use metrics from the footage.
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.

Revise the film and fix problems

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

Replace the group scene with [my feature recording], preserving action order and at least 2.5 seconds per feature. Move titles away from platform controls and bottom overlays.

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.

• The demo lacks real use: record the action and result rather than faking them with an animated button.
• Platform controls cover text: preview with the platform overlay and adjust title placement.

Creator source and reproduction limits

The post mentions Opus 5.5, Motoseyir and a separate music tool. The stored detailed request emphasizes real recordings, reading time and safe placement. 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.