Flora Menstrual Calendar App Ad

Make a similar video

The vertical Flora film uses pink gradients and phone screens showing daily logs, a calendar, music selection and a download action. Interface assets explain the features while copy highlights the current scene.

Your goal: Make a vertical app ad from existing screenshots and recordings, showing three real usage scenes. 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 specifies JavaScript, Playwright and FFmpeg with videos and screenshots from an ads folder. Ask AI for a browser preview plus scripts for frame capture, encoding and audio assembly.

Prepare your assets

• Phone screenshots and short recordings for three features, using a demo account.
• App icon, brand colors, store link and audience language.
• Feature descriptions and accurate data-handling statements.

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
Daily logging	Your first core action
Cycle calendar	Your second core feature
Music selection	Your third supporting feature
Pink palette and App Store action	Your palette and actual download action

A habit app can show logging, statistics and reminders; a notes app can show creation, organization and search. Supply actual footage for each action instead of changing only the app name.

Match screenshots and recordings to the same feature. Use confirmed health-feature wording rather than turning a calendar display into a diagnosis or prediction promise.

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: one user need.
2. 4–10s: the first real feature action.
3. 10–16s: the second feature and result.
4. 16–22s: the third feature.
5. 22–26s: icon 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 vertical app ad from existing screenshots and recordings, showing three real usage scenes.
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.
Match screenshots and recordings to the same feature. Use confirmed health-feature wording rather than turning a calendar display into a diagnosis or prediction promise.
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. Place one actual recording in a phone frame with one heading; ensure the frame does not obscure the action.
Production approach: The stored request specifies JavaScript, Playwright and FFmpeg with videos and screenshots from an ads folder. Ask AI for a browser preview plus scripts for frame capture, encoding and audio assembly.
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.
Match screenshots and recordings to the same feature. Use confirmed health-feature wording rather than turning a calendar display into a diagnosis or prediction promise.
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 only the calendar scene with [my feature recording], adjusting its crop without distorting proportions. Use [heading] and keep captions clear of bottom buttons.

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 phone looks static: use footage including the action and result, trimming idle time.
• Export has no audio: check the audio assembly step; browser playback does not prove the MP4 contains audio.

Creator source and reproduction limits

The post says videos and photos were supplied to Opus 5.5 in a folder and the prompt was in a comment. The page retains the collected Portuguese request and translation, without capture-script source. 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.