guide

App store optimisation

How App Store and Google Play listings are structured: title, screenshots, keywords, reviews, and what optimisation cannot fix.

App store optimisation, often shortened to ASO, is the work of making a store listing accurate and easy to understand. On Apple's App Store the fields people actually see are the name, subtitle, icon, screenshots, and preview video. Keywords are a hidden field with a character limit. On Google Play the short description and the long description are indexed more directly, and the title still carries weight. The two stores are not the same form with different logos.

Start from the words a person types, not from the words the company uses internally. If someone looks for 'mileage log' and the title only says a brand name, the listing depends on the brand being known. A small product usually needs the job in the title or subtitle. A known brand can spend that space on a different message. Either way, the first screenshot should show the product doing the job, with a short caption, not a slogan about innovation.

Screenshot sets fail when they are a tour of every menu. Three to five frames that follow the main task are easier to scan on a phone. Use the device sizes the store currently requires and check them on a real phone, because a caption that fits a desktop mock is often truncated on the store. Localized listings matter when you sell in more than one language. A machine-translated subtitle can change the meaning of a purchase.

Ratings are an outcome of the product and of when you ask. Asking for a review after a failure, or before the person has done anything, trains people to ignore the prompt or to leave a low score. Apple and Google both limit how naggy the prompt can be. A listing cannot outrun a crash on launch. Fix the crash before you buy ads that send strangers to that listing.

Custom product pages and store experiments exist on both platforms, with different rules and different reporting. Use them when you have enough traffic for a comparison to mean something. A test with a handful of views will wander. This page does not report an experiment we ran. It describes how the tools are meant to be used.

Keywords rot. A term that matched the product last year may now describe a different category, or a competitor may have made it uselessly broad. Review the listing when you ship a major feature, when you enter a country, and when the conversion from store view to install drops. Conversion here means the store's own reporting, not a number invented for a sales deck.

ASO does not replace a clear first-run experience. If the screenshots promise a result the app hides behind a subscription with no explanation, the listing and the product are in conflict, and review teams notice. Write the listing from the build you are actually submitting.

The iOS and Android hubs describe how the binaries are built. This page sits beside them because a shipped binary with a confusing listing is only half released. ClickMasters can help with the product and with the listing copy. Ask for a review of the current title, subtitle, and first three screenshots if you already have an app in market.

Review the listing on a phone, not only in App Store Connect or Play Console. Read the title out loud. If it does not say what the app does, the screenshots have to do that job in the first frame. Check that the subtitle or short description does not repeat the title word for word, because the wasted characters could have named the audience or the job. Confirm the support URL loads without a login wall. Confirm the privacy policy matches the SDKs in the binary you are submitting, not the binary you plan to submit next month. Do this the day before upload, when the feature list is frozen. A listing edited from memory after a last-minute cut is how screenshots advertise a button that is no longer there.

Ask for a scoped plan

Send the flows, the platforms, and the systems the app must call. We will reply with what is in the first release and what should wait. This guide is not a quote and not a test report.

Contact ClickMasters

Related guides

  • Swift app development

    What Swift and SwiftUI are used for in an iPhone app, how modules are split, and what to decide before writing the first screen.

  • Develop an iOS app

    A practical sequence for developing an iOS app, from the flow list and TestFlight plan through App Store submission.

  • iOS app development

    How native iOS apps are planned in Swift and SwiftUI, what App Store review checks, and when iPhone-only is the right scope.

  • Android app development

    How native Android apps are built with Kotlin, how Play review works, and what to decide about devices, screens, and background work.

  • Flutter and React Native

    When a shared Flutter or React Native codebase fits, where native code still appears, and how to choose between them.

  • Mobile app cost

    What actually changes the cost of a mobile app, how to read a range, and what to send so an estimate can be scoped.