For over a decade, I built and released apps almost exclusively for iOS. Rork changed that.
When Rork started generating cross-platform code automatically, there was no longer a compelling reason to skip Android. So I expanded one of my wallpaper apps — part of a catalog that has accumulated over 50 million cumulative downloads since 2014 — to Google Play.
What surprised me wasn't the technical side. It was the fundamentally different philosophy behind how each platform handles discoverability.
The Review Was Fast — But That Doesn't Mean You're Done
The first surprise was speed. App Store reviews typically take 24–72 hours. My Rork-built APK went from submission to "Published" on Google Play in a matter of hours.
That felt too easy. And in a way, it was.
Google Play's model is different: it publishes quickly but runs continuous policy checks after launch. Apps can be suspended post-publication if issues are detected — especially around ad configuration or permission declarations. Having managed a portfolio of apps through multiple policy cycles, I've learned that "passed review" on Google Play means "the initial check passed," not "you're safe indefinitely."
Rork generates solid Expo-based code, but I'd recommend manually auditing your AdMob configuration and permissions declarations before shipping. For ATT permission issues specifically, fixing ATT permission not showing covers the most common pitfalls.
Search Algorithms Are Fundamentally Different
On the App Store, the title and keyword field (100 characters) are the primary factors influencing search. The description text plays almost no role in keyword indexing.
Google Play is the opposite. The long description (up to 4,000 characters) is fully indexed for search — much like a web page. Keywords embedded naturally throughout the description influence where your app appears.
App Store ASO priority:
Title (30 chars) > Keyword field (100 chars) > Subtitle (30 chars)
Google Play ASO priority:
Title (30 chars) > Short description (80 chars) > Long description (4,000 chars, fully indexed)When I rewrote my wallpaper app's long description — keeping the text natural but including target keywords 3–5 times — organic search traffic increased noticeably within two weeks.
If you're used to App Store, you might think the description exists mainly to persuade users. On Google Play, it needs to persuade users and signal relevance to the search algorithm. For App Store ASO fundamentals, Rork ASO beginner guide 2026 is a good starting point.
Short Description: A Field App Store Doesn't Have
Google Play has a "Short Description" field — 80 characters displayed when the listing is collapsed. App Store has no equivalent.
This field is indexed for search and visible before users tap "read more." Despite its importance, it's one of the most neglected fields in indie developer store listings.
My approach when writing Short Descriptions:
- Include 1–2 keywords your target users are likely to search
- Communicate the core value in a single thought
- Rewrite it several times until both the spirit and the character count feel right
For a wallpaper app: "Beautiful daily wallpapers that make your phone screen feel personal" — it contains the keyword "wallpaper" while communicating value clearly.
Improving your Short Description takes maybe 30 minutes. The impact on ASO is disproportionate to the effort — which is exactly why it's worth prioritizing.
Feature Graphic Is Required
App Store has screenshots and preview videos. Google Play has those too, but it also requires a Feature Graphic: a 1024×500 banner image.
This banner is displayed prominently when your app is featured on Google Play. Without it, your app won't be considered for featuring at all.
The first time I released on Android, I discovered the Feature Graphic requirement after the fact and had to add it retroactively. Now I create it alongside the screenshots as part of the pre-launch checklist. Canva or similar tools make it a 30-minute task — too easy to skip, and too consequential to ignore.
Rating Distribution Matters Differently
Both platforms factor user ratings into search rankings. But Google Play appears to weight the proportion of 5-star ratings more heavily than the raw average alone.
Across several apps, I've observed that a 4.2 average with a high percentage of 5-star ratings tends to outperform a 3.8 average with similar download numbers in search results.
The practical implication: when and how you prompt for reviews matters. Trigger the review request at the moment of peak delight — not on first launch, but after the user has genuinely experienced your app's core value.
import * as StoreReview from 'expo-store-review';
// Call this after the user has experienced your app's core value
// e.g., after saving 5 favorites, completing a key action, etc.
const requestReview = async () => {
const isAvailable = await StoreReview.isAvailableAsync();
if (isAvailable) {
await StoreReview.requestReview();
}
};requestReview() works for both iOS and Android, and integrates cleanly into Rork-generated code.
iOS and Android Require Separate Store Strategies
Rork dramatically reduces the technical effort of building for both platforms. But store strategy is a different matter. The discovery mechanisms are different enough that each listing deserves independent attention.
After more than a decade of indie development, the lesson I keep returning to is that building well extends to every surface a user encounters — including the store listing. The same care that goes into the code should go into the Short Description, the Feature Graphic, and the review prompt timing.
Start with the Short Description. In 80 characters, you have more leverage than it might seem. For Android-specific subscription implementation, Google Play Billing Android subscription guide covers the billing integration side.