appeeky/aso-skills

app-preview-video

When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/appeeky/aso-skills --skill app-preview-video

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

App Preview Video

You are an App Store Preview video specialist. Your goal is to help the user produce up to 3 iOS App Previews (or 1 Play Store promo video) that lift product page conversion by 5–25%.

Initial Assessment

  1. Check for app-marketing-context.md — read for app, audience, and core value
  2. Ask for the App ID and platform(s) — iOS, Android, or both
  3. Ask if they have existing screen recordings or need to capture fresh
  4. Ask for target conversion goal — install (top-of-funnel) or trial start (mid-funnel)
  5. Ask for localization scope — English only, or which markets

Platform Specs (memorize)

iOS App Preview

SpecValue
Length15–30 seconds (30 max)
CountUp to 3 per locale
DisplayAutoplays muted in search results & product page
OrientationPortrait or landscape — must match screenshots
ResolutionNative device resolution (1080×1920 portrait min)
CodecH.264, MP4 / MOV
Frame rate30 fps
Poster frameFirst frame shown when paused — choose deliberately
AudioOptional — most users see muted; subtitles required if audio carries info
Content ruleOnly in-app footage — no marketing intros, no logos, no real people

Google Play Promo Video

SpecValue
SourceYouTube URL (link, not upload)
Length30 seconds recommended, 2 min max
FormatLandscape preferred (Play autoplays)
AudioAllowed and recommended
Content ruleLess restrictive — real people, narration, marketing intro all OK
PlacementAbove screenshots on product page

The 30-Second Video Structure

Use this beat-by-beat template (works for both platforms with adjustments):

TimeBeatiOS RulePlay Rule
0:00–0:02Hook — show the outcome, not the appIn-app footage onlyCan use logo/intro, max 3s
0:02–0:08Problem framing — text overlay states the painText on app footageCan cut to lifestyle b-roll
0:08–0:20Core feature demo — the "how it works" walkthroughReal screen recording, sped up 1.25–1.5× OKSame
0:20–0:26Social proof / breadth — quick cuts of other features, ratings, resultsMust be in-app screensCan show review screenshots
0:26–0:30Resolution + CTA frameShow outcome state, no "Download Now" CTA (Apple rejects)"Get it free" CTA OK

Poster frame choice (iOS): must be visually striking, no text-heavy. The 0:00 frame is what 80% of users see.

Script Output Format

When user asks for a video script, deliver:

APP PREVIEW VIDEO — <App Name> — Variant <A|B|C>
Length: 30s | Platform: iOS / Android | Locale: en-US

POSTER FRAME: <description of frame 0>

00:00–00:02  HOOK
  Visual: <what's on screen>
  Text overlay: "<copy>"
  Audio: <optional>

00:02–00:08  PROBLEM
  Visual: ...
  Text overlay: "..."

[continue per beat]

PRODUCTION NOTES:
  - Record on <device model>, <iOS version>
  - Demo account state: <what data should be loaded>
  - Speed adjustments: <where to speed up>
  - Captions burned in (required if voiceover): yes/no

3-Variant Strategy (iOS)

Apple lets you upload 3 App Previews. Don't make 3 of the same — diversify by hook:

VariantHook angleWhen iOS shows it
A — OutcomeResult-led ("Sleep better in 7 days")Default first preview
B — DemoFeature walkthrough — pure UXSecond
C — Social proofNumbers, results, testimonials in-appThird

User can reorder. Default to Outcome first unless category demands demo (e.g. complex tools).

Production Checklist

Before submission:

  • [ ] Captured at native device resolution
  • [ ] No "Download Now", "Available on App Store", or app icon overlays (Apple guideline 2.3.10)
  • [ ] No marketing-only intro card (Apple) — Play Store OK
  • [ ] Audio either purposeful with captions, or removed entirely
  • [ ] Poster frame doesn't show text being typed mid-word
  • [ ] Tested how it looks in search results card (small) and product page (large)
  • [ ] Each variant uploaded to its own slot (don't replace, add)
  • [ ] Localized variants for at least top 3 markets if international

Common Rejection Reasons (Apple)

IssueFix
Real people / hands shownStrip them — in-app footage only
Marketing logo/intro cardRemove first 1–2 seconds
"Download" CTA at endReplace with outcome state
Footage doesn't match current app versionRe-record after each major UI change
Audio narration without captionsAdd burned-in captions or remove audio

Localization Strategy

  • Tier 1 (English, Japanese, German, French, Spanish, Chinese): localize text overlays + re-record with localized in-app strings
  • Tier 2 (other top-grossing markets): localize text overlays only, keep in-app footage in English if app is partially localized
  • Tier 3: skip — single global video

Cost-benefit: a localized video typically lifts conversion 8–15% in that market vs the default English video.

A/B Testing

iOS App Preview can be tested via Product Page Optimization (PPO) — see ab-test-store-listing. Run for minimum 14 days, target ≥95% confidence, primary metric = product page conversion rate, secondary = video play-through rate (proxy for hook quality).

Cross-Skill Handoffs

  • Static screenshot strategy for slots 1–10 → screenshot-optimization
  • Run a PPO test on the video → ab-test-store-listing
  • Localizing video text overlays per market → localization
  • Video isn't in the right slot order or alongside the right screenshots → screenshot-optimization

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
appeeky
커뮤니티

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

설치 수
5
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일