Publishing a Mobile App: App Store, Google Play, ASO, Review Process, Fastlane
A finished app is not a published app. The App Store rejects around 40% of first submissions for various reasons, and some are not technical but political. Google Play is more automated, but it has its own pitfalls: an app can be published and removed 3 days later when an automated reviewer discovers something.
App Store: A Review You Cannot Rush
Apple Review typically takes 24–48 hours (the 2024 average is about 90% of apps reviewed within a day). Expedited review is a real option through App Store Connect for critical bugs, but not for the first submission.
Common rejection reasons that waste time:
Guideline 2.1 — App Completeness. Test account doesn't work, demo data doesn't load, some screens show empty states without explanations. The reviewer sees a broken app. The solution is simple: a filled test account with realistic data, Notes for Reviewer with step-by-step instructions for checking key scenarios.
Guideline 4.3 — Spam. The app looks like another app of yours or is too simple (a wrapper around a website). This is one of the most subjective reasons. If you have several similar apps for different countries—you need serious justification for the differences.
Guideline 5.1.1 — Data Collection and Storage. No Privacy Policy, Privacy Policy doesn't match actual data collection, or the privacy manifest (mandatory since May 2024) doesn't declare the APIs being used. Privacy Manifest—PrivacyInfo.xcprivacy file—is mandatory if using UserDefaults, FileTimestamp, DiskSpace, ActiveKeyboards, or any required reason APIs. Apple started rejecting without it in 2024.
Guideline 3.1.1 — Business — Payments. External payment links where IAP should be. After the Epic vs Apple ruling in the US, Apple allowed external site links for Reader Apps, but the rules are complex and depend on app category.
A separate point—App Privacy Labels (nutrition labels). You must honestly declare what is collected, why, and whether linked to user. Errors here don't block publication immediately, but Apple may request corrections afterward.
Google Play: Automation and Hidden Surprises
Google Play is more automated, initial review often takes a few hours. But there are nuances.
Target SDK level—Google regularly raises requirements. In 2024, new apps must target Android 14 (API 34). Existing apps received notifications with mandatory update deadlines. If not updated—the app becomes unavailable to new users on new devices.
64-bit requirement—all apps with native libraries must have 64-bit versions. Flutter builds both by default, React Native with some native modules—doesn't. Check in advance.
Data Safety Form—the Android equivalent of Apple Privacy Labels, filled in Play Console. Unlike Apple, Google doesn't automatically check this with every release—but may request an audit.
Play Integrity API (SafetyNet replacement, which is deprecated)—for apps concerned with device integrity (banks, payment apps, games with anti-cheat). Requires a server to verify tokens.
ASO: App Store Optimization
ASO affects organic traffic—real downloads without ad spend.
Key ranking factors in App Store and Google Play:
App Name—the most significant factor. Keywords in the name work best. Limitation: App Store—30 characters, Google Play—50.
Keywords (App Store)—100 character field, App Store only, not displayed to users. No spaces after commas (saves characters), don't duplicate words from the name.
Description (Google Play indexes it, App Store doesn't)—first 80 characters visible without "more," the rest in a collapsible block.
Visual Assets—icon, screenshots, preview video. A/B testing of visuals through Product Page Optimization (App Store) and Store Listing Experiments (Google Play) really affects page conversion. The difference between a bad and good screenshot—15–30% conversion.
Rating and Reviews—the algorithm accounts for freshness, not just average. Active work with reviews (responses) signals an active app to the platform. SKStoreReviewRequest.requestReview() (iOS) and ReviewManager.requestReview() (Android)—request reviews at the right moment: after a positive event, not at first launch.
Fastlane: Automating Publication
Manual publication—certificates, provisioning profiles, build, upload to App Store Connect or Google Play Console—takes an hour and is easy to get wrong. Fastlane automates the entire pipeline.
Key lanes:
match—manages certificates and provisioning profiles through an encrypted Git repository. The entire team uses the same certificates, no "certificate expired on a developer machine" issues. fastlane match appstore—synchronize before building.
gym (build)—fastlane gym --scheme "AppName" --configuration Release --export_method app-store. Parameters are fixed in the repository via Gymfile.
deliver (upload to App Store)—uploads the binary, metadata, screenshots. Screenshots can be kept in the repository via fastlane snapshot (automatic generation via XCUITest).
supply—the Google Play equivalent of deliver, supports all tracks (internal, alpha, beta, production) with rollout parameter for gradual rollout.
Typical Fastfile:
lane :release_ios do
match(type: "appstore")
gym(scheme: "App")
deliver(submit_for_review: true, automatic_release: false)
end
lane :release_android do
gradle(task: "bundle", build_type: "Release")
supply(track: "production", rollout: "0.1")
end
CI/CD integration: Fastlane + GitHub Actions or Bitrise—standard stack. Environment variables for App Store Connect and Google Service Account API keys. Code is signed automatically on main merge.
Phased Rollout and Rollback
Google Play supports gradual rollout: rollout: "0.05"—5% of users get the update first. Monitor Crashlytics/Firebase Crashlytics, crash-free rate, ANR rate. If metrics deteriorate—stop rollout via Play Console without recalling the release.
App Store doesn't have gradual rollout for regular apps (Phased Release for app updates—7-day gradual rollout). For more flexible control, use feature flags (Firebase Remote Config, LaunchDarkly)—new functionality is disabled by default, enabled via config without a new release.
Timeframe for Publication Preparation
Preparing the first release: setting up accounts, certificates, metadata, screenshots, Privacy Policy—3–5 business days with all materials. Setting up Fastlane + CI/CD—2–3 days. App Store review—1–3 days. Total from ready app to publication—1–2 weeks.