5 exercises — Practice app store vocabulary in English: App Store Connect, TestFlight, ASO, Google Play Console, release tracks, Android Vitals, and phased releases.
Core app store vocabulary clusters
App Store Connect: App Review, TestFlight, phased release, metadata, screenshots, app preview, promotional text
An iOS developer explains the App Store review process to a PM: "Every new version goes through App Review before users can download it. Standard review time is 24-48 hours. Rejections happen for guideline violations: missing privacy disclosures, broken functionality in review environment, inappropriate content, or payments bypassing in-app purchase. TestFlight is Apple's beta distribution platform — you can distribute to up to 10,000 external testers without App Review for each build (just an initial review). Phased release rolls out an approved version to 1%, 2%, 5%, 10%, 20%, 50%, 100% of users over 7 days." What is phased release on the App Store and what is its primary purpose?
Phased release: automatic rollout schedule — 1%, 2%, 5%, 10%, 20%, 50%, 100% over 7 days. Users receive the update through normal App Store updates; you cannot target specific users. Benefit: catch issues with a small fraction of users before 100% are affected. Halt rollout: pause the phased release if metrics degrade (crash rate spikes, negative reviews). Resume when fixed. App Store Connect vocabulary: App Review: Apple's manual review of each new app or app update. Checks compliance with App Store guidelines. TestFlight: beta testing platform. Internal testing: up to 100 members of your App Store Connect team, no review. External testing: up to 10,000 testers via email or public link; requires initial review. Expedited review: request faster review for critical bug fixes (only granted occasionally). Rejection: the build fails review. Common reasons: crashes during review, missing privacy policy, payments not using IAP, misleading metadata. Guideline 3.1.1: digital goods and services must use IAP. Common source of rejections. App Store Connect API: automate submissions, manage metadata, query sales data programmatically. In conversation: 'We always use phased release for major versions. We catch 90% of issues within the first 1% rollout — before they affect most of our users.'
2 / 5
A mobile developer explains ASO to a marketing colleague: "ASO — App Store Optimisation — is SEO for app stores. On iOS: the title (30 chars), subtitle (30 chars), and keyword field (100 chars) determine search ranking — no keyword repetition between them. On Android: the title (30 chars) and long description (4,000 chars) are indexed. Conversion rate is how many users download after viewing your listing. Screenshots and app preview video are the biggest conversion drivers. Ratings strongly influence both search ranking and conversion." Why are screenshots considered the most important ASO element for conversion?
Conversion rate: the percentage of listing page views that result in a download. ASO goal: maximise both impressions (search ranking) and conversion (listing quality). Screenshots: the first visual content users see. On iOS: up to 10 per device size. Best practices: lead with the strongest value proposition, use lifestyle/in-app screenshots, add minimal text overlay, test with different creative. App Preview: a 15-30 second video showing real app footage (not promotional). Autoplays on iOS search results. Can significantly increase conversion. App Store listing vocabulary: Title: primary ranking signal + first text users read. 30 characters. Subtitle (iOS): secondary description below title. 30 characters. Indexed. Promotional text (iOS): 170 characters. Not indexed. Can be changed without a new version. Keyword field (iOS): 100 characters of search keywords. Not visible to users. Not indexed separately — searched combined with title/subtitle. Long description (Android): up to 4,000 characters. Indexed for search. Short description (Android): 80 characters. Appears on the listing and in search. Rating: star rating prominently displayed. Below 4.0 significantly reduces conversion. Review velocity: rate of new reviews. Recent reviews weighted more heavily. In conversation: 'We doubled our App Store conversion rate by redesigning screenshots with a clear value proposition in the first frame. No other change came close.'
3 / 5
An Android developer presents Google Play Console metrics at a sprint review: "Android Vitals shows quality metrics that affect our Play Store ranking: crash rate (should be under 1.09% — Play's bad behaviour threshold), ANR rate (should be under 0.47%), and excessive wakeups. If we cross these thresholds, Play reduces our visibility in search and browse. The pre-launch report runs our APK on real devices in Firebase Test Lab before we release — it catches crashes, accessibility issues, and security vulnerabilities automatically." What is an ANR in Android, and why does Google use it as an app quality signal?
ANR (App Not Responding): occurs when the Android main thread is blocked. Thresholds: 5 seconds during an input event (user touch), 10 seconds during a BroadcastReceiver. Android shows a dialog: "[App] isn't responding. Do you want to close it?" Common causes: synchronous disk/network I/O on main thread, deadlock, long-running computations on UI thread. Fix: move work to background threads (coroutines, WorkManager). Android Vitals vocabulary: Core Vitals: crash rate, ANR rate, excessive background battery usage. Bad behaviour threshold: Play's threshold above which your app is flagged. Crash rate: 1.09% of daily sessions. ANR rate: 0.47% of daily sessions. User-perceived crash rate: crashes per user (not per session). ANR rate: ANRs per user per day. Google Play Console vocabulary: Release tracks: Internal testing (100 users, immediate), Alpha (closed testing), Beta (open testing), Production. Each track can have staged rollout. Staged rollout: equivalent to phased release — roll out to X% of users. Pre-launch report: Firebase Test Lab runs the APK on real devices before you release. Reports: crashes, ANRs, accessibility issues, security vulnerabilities (hardcoded secrets). App bundle (.aab): modern upload format. Play generates optimised APKs per device. Smaller download sizes. Required for new apps. In conversation: 'Android Vitals directly affects store visibility. We monitor crash and ANR rates daily — any spike gets investigated before it hits the bad behaviour threshold.'
4 / 5
A mobile team lead explains release tracks to a QA engineer: "Google Play has four release tracks. Internal testing is for your team — up to 100 testers, almost instant availability. Closed testing (alpha) is for a specific group — invite by email or Google Groups. Open testing (beta) is public — anyone can join. Production is the live release. We typically: internal (daily builds for team QA), closed beta (wider testing before release), then production with a 10% staged rollout. iOS uses TestFlight for the same purpose — internal and external testing before App Store release." Why would you use internal testing versus a closed beta track in Google Play?
Internal testing track: up to 100 testers. Builds available within minutes of upload. No review required. Purpose: developer testing, QA team validation, crash hunting on real devices. Closed testing (Alpha): specific group via email list or Google Group. Broader testing — selected external testers, partners, beta users. Not publicly accessible. Must go through review. Open testing (Beta): public — anyone can opt in via Play Store listing. Good for community beta testing and collecting reviews before production. Release track vocabulary: Staged rollout: release to a percentage of users in each track. Can pause, increase, or halt. Rollout halt: emergency stop — no new users receive the update, but users already on it stay updated. Emergency fix: critical bug fix — increase rollout percentage rapidly after verification. Release notes: what's new text shown in the Play Store for each update. Per-language. Managed publishing: hold approved changes until you manually publish — lets you coordinate with marketing. iOS equivalent vocabulary: TestFlight internal: App Store Connect team members. TestFlight external: up to 10,000 testers; requires initial review. Public link: shareable TestFlight link for open beta. In conversation: 'Our flow: internal (2-3 days), closed beta (one week), 10% production rollout (monitor 48h), full rollout. This pattern has saved us from releasing broken updates multiple times.'
5 / 5
A product manager explains app store rating strategy to an engineering team: "User ratings directly impact both search ranking and conversion. Apps with fewer than 50 ratings are invisible in search. Negative reviews cost us downloads. We use SKStoreRequestReview (iOS) and the Review API (Android) to prompt users at the right moment — after a positive interaction, not after an error or onboarding. We also monitor reviews daily and respond within 24 hours — especially negative ones. Responding to a negative review sometimes converts the reviewer to update their rating." What is a rating prompt and when should it be triggered?
SKStoreRequestReview (iOS) / In-App Review API (Android): native OS dialog prompting for a star rating. Rules: iOS — can show at most 3 times per year. Android — quota-based, Google controls frequency. Custom prompts that say "rate us" and redirect to the store are allowed but rate at lower conversion. Timing best practices: Do trigger after: successful task completion (order placed, document exported, level completed), Nth session (session 3-5 shows retention), after feature discovery. Don't trigger after: onboarding (user hasn't experienced value yet), after an error or crash, during a task flow, first launch. App store review vocabulary: Review response: public reply to user reviews. Visible on the listing. Good responses show responsiveness and can get users to update their rating. Developer reply: Apple/Google term for review response. Rating prompt impression: how many times the dialog was shown. Rating prompt conversion: % of impressions that result in a rating submission. Review velocity: new reviews per time period. Bayesian rating: both Apple and Google blend your rating with a prior — new apps start near the average. Remove rating: users can delete their rating; a good response sometimes prompts this for negative reviews. In conversation: 'We A/B tested rating prompt timing. Triggering after the user successfully exported a file gave us a 4.7 average rating. Triggering after onboarding gave us 3.9.'