Mobile Game Development for Hobbyists: Getting Your Game on US App Stores
Getting a mobile game onto the Apple App Store or Google Play Store involves more than finishing the code — it requires platform accounts, compliance reviews, asset specifications, and a working understanding of how each marketplace evaluates submissions. For hobbyist developers, the gap between "my game runs on my phone" and "my game is publicly available" is real but absolutely crossable. This page walks through the definitions, mechanics, typical scenarios, and decision points that shape that journey.
Definition and scope
A hobbyist mobile game developer is someone building games outside of a commercial studio context — often solo, often self-funded, and often using consumer-tier development tools. The distribution targets are the two dominant US-facing storefronts: Apple's App Store and Google Play, which together account for the overwhelming share of mobile game downloads in the United States (Sensor Tower tracks these distributions annually, though figures shift year to year).
Publishing on these platforms means entering formal legal and technical relationships with Apple and Google as a registered developer. Both platforms require acceptance of their developer agreements, which are substantive documents — Apple's App Store Review Guidelines run across dozens of sections covering content, safety, performance, legal, and business requirements. Neither agreement is boilerplate that can be skimmed.
The scope of mobile game development and publishing as a discipline includes game creation, platform compliance, metadata preparation, and ongoing maintenance post-launch. For hobbyists, "scope" also means being honest about what a single developer can reasonably sustain.
How it works
Both Apple and Google operate developer programs with annual or one-time fees attached.
-
Apple Developer Program — costs $99 USD per year (Apple Developer). This grants access to App Store Connect, TestFlight beta distribution, and submission tools. All iOS and iPadOS apps, including games, must be submitted through Xcode and reviewed by Apple's human review team before public release.
-
Google Play Console — costs a one-time $25 USD registration fee (Google Play Console Help). Android games are submitted as APK or AAB files. Google's review process is largely automated initially, with human review triggered by policy flags.
-
Submission preparation — both platforms require a privacy policy URL (non-negotiable if the app collects any data), screenshots in precise pixel dimensions, an app icon, a content rating (obtained through each platform's questionnaire), and a complete metadata package including title, description, and category.
-
Review and rejection cycles — Apple's median review time has historically ranged from 24 to 48 hours for most submissions, though appeals extend that timeline. Google's initial processing is often faster, but policy violations discovered post-launch can result in removal.
The underlying technical path runs through a game engine. Unity, for instance, supports export builds for both iOS and Android from a single project, which is why it dominates the hobbyist mobile space. Godot, another free and open-source option, similarly supports both targets. The engine handles the compilation to platform-native formats; the developer handles everything from signing certificates to store provider copy.
Understanding how this fits into the broader creative process — from initial concept through production — is well-grounded in the conceptual overview of how recreation works, which situates game-making within hobbyist practice generally.
Common scenarios
The first-time submitter with a puzzle game. This is the most common hobbyist scenario. A developer builds a simple tile-matching or logic puzzle game, usually in Unity or Godot, and attempts a first submission to both stores simultaneously. Common friction points: missing privacy policy, incorrect icon dimensions (Apple requires a 1024×1024 px icon without rounded corners or transparency), and content rating miscalculation.
The game that gets rejected for intellectual property. Apple Guideline 5.2 addresses IP ownership explicitly. A game using unlicensed character likenesses, trademarked logos as decorative elements, or music ripped from commercial sources will be rejected. This catches a meaningful portion of first-time hobbyist submissions.
The free-to-play hobbyist. Some hobbyists build free games with no monetization whatsoever. Both platforms accept these without issue, though Apple still requires a privacy policy if any analytics SDK is included — and nearly every major Unity build includes Firebase or Unity Analytics by default.
The paid game. Charging even $0.99 introduces tax form requirements. Apple requires completion of banking and tax information in App Store Connect before a paid app can go live. This involves US tax form W-9 (for US-based developers) or W-8BEN (for non-US developers) submitted through Apple's agreements portal.
Decision boundaries
The central decision a hobbyist faces is iOS-first, Android-first, or simultaneous. Android's lower barrier to entry (no Mac required, cheaper registration, faster initial review) makes it attractive for first launches. iOS reaches a US audience that, by multiple platform revenue analyses, spends more per user on average — but the $99 annual fee and mandatory Mac hardware for builds raise the floor.
A second decision boundary: free vs. paid vs. in-app purchases. Each choice carries different review scrutiny and different technical requirements. In-app purchases on iOS require implementation of Apple's StoreKit framework; on Android, Google Play Billing is required. These are not trivial integrations for a solo hobbyist.
Third: solo vs. published under a studio name. Both Apple and Google allow individuals to register under a personal name or a business name. A registered LLC or DBA changes the tax documentation required and may affect how the developer name appears on store providers — a minor but visible distinction that some hobbyists care about for aesthetic reasons.
The broader context of game publishing and distribution — including how storefronts compare, how platform relationships evolve, and how discoverability differs — sits underneath all of these choices. The video game development authority index connects these topic areas for reference as any given project develops.