appeeky/aso-skills

in-app-events

When the user wants to create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/appeeky/aso-skills --skill in-app-events

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

In-App Events

You help the user plan, write, and optimize App Store In-App Events — event cards that surface in search, the Today tab, and the product page, driving installs and re-engagement without paid media.

What In-App Events Are

In-App Events are time-limited content cards on the App Store. They appear:

  • Today tab (editorial + algorithmic)
  • Search results (alongside app results)
  • Your product page
  • Personalized recommendations (for lapsed users)

Key advantage: Existing users who haven't opened your app recently are notified of events. Non-users see them as discovery.

Event Types

TypeBest ForExample
ChallengeUser-generated competition"30-Day Streak Challenge"
CompetitionRanked or scored contest"Weekly High Score Leaderboard"
Live EventReal-time activity"Live Q&A with Experts"
Major UpdateSignificant new feature"Introducing AI Coach"
PremiereFirst-time content launch"New Series: Morning Routines"
Special EventSeasonal or themed moment"Holiday Collection Unlocked"

Event Card Specs

FieldLimitNotes
Event name30 charsAppears prominently — keyword-conscious
Short description50 charsBelow the name on cards
Long description120 charsShown in expanded event view
Event card image2160×1080px2:1 ratio, PNG/JPG, no text required
Badge—Chosen from the 6 type badges above
DurationUp to 31 daysStart and end time required

Up to 10 events can be live or scheduled at a time.

Planning Workflow

Step 1 — Event Idea Selection

  1. Check for app-marketing-context.md
  2. Evaluate event type based on app category:
App TypeBest Event Types
GamesChallenge, Competition, Major Update
FitnessChallenge, Live Event, Major Update
ProductivityMajor Update, Premiere
Social / CommunityLive Event, Challenge
Streaming / ContentPremiere, Special Event
UtilityMajor Update, Special Event
  1. Identify the primary goal:
  • Re-engagement → Use notification-triggering events (any type)
  • New user acquisition → Focus on Today tab visibility (Challenge or Competition)
  • Feature launch → Major Update type

Step 2 — Write Event Copy

Event name (30 chars) — rules:

  • Lead with the user benefit or action, not your app name
  • Include relevant keywords where natural
  • ✅ "30-Day Habit Challenge" | ❌ "AppName Challenge 2026"

Short description (50 chars):

  • Answer "what's in it for me?" in one line
  • ✅ "Build a streak and win exclusive rewards"

Long description (120 chars):

  • Expand on the short description: what, when, and why to join
  • ✅ "Join our 30-day challenge. Complete daily habits, hit your streak, and unlock your achievement badge."

Step 3 — Event Card Image

Spec: 2160×1080px, 2:1 ratio

Best practices:

  • No text needed (name/description appear as overlay) — but a short tagline is allowed
  • High contrast, bold visual that works at small thumbnail size
  • Show the outcome or reward, not just the app UI
  • Test thumbnail at 390×195px to verify legibility

Step 4 — Submit in App Store Connect

  1. App Store Connect → Your App → In-App Events → +
  2. Fill all required fields + upload image
  3. Submit for review (typically 24–48 hours)
  4. Schedule start/end times

Submit 3–5 days before the desired start date to account for review time.

Optimization Tips

Maximize Today Tab Placement

Apple's algorithm favors events that are:

  • Timely — tied to real-world moments (holidays, trends, app anniversaries)
  • High quality — polished images, complete descriptions
  • Engaging — event types that drive sessions (challenges > updates)
  • Consistent — apps that run regular events get better recurring placement

Run at least one event per month to maintain algorithmic eligibility.

Keyword Visibility in Search

Event names and short descriptions are indexed by the App Store search algorithm.

  • Include 1–2 target keywords in the event name naturally
  • The short description can reinforce secondary keywords
  • Use keyword-research skill to validate which terms to include

Re-engagement Notification

Users who have downloaded your app but haven't opened it recently receive a push notification for your event automatically — no opt-in required. This is the highest-value feature of In-App Events.

Make the event name the notification subject line — write it to be compelling as a standalone message.

Output Format

Event Brief

📅 Event: [Name — 30 chars]
   Type:  [Badge type]
   Dates: [Start] → [End]

Copy:
  Short:  [50 chars]
  Long:   [120 chars]

Image direction:
  Visual: [describe the scene/concept]
  Style:  [photography / illustration / abstract]
  Key element: [the reward, the action, the outcome]

Goals:
  Primary: [re-engagement / acquisition / feature launch]
  KPIs: [sessions spike, downloads, event page views]

Submit by: [date — 4 days before start]

Event Calendar (monthly)

Week 1:  [Event name] — [type] — [dates]
Week 2:  [No event / buffer]
Week 3:  [Event name] — [type] — [dates]
Week 4:  [Event name] — [type] — [dates]

Common Mistakes

MistakeFix
App name in event nameLead with the user benefit
Generic image (screenshot of UI)Show the reward/outcome visually
Events shorter than 7 daysMinimum 7 days for Today tab consideration
Submitting day-ofSubmit 4–5 days early for review
No recurring scheduleRun 1+ events/month for sustained placement

Related Skills

  • seasonal-aso — Align event timing with keyword seasonal peaks
  • screenshot-optimization — Apply same visual best practices to event images
  • app-store-featured — Events increase editorial feature eligibility
  • retention-optimization — Track re-engagement lift from events

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
appeeky
Communauté

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.

installations
5
GitHub Stars
2,2 k
Mis à jour
6 oct.
appeeky
Communauté

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.

installations
4
GitHub Stars
2,2 k
Mis à jour
6 oct.
appeeky
Communauté

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.

installations
4
GitHub Stars
2,2 k
Mis à jour
6 oct.
appeeky
Communauté

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

installations
4
GitHub Stars
2,2 k
Mis à jour
6 oct.