Launch day is quiet for most apps. The listing goes live and almost nobody finds it. A new app with no ratings, thin metadata and screenshots copied from the design file has very little to rank on.
App store optimisation (ASO, often spelt app store optimization) fixes that. It covers the text fields the stores read for search, the visuals that turn a listing view into an install, ratings, and the free testing tools each store offers. This guide is for Singapore businesses that have just launched an app or are about to. If you’re still building, our guide to the mobile app development process shows where ASO fits.
The short answer
- The two stores read different fields. On iOS, search draws on the app name, subtitle, 100-character keyword field and category. On Google Play there is no keyword field, so the title, short description and full description carry your keywords.
- Put the most valuable keyword in the app name on both stores, within the 30-character limit, and keep the brand name short.
- Your first three screenshots do most of the selling. They often show in search results before anyone opens your page.
- Ratings affect ranking and conversion. Use Apple’s and Google’s official in-app review prompts at a good moment, never behind a “Rate us” button.
- Test, don’t guess. Apple’s Product Page Optimization and Google Play’s store listing experiments let you A/B test icons and screenshots at no cost.
- For Singapore, localise for both stores. Apple lists English (U.K.) as the Singapore storefront’s default language and Simplified Chinese as the additional one.
- App quality is part of ASO. Google Play may reduce the visibility of apps with high crash or ANR rates.
How ranking works on the App Store vs Google Play
Both stores rank apps on two broad things: how well your listing text matches the search, and how users respond to your app (downloads, ratings, engagement). Apple says it directly on its App Store search page: results are based on “text relevance (matches for your app’s title, subtitle, keywords, and primary category), as well as user behavior (downloads, ratings and reviews, and more).”
The difference is in which text fields count. This is the part most first-time publishers get wrong.
| Field | Apple App Store | Google Play | Used for search? |
|---|---|---|---|
| App name / title | Up to 30 characters | Up to 30 characters | Yes, on both. The strongest text signal |
| Subtitle | Up to 30 characters, shown under the name | Not available | Yes (Apple) |
| Keyword field | 100 characters, comma-separated, hidden from users | Not available | Yes (Apple only) |
| Short description | Not available | Up to 80 characters | Yes (Play) |
| Promotional text | Up to 170 characters, editable any time | Not available | No. Apple says it “doesn’t affect your app’s search ranking” |
| Full description | No stated limit | Up to 4,000 characters | Play: yes. Apple: not in Apple’s list of search fields |
| Category | Primary and optional secondary | One category | Apple indexes the category |
| Ratings and reviews | Shown in search results | Shown in search results | Influence ranking and conversion on both |
Limits are taken from Apple’s product page guidance and Google’s store listing best practices, checked in November 2026.
So on iOS, write the description for people and spend your keyword effort on the name, subtitle and keyword field. On Google Play the full description does count for search, but Google warns against keyword lists, so mention your main terms naturally a few times.
Singapore splits fairly evenly between the platforms. StatCounter puts Android at 57.5% and iOS at 42.4% of mobile OS share in October 2026, so most local businesses need both listings in shape. Our comparison of native vs cross-platform apps covers how to build for both.
Step 1: Do keyword research for app stores
App store searches are short: “gym booking”, “bus arrival”, “receipt scanner”. Find the three to five phrases your users type and decide where each goes.
- Write ten phrases a customer would say, not your internal feature names. “Book a cleaner” beats “on-demand home services platform”.
- Use the stores’ autocomplete on a phone set to Singapore. The suggestions are real searches.
- Read the top five competitors’ names, subtitles and short descriptions. Words they all repeat are the category’s core terms.
- Check popularity. Apple Ads shows a popularity indicator for keywords when you build a campaign. Google Keyword Planner gives web demand as a rough proxy, and our guide to finding keywords for free lists more tools. Paid tools such as AppTweak, Appfigures and Sensor Tower estimate store volume by country.
- Score each phrase by relevance, popularity and competition. Pick one primary phrase for the app name and a few secondary ones.
| Keyword type | Example (gym class booking app) | Competition | Where to use it |
|---|---|---|---|
| Brand | “FitLoop” | Low | App name |
| Core category | “gym”, “fitness” | Very high | Name or subtitle if relevant, but hard to rank for early |
| Specific feature | “class booking”, “spin class” | Medium | Name, subtitle, short description |
| Local | “singapore”, “sg” | Low to medium | Keyword field (iOS), description (Play) |
| Long tail | “pilates timetable”, “hiit studio” | Low | Keyword field, full description |
New apps rarely rank for the broad category term in month one. Aim first for specific phrases where the top results are weak, then widen as ratings and downloads build.
Step 2: Write the metadata for each store
iOS: name, subtitle and the keyword field
Apple’s search guidance sets a few rules for the keyword field:
- Separate terms with commas and no spaces. Spaces are fine inside a phrase (“real estate”).
- Don’t repeat words already in your app name, subtitle or category. Apple already counts them.
- Skip plurals of words you’ve used, generic words like “app” or “game”, and filler words like “the”.
- Don’t use competitor app names, trademarks or celebrity names. Apple notes that improper keyword use is “a common reason for App Store rejections”.
Worked example for a fictional Singapore fitness studio app:
| Field | Text | Characters |
|---|---|---|
| App name | FitLoop: Gym Class Booking | 26 of 30 |
| Subtitle | Book HIIT, yoga and spin in SG | 30 of 30 |
| Keyword field | pilates,fitness,workout,studio,timetable,trainer,singapore,cycling,barre,boxing,schedule | 88 of 100 |
No keyword-field word repeats the name or subtitle, and 12 characters are left for terms you add after testing.
Google Play: title, short description, full description
Google’s metadata policy bans a few things that often slip into Play titles: emojis, ALL CAPS (unless it’s your brand), ranking claims such as “#1” or “Best of Play”, and promotional text such as “10% off”. Its preview asset rules add that the short description can’t contain emojis, repeated punctuation or calls to action like “download now”.
- Title (30 characters): same pattern as iOS. Brand plus the main phrase.
- Short description (80 characters): the main benefit in one sentence, with one or two keywords. Example: “Book gym, yoga and spin classes at studios across Singapore in a few taps.” (74 characters)
- Full description (4,000 characters): open with two or three sentences that explain the app, because Google notes users “may only read the first few sentences”. Then cover features in short paragraphs or lists, using your main phrases naturally. Don’t repeat the short description word for word.
Step 3: Get screenshots and preview videos right
Most people decide from the visuals. Apple notes that the first one to three screenshots appear in search results when there’s no app preview. On Google Play, the icon, title, rating and screenshots do the same job.
| Asset | Apple App Store | Google Play |
|---|---|---|
| App icon | Supplied in the app binary | 512 x 512 px, 32-bit PNG, max 1,024 KB |
| Screenshots | 1 to 10 per device size, JPEG or PNG, no transparency | 2 to 8 per device type, JPEG or 24-bit PNG |
| Required phone size | At least one for iPhone with Dynamic Island (medium display): 1179 x 2556 or 1206 x 2622 px portrait | Each side 320 to 3,840 px; at least four at 1080 px or more to be eligible for recommendations |
| Tablet | iPad 13-inch (2064 x 2752 or 2048 x 2732 px) if the app runs on iPad | At least four large-screen screenshots if you target tablets |
| Feature graphic | Not used | 1024 x 500 px, required |
| Video | Up to 3 app previews, 15 to 30 seconds, max 500 MB, autoplay muted | One YouTube link, public or unlisted, ads off; only the first 30 seconds autoplay |
Sources: Apple’s screenshot specifications and app preview specifications, and Google Play’s preview asset guide. Apple adds new device sizes most years, so check the current list before each design round.
A screenshot order that suits most apps:
- The main outcome, with a short caption (“Book a class in 10 seconds”).
- The second reason to install, often the feature competitors lack.
- Proof or a local detail, such as studios across Singapore or PayNow at checkout if you support it.
- Supporting features, one per image.
Keep captions to five or six words in large type, since people see them at thumbnail size. Show real app screens: both stores reject misleading visuals, and Google bans store badges and third-party logos you lack permission for. In preview videos, show the app in use straight away with captions, because Apple’s previews autoplay muted and Google recommends real footage within the first 10 seconds. Good screenshots start with good screens, so the UX design best practices behind your interface matter here too.
Step 4: Build ratings with the official review prompts
Apple states that ratings and reviews “can influence how your app ranks in App Store search”, and both stores show your star rating in results. Use the official prompts, not your own pop-up:
- iOS: StoreKit’s review request (SKStoreReviewController’s
requestReview(in:),AppStore.requestReview(in:), or SwiftUI’srequestReviewenvironment action). Apple’s documentation says the system shows the prompt a maximum of three times within a 365-day period, and that you shouldn’t call it from a button tap, because the prompt may not appear. - Android: the Play In-App Review API. Google enforces a quota it doesn’t publish, so calling it more than once in a short period “might not always display a dialog”. Google also says not to trigger it from a button.
Don’t ask “Do you like the app?” first (Google’s guidelines ban any question before or during the review card), don’t offer rewards for reviews, and don’t cover or restyle the card. Trigger the prompt just after the user succeeds at something:
| App type | Good moment to ask | Bad moment |
|---|---|---|
| Booking app | After the second completed booking | Right after sign-up |
| Ecommerce | After an order is delivered and marked received | At checkout or during a payment error |
| Fintech or utilities | After a task completes smoothly (a bill paid, a scan saved) | After a failed login |
| Learning or fitness | After finishing a lesson streak or third workout | During a lesson |
Reply to reviews in App Store Connect and Play Console, especially negative ones. A calm reply saying what you fixed shows future users you’re listening. The approach in our guide to responding to negative Google reviews works for app reviews too.
Step 5: Use Apple’s Custom Product Pages and In-App Events
Apple gives you two tools beyond the default listing.
Custom Product Pages are up to 70 extra versions of your product page, each with its own screenshots, app previews and promotional text, and a unique URL. You can now assign keywords to a custom page so it shows in organic search for those terms instead of your default page. You can also add a deep link (iOS 18 and later) so people who tap “Open” land on the right screen. Apple reports that developers see a 2.5 percentage point average lift in conversion when they send people to a custom product page, compared with a 1.6% average on default pages.
Use them for separate audiences (corporate wellness vs individual members), or so each ad campaign lands on screenshots that match the ad.
In-App Events are timed event cards that appear on your product page, in search results and in editorial spots. You can have up to 10 published at once, each running up to 31 days, and promote them up to 14 days before they start. Fields: event name (30 characters), short description (50) and long description (120), with a badge such as Challenge, Live Event, Major Update, New Season, Premiere or Special Event. Good fits are a Great Singapore Sale promotion, a new feature launch or a seasonal challenge. Google Play has a similar feature called promotional content, available to apps that meet its eligibility criteria.
On Google Play, the closest match to custom product pages is custom store listings. Google allows up to 50 per app, targeted by country, by a unique URL, or from some Google Ads campaigns.
Step 6: A/B test your listing on both stores
Both stores let you test creative changes on real store traffic.
| Apple Product Page Optimization | Google Play store listing experiments | |
|---|---|---|
| What you can test | Icon, screenshots, app previews | Icon, feature graphic, screenshots; descriptions in localised tests |
| Variants | Up to 3 treatments vs the original | Up to 2 variants vs the current listing |
| How many at once | One test at a time | One default graphics test, or up to 5 localised tests |
| Maximum length | 90 days | Stops automatically after 6 months |
| Confidence | Apply a winner at 90% confidence or higher | You set the confidence level and minimum detectable effect |
| Catch | Alternate icons must be in the app binary | Users seeing a localised listing are excluded from default graphics tests |
Sources: Apple’s Product Page Optimization page and Google’s store listing experiments help.
Test one element at a time (Google recommends this), starting with the icon or first screenshot. Write the hypothesis down, give small apps several weeks of traffic, apply the winner, and log the result before the next test. It’s the same thinking as website conversion rate optimisation.
Step 7: Localise for Singapore
Singapore has four official languages, but the app stores don’t treat them equally. Apple’s App Store localisation reference lists the Singapore storefront with English (U.K.) as the default language and Chinese (Simplified) as the additional supported language.
What that means in practice:
- iOS: many teams fill in only English (U.S.). Add an English (U.K.) localisation, using UK spelling, and a Simplified Chinese one. Each localisation has its own name, subtitle and keyword field, which gives you more room for search terms, including Chinese ones.
- Google Play: add translations for Chinese (Simplified), Malay and Tamil if your users use them. Play shows the translated listing to users whose device language matches.
- Malay and Tamil on iOS: Apple supports both for metadata. Tamil was one of 11 languages added on 31 March 2026, bringing the total to 50. Neither is listed for the Singapore storefront, though, so treat them as lower priority there unless you also target Malaysia or India.
Have a native speaker check every translation, since machine-translated Chinese captions are easy to spot. Our international SEO checklist applies the same localisation thinking to websites.
Step 8: Keep the app healthy, because quality affects visibility
ASO isn’t only text and images. Google says your app’s core vitals “affect the visibility of your app on Google Play”. From the Android vitals documentation:
| Core vital | Overall bad behaviour threshold | Per phone model |
|---|---|---|
| User-perceived crash rate | 1.09% | 8% |
| User-perceived ANR (app not responding) rate | 0.47% | 8% |
Play uses a 28-day average. Above these thresholds, Play “may reduce the visibility” of your app and may show a warning on your store listing. Google has also said memory usage and code optimisation thresholds may affect visibility from February 2027.
On iOS, crashes show up in reviews and ratings faster than in any dashboard. Either way, budget for updates after launch. Our breakdown of app maintenance costs in Singapore shows what to plan for.
Step 9: Add paid installs to speed up the start
Organic ranking needs downloads, and downloads need ranking. Paid installs break that loop early.
- Apple Ads (renamed from Apple Search Ads in April 2025) shows ads in search results, the Search tab, the Today tab and on product pages, and Apple announced more search result positions for 2026. Ads can point to a custom product page.
- Google Ads App campaigns promote Android apps across Google Play, Search, YouTube and Display. Our overview of types of Google Ads explains how they differ from Search campaigns.
Start with your brand name and a few specific keywords, watch cost per install and week-one retention, and feed the search term data back into your metadata. Our Google Ads team can run these alongside your other paid search.
Pre-launch and post-launch ASO checklist
Before you submit:
- One primary keyword phrase chosen per store
- Name, subtitle and keyword field (iOS) and title, short and full description (Play) written and counted
- Categories chosen
- Icon checked at small size on light and dark backgrounds
- Screenshots exported at current required sizes, captions readable as thumbnails
- English (U.K.) and Simplified Chinese localisations (iOS); translations considered (Play)
- Official review prompt built in, triggered after a success moment
- Analytics and crash reporting in place; privacy details (Apple) and Data safety form (Play) completed
Your mobile app requirements document is a good place to list the review prompt and analytics events, so they’re built rather than bolted on.
In the first 90 days after launch:
- Weeks 1 to 4: reply to every review, fix the top crash, check which search terms bring impressions
- Week 2: start small Apple Ads and Google App campaigns on brand and specific keywords
- Week 4: run the first screenshot test on each store
- Month 2: rewrite the subtitle or short description from search term data; add custom pages for main campaigns
- Month 3: plan an In-App Event around a real update or promotion
- Every release: update “What’s New” in plain words
Metrics to track
Both consoles give you the core numbers for free: App Analytics in App Store Connect and the store performance reports in Play Console.
| Metric | Where | What it tells you |
|---|---|---|
| Impressions from search | App Store Connect, Play Console | Whether your keywords are working |
| Product page views / store listing visitors | Both consoles | How many people open your listing |
| Conversion rate (installs ÷ page views) | Both consoles | Whether your visuals and rating persuade |
| Search terms bringing installs | Play Console; Apple Ads search terms report | Which phrases to push harder |
| Average rating and new ratings per week | Both consoles | Whether your review prompt timing works |
| Crash rate and ANR rate | Android vitals; Xcode Organizer | Quality issues that hurt ratings and Play visibility |
| Day 1, 7 and 30 retention | Your analytics (Firebase, GA4) | Whether the users you win stay |
ASO gets people to install. Retention shows whether they were the right people. If you track your app in Google Analytics 4, our guide to setting up GA4 covers the basics.
Frequently asked questions
How long does ASO take to show results?
Metadata changes on Google Play can show within days to a few weeks. On iOS, keyword changes need a new app version or an approved metadata update. Ranking for competitive terms usually takes months, because it depends on downloads and ratings building up.
How do I rank my app higher on the App Store?
Put your main keyword in the app name and subtitle, fill the 100-character keyword field without repeating words, choose the right category, and build ratings with Apple’s official review prompt. Then improve your first screenshots so more searchers install.
Is ASO different for Google Play?
Yes. Google Play has no hidden keyword field, so the title, short description and full description carry your keywords. Play also weighs app quality through Android vitals, and offers custom store listings and store listing experiments.
Do Apple Ads help organic rankings?
Apple doesn’t say paid installs affect organic ranking. What paid campaigns do give you is search term data and early downloads and ratings, which feed the user behaviour signals Apple says it uses.
Should I localise my app listing for Singapore?
Yes. Apple lists English (U.K.) and Simplified Chinese for the Singapore storefront, and each localisation adds its own keyword fields. On Google Play, Chinese, Malay and Tamil translations help users who browse in those languages.
Need help getting your app found?
ASO works best when it’s planned with the build: screens designed with screenshots in mind, review prompts placed at the right moments, and analytics in from day one. Our mobile app development team handles store submission and post-launch ASO for iOS and Android apps. If you’re still budgeting, start with our guide to the cost of developing an app in Singapore. Contact us to talk about your app’s launch.
