shipping-and-launch

Validates Android releases with pre-launch checklists, staged rollouts, and rollback plans.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill shipping-and-launch-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/shipping-and-launch
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill shipping-and-launch-22teikk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping an Android app is risky because an installed APK or AAB cannot be recalled, so a bad release reaches users permanently. This Skill enforces a rigorous pre-launch checklist, staged rollout plan, and remote kill-switch strategy so releases to Google Play or Firebase App Distribution happen with controlled risk. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality, Proguard/R8, security and permissions, Room migrations, accessibility, and Play Console release configuration. - Two-Tier Ship Verdict: Distinguishes GO (production) from GO (demo/portfolio) by enumerating production blockers such as untested acceptance criteria or missing Room migrations. - Staged Rollout & Monitoring: Defines 1% to 100% rollout stages with Crashlytics, ANR, and rendering thresholds, plus Remote Config feature flags as a kill-switch. - Use Case: Before pushing a new version with a Room schema change to the Play Store, run the checklist to confirm migrations are tested, then roll out at 5% while monitoring Crashlytics before advancing. ## Quick Start Use the shipping-and-launch skill to run the pre-launch checklist and produce a ship verdict for my Android release.

Frequently Asked Questions about shipping-and-launch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare an Android app for Google Play release?▼

Run a pre-launch checklist covering release-mode builds, Proguard/R8 rules, permissions, Room migration tests, and accessibility. Then use a staged rollout starting at 1-5% of users while monitoring Crashlytics before advancing to 100%.

How to roll back a bad Android app release?▼

Mobile rollback relies on a Remote Config kill-switch to disable the faulty feature within minutes, halting the staged rollout in Play Console, and shipping a hotfix build with an incremented version code for expedited review.

What crash-free rate is safe for a staged rollout?▼

Advance the rollout when crash-free users exceed 99.9% and ANR rate stays below 0.47%. Hold between 99.5% and 99.9%, and halt the rollout if crash-free users drop below 99.5% or ANRs exceed 1.0%.

Why use feature flags with Firebase Remote Config?▼

Feature flags decouple APK deployment from feature activation, letting you ship code disabled, enable it for internal testers, roll out gradually to 5-100% of users, and disable it instantly if crashes appear.

What blocks an Android release from production approval?▼

Production blockers include Room databases with exportSchema=false and no migration path, acceptance criteria without behavioral tests, money stored as Double instead of Long minor-units, and no Room in-memory DAO tests.