A first promo video on X (Twitter) for a side project

You do not need a studio. You need one clear minute (or less) that answers: what is this, who is it for, and what should I do next? This note is for me and for anyone shipping something small, like Cosa Cuciniamo, a recipe and meal-planning app I am building in the open.

X (Twitter) rewards native video: it loops in the feed, autoplays muted, and works best when the story is obvious without sound at first glance.

What “effective” means here

Effective does not mean viral. It means:

• A stranger understands the problem in the first three seconds.
• They see one concrete action in the product (save a recipe, plan a week, build a shopping list).
• They know where to go (your URL in the post, and ideally on screen once).

If one person bookmarks the link or replies with a question, the video did its job.

Format that fits X

These are guidelines, not rules carved in stone:

• Length: roughly 20 to 45 seconds for a first promo. Short enough to rewatch, long enough to show one flow.
• Aspect ratio: 9:16 (vertical) or 1:1 (square). Vertical tends to feel more “native” on the phone.
• Safe zones: Leave a little margin at the top and bottom so UI and captions are not clipped on different devices.
• Captions: Assume sound off. Burn in large, readable subtitles or use X’s caption workflow if you use it.

A simple script you can steal

Use this structure. Replace the middle with one real screen recording from your app.

1. Hook (2 to 3 seconds): Name the pain in plain language.
   Example: “Tired of deciding what to cook every night?”
2. Product (one sentence): What it is.
   Example: “Cosa Cuciniamo helps you save recipes, plan the week, and shop from one list.”
3. Demo (15 to 25 seconds): One path only. For example: open a recipe, add it to the week, show the list updating. No settings tour.
4. CTA (3 to 5 seconds): Domain on screen + spoken.
   Example: “Try it at cosacuciniamo.com.”

How to record without overthinking

• Phone + screen recording: Record the app on your device, or mirror to a computer if that is easier. Keep gestures slow and deliberate.
• Voice: Quiet room, phone mic at arm’s length, or cheap USB mic. Normalize volume so it is not quieter than other videos in the feed.
• Face optional: A short intro face cam can help trust, but it is not required for v1.

Editing (minimum viable)

Use whatever you already tolerate (CapCut, DaVinci Resolve, iMovie, etc.):

• Trim dead air at the start.
• Add chapter-style captions (not a wall of text).
• One lower-third or end card with the URL.

Export at a resolution X accepts without heavy compression artifacts; when in doubt, slightly higher bitrate beats a tiny blurry file.

The post around the video

The video is half the work. The post copy should repeat the CTA and invite a specific reaction:

• Pin a line with the link: https://cosacuciniamo.com
• One sentence on who it is for (home cooks who want a lighter weekly rhythm, language learners practicing Italian in the kitchen, etc., whatever is true for you).
• Optional: ask one question (“What would you want this to do next?”) to seed replies.

Avoid stuffing hashtags. One or two relevant tags, or none, often look cleaner on X.

What to avoid on the first try

• Feature dumps: Ten screens in forty seconds helps nobody remember anything.
• Inside baseball: Framework names, infra, or repo structure belong in a dev post, not in a user-facing promo.
• Ambiguous CTA: “Check it out” is weak. “Plan your week in under a minute” is stronger if it matches the demo.

After you publish

Watch retention if X gives you analytics, but do not obsess on day one. More useful:

• Did people ask the same misunderstanding twice? Fix the hook or the first screen in the next cut.
• Did anyone sign up or share? Note what was different about that post (time of day, caption angle).

The goal of the first video is not to max impressions. It is to exist, to clarify the story, and to give you a link you can reuse in bios, threads, and future updates. Ship it, then improve.