◉RORK LABJP
●GPT-6.1 SOL — Added to Rork's model menu (09-29) with Low, Medium and High effort; included on Pro and Max●SONNET 5.5 — Claude Sonnet 5.5 is selectable: strong at UI design and faster than Sonnet 5 (09-28)●SDK 58 — Expo SDK 58 is out of beta as of 10/15 (beta since 09/15). Check your dependencies before upgrading●WIDGET — A write-up traces an iOS widget that renders black only in production builds●OBSERVE — EAS Observe now records native crashes too (SDK 57.0.21 or later, 10/07)●NEW — My App Open Ad Only Showed When the App…●GPT-6.1 SOL — Added to Rork's model menu (09-29) with Low, Medium and High effort; included on Pro and Max●SONNET 5.5 — Claude Sonnet 5.5 is selectable: strong at UI design and faster than Sonnet 5 (09-28)●SDK 58 — Expo SDK 58 is out of beta as of 10/15 (beta since 09/15). Check your dependencies before upgrading●WIDGET — A write-up traces an iOS widget that renders black only in production builds●OBSERVE — EAS Observe now records native crashes too (SDK 57.0.21 or later, 10/07)●NEW — My App Open Ad Only Showed When the App…
← Back to Blog

Publishing Your Rork App on Google Play — A Practical Guide for Android

RorkGoogle PlayAndroidApp PublishingReact Native

Your Rork App Deserves an Android Audience Too

There's already plenty of guidance on getting a Rork app onto the App Store. But if you stop there, you're leaving a massive audience on the table. Android commands roughly 70% of the global smartphone market, with especially strong dominance in Asia, South America, and Africa.

Because Rork is built on React Native and Expo, the same project that powers your iOS app can produce an Android build with minimal extra effort. Here's how to take that build all the way to a published Google Play listing.

Step 1: Create a Google Play Developer Account

Head to the Google Play Console and register as a developer. Unlike Apple's annual $99 fee, Google charges a one-time $25 registration fee — a much lower barrier to entry for indie developers testing the waters.

You'll need:

  • A Google account
  • A credit or debit card for the $25 fee
  • Contact information (including a public-facing email address)

One important wrinkle: since 2024, Google requires new developer accounts to complete a closed testing milestone before publishing to production. Specifically, you need 20 testers who opt in and use your app for at least 14 consecutive days. There's no shortcut around this, so start your closed testing track early.

Step 2: Build an AAB with EAS Build

Rork projects run on Expo, which means you can use EAS Build (Expo Application Services) to generate an Android App Bundle (AAB) in the cloud.

Either use Rork's built-in terminal or export your project locally and run:

npx eas-cli build --platform android --profile production

Once the build completes, download the .aab file from your EAS dashboard. Note that Google Play has required AAB format (not APK) for all new apps since 2021.

Step 3: Prepare Your Store Listing

With your app created in Google Play Console, fill out the store listing. Here's what you'll need:

Text assets:

  • App name (up to 30 characters)
  • Short description (up to 80 characters)
  • Full description (up to 4,000 characters)

Graphic assets:

  • App icon (512 × 512 px)
  • Feature graphic (1024 × 500 px)
  • Screenshots (minimum 2, recommended 4–8)

Google Play gives you more flexibility than the App Store when it comes to listing copy. You can use Unicode characters and emoji in your descriptions to improve visual appeal and scannability.

Step 4: Content Rating and Data Safety

Google Play requires you to complete an IARC (International Age Rating Coalition) questionnaire. It's a series of straightforward questions about your app's content — violence, language, user-generated content, and so on. The whole process takes about five minutes, and you'll receive an automatic age rating.

You'll also need to fill out the Data Safety section. Be thorough and honest about the data your app collects and shares. If your Rork app connects to Supabase, Firebase, or any third-party analytics, make sure to account for the data those services handle on your behalf.

Step 5: Release Through Test Tracks

Resist the urge to publish straight to production. Google Play offers three testing tiers:

  • Internal testing: Up to 100 testers, no review required, instant distribution
  • Closed testing: Invite-only via email lists or Google Groups, light review process
  • Open testing: Anyone can join, ideal for a final check before launch

Remember the 20-tester requirement from Step 1? That can only be fulfilled through closed testing — internal testing alone won't count. Getting your closed test up and running early is the single most important thing you can do to avoid delays.

How Google Play Differs from the App Store

If you've already been through Apple's review process, here are the key differences to expect:

Review speed: Google Play reviews typically take a few hours to three days. That's generally faster than Apple's one-to-seven-day window, though first-time submissions from new accounts can take longer.

Enforcement style: Google tends to enforce policies reactively. Apps can go live and then get flagged or removed after the fact. Read the Developer Program Policies carefully before submitting — don't assume that passing review means you're in the clear forever.

Update agility: Once your app is live, updates roll out quickly after review. Google also offers staged rollouts, letting you release an update to a small percentage of users first. This is a great way to catch bugs before they affect your entire user base.

Rork and Google Play Are a Natural Fit

Rork's React Native / Expo architecture plays well with Android builds. EAS Build handles AAB generation automatically, so you rarely need to touch Android-specific build configurations like Gradle files or signing keys.

For solo developers, shipping on both iOS and Android means more than doubling your potential reach. If you've already published on the App Store, extending to Google Play is a logical next step — and with Rork, it requires almost no additional code. Your app is ready for both platforms from day one.