Games · US iPhone listing

ASO Audit: Royal Match

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

4/10Recognisable. Not convincing.

Royal Match shows rescue, rescue and more rescue. The danger changes; the argument does not. The audit question is whether this opening represents the actual first sessions, not whether a bigger falling rock would look exciting.

ASO Audit: Royal Match illustration: A colorful match-three board leads toward separate dramatic puzzle scenes.
Gabriel Machuret in an ASO Guru T-shirt: calling out repeated screenshots.

Gab’s verdict · 4/10Gabriel Machuret

Editorial illustrationThree ways to endanger the king. One narrow sales story.See the actual listing screenshots ↓
Listing snapshot · what I checked

What I actually checked

One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.

Store & market
Apple App Store · United States
Language & device
en-US · iPhone
Captured
30 September 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 11/30 characters

Royal Match

Observed subtitle · 29/30 characters

King Robert’s Match 3 Puzzles

Gab’s take · Five criteria. Two points each.

Why this gets 4/10

The rescue scenes are readable and the matching boards are visible. Keep the urgency. The unanswered question is how representative that opening is of the game a new player will actually reach. Verify how the pictured situations fit the current game, then show a representative play loop. Historical reviews do not establish today's frequency. Repeating rescue artwork cannot substitute for an accurate introduction.

  1. Reason to care

    1/2

    Rescue danger is clear but the broader game is not.

  2. Product evidence

    1/2

    Match-three boards appear without establishing the normal play mix.

  3. Readable at a glance

    2/2

    Bold captions and contrast create readable urgency.

  4. A useful sequence

    0/2

    Three rescue scenes repeat one proposition.

  5. A reason to choose

    0/2

    Different hazards do not demonstrate broader game value or representativeness.

0: not earned · 1: useful but incomplete · 2: clearly demonstrated. Judged on the dated opening creative; public metadata provides context. These points assess creative execution, not private conversion or ranking performance. Read the scoring criteria · See all ten verdict levels

Three things worth your attention

The screenshot teardown

Inspect the numbered original, read the problem, then compare the proposed fix. The publisher’s creative stays unchanged.

What the visitor sees → what I’d change

The rescue needs context

Look at the original: The artwork shows match-three pieces below the threatened king and an illustrated hand selecting pieces.

Why I’m flagging it: A dramatic scene does not establish its place in normal play.

Brief this change

Verify the current mode and show a representative match action.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The shark repeats the same pitch

Look at the original: A second rescue scene repeats the board-and-danger composition.

Why I’m flagging it: A new hazard adds little explanation beyond another rescue.

Brief this change

Use this position for a different genuine core-game decision.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The rockfall still avoids breadth

Look at the original: The third opening still uses another danger scenario and a pointed match-three gesture.

Why I’m flagging it: A third danger scene repeats the gesture and premise.

Brief this change

Show authentic progression or its consequence without implying mode frequency.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 30 September 2026. Creative belongs to the app publisher and is reproduced for analysis. Publisher claims inside screenshots are not independently verified.

What I’d put on the table

Proposed copy for discussion. These are not current listing fields or tested winners.

Observed listing

Royal Match

King Robert’s Match 3 Puzzles

Proposed alternative

Royal Match

Match 3 puzzles with the king

Name 11/30 · Subtitle 29/30 characters
Metadata comparison. A proposed alternative to review against the current listing.

Keep the brand name and state the visible mechanic in plain language while retaining the character context. The alternative avoids promising constant rescue scenarios.

The tradeoff: It removes Robert’s name and largely restates the existing subtitle. This is a clarity hypothesis, not a necessary keyword expansion; preserve the current subtitle unless research supports a change.

Gab’s proposed direction

Give each screenshot a job.

Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from Royal Match or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Make your first match

    Illustrative layout · verify the real flow

    Put this in the frame: A captured, reproducible early board with the real gesture and outcome.

    Why it earns the space: Set an accurate expectation for the first session.

  2. 02Show useful evidence

    Proposed headline

    See what comes next

    Illustrative layout · verify the real flow

    Put this in the frame: The verified progression step reached after that board, using genuine current footage or screenshots.

    Why it earns the space: Explain the loop instead of assuming every successful match immediately triggers a rescue.

  3. 03Move the decision forward

    Proposed headline

    Meet a rescue challenge

    Illustrative layout · verify the real flow

    Put this in the frame: A verified rescue scenario with accurate access context and no invented availability claim.

    Why it earns the space: Keep the distinctive dramatic proposition while explaining its actual place in the game.

The test: Does an authentic early-play opening set clearer expectations while preserving qualified download conversion? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.

Want this level of detail for your app?

Bring the listing. I’ll help you decide what to keep, what to fix and what to test.

Talk to Gabriel →
Compare three alternatives

Three alternatives—and what they make clearer

Observed competitor metadata

Candy Crush Saga ↗

Your Relaxing Puzzle Escape!

Candy Crush Saga describes a relaxing puzzle escape.

The lesson: It uses a mood benefit rather than a rescue promise. Royal Match can make the actual first action clear without claiming the same emotional effect for every player.

Observed competitor metadata

Gardenscapes ↗

Enjoy Your Garden Puzzle Game

Gardenscapes pairs its name with a garden puzzle-game proposition.

The lesson: A setting can frame progression, but metadata does not establish how its gameplay compares. Explain Royal Match’s own verified loop.

Observed competitor metadata

Toon Blast ↗

Funniest Match 3 Puzzle Game

Toon Blast explicitly names match-three puzzle play.

The lesson: The mechanic is direct category language. Royal Match already includes match-three in its subtitle; its creative can connect that label to an authentic early session.

Competitor comparison. US listing names and subtitles captured 30 September 2026. These are positioning comparisons, not ranking or revenue comparisons.
Keyword ideas and their evidence

The keyword questions I’d investigate

Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.

match 3 puzzle / matching game

Visitor’s job: Find a game built around matching pieces and clearing boards.

Evidence: The subtitle explicitly names Match 3 Puzzles and all three images contain matching boards.

Decision: Retain the mechanic as the core category term; do not infer keyword demand or difficulty.

save the king / rescue puzzle

Visitor’s job: Play the particular rescue situations shown in the creative.

Evidence: All three opening stills feature danger and a rescue objective.

Decision: Verify availability and progression before using rescue language as a general promise of the whole experience.

Royal Match / King Robert

Visitor’s job: Find this specific game or return to a recognised character.

Evidence: The name identifies the brand and the subtitle names King Robert.

Decision: Preserve brand continuity. Research returning-player expectations separately from a newcomer’s understanding of the first session.

The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.

What the selected reviews tell us

What three reviewers can teach us

Three 2023–2025 accounts were selected because they describe different rescue-versus-regular-play expectations. Their disagreement is preserved. They do not establish current mode frequency, ad policy, pricing, offline behaviour or deceptive advertising, and they are not a representative retention or satisfaction sample.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 7 July 2023–6 October 2025. No sentiment percentage is calculated.

6 October 2025 · 5/5 stars

“Kings Nightmare”

An October 2025 reviewer enjoyed the game and distinguished rescue-themed advertising from the wider experience.

What I’d investigate: Their ad-free and purchase-value statements remain personal reports, not verified current policy. Investigate mode identity and access independently.

Listing review source · Review ID 13232085094

6 August 2023 · 5/5 stars

“match three game”

An August 2023 reviewer liked the game and rescue levels but reported an interruption after losing connectivity.

What I’d investigate: Do not infer current offline support or a current resume defect. The account provides a different view of rescue availability from the next selected reviewer.

Listing review source · Review ID 10226422367

7 July 2023 · 4/5 stars

“little side games”

A July 2023 reviewer enjoyed play but was frustrated by how rarely rescue-like situations appeared at their reported progression.

What I’d investigate: Verify the current game version and progression before making a frequency claim or adopting the reviewer’s advertising accusation.

Listing review source · Review ID 10112456406

A displayed review can be old, unusually positive or internally inconsistent with its star rating. These accounts suggest questions; they do not establish current defects or typical customer experience. Use the Review Research Desk to keep evidence and interpretation separate.

What I’d do first

01

The rescue needs context

A dramatic scene does not establish its place in normal play.

Deliverable: Verify the current mode and show a representative supported match action.

Creative brief and current-product check
02

The shark repeats the same pitch

A new hazard adds little explanation beyond another rescue.

Deliverable: Use this position for a different genuine core-game decision.

Creative brief and current-product check
03

The rockfall still avoids breadth

A third danger scene repeats the gesture and premise.

Deliverable: Show authentic progression or its supported consequence without implying mode frequency.

Creative brief and current-product check
Open the full test plan

One test worth running

Does an authentic early-play opening set clearer expectations while preserving qualified download conversion?

Audience
Eligible US English iPhone default-page visitors, with separate research among new match-three players and people arriving from rescue-themed advertising.
Control
The current first frame only after verifying the depicted scenario and access claims; correct any confirmed mismatch before testing and collect a new baseline.
Treatment
Replace frame one with a verified early gameplay example and accurate first-action wording; keep later frames, metadata and other assets fixed after validating their claims.
Method
Document current gameplay and run comprehension research, then eligible App Store product page optimization. This compares complete opening concepts, not game difficulty or measured retention.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Participants should identify the matching mechanic without assuming every level is a rescue. First-session progression and retention need separately consented product evidence and cannot be inferred from downloads.
Decision rule
Predefine a useful effect, sample requirement and decision timing from baseline traffic. Keep control if inconclusive; reject a lift caused by stronger inaccurate expectations about scenario frequency.
What could muddy the result
Game versions, event schedules, progression states, paid creative mix and returning-player campaigns can alter the result.

Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.

How the ten-point scale works

So, does their ASO suck?

1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up

  1. 1/10

    Yeah. It really does!

    The basics need a serious rethink.

  2. 2/10

    I hope no agency is getting paid for this.

    Too many obvious things have been left unfinished.

  3. 3/10

    The app deserves better.

    There is a useful product here. The listing needs to show it.

  4. 4/10Royal Match is here

    Recognisable. Not convincing.

    Some basics work, but the opening wastes attention and under-explains the benefit.

  5. 5/10

    Fine. A dangerous place to stop.

    There is usable creative here, but too much of the sales argument is left to the visitor.

  6. 6/10

    Useful. Still leaving too much unsaid.

    Real strengths, undermined by meaningful gaps in the opening story or execution.

  7. 7/10

    Good. The product proof earns it.

    A clear, useful demonstration with specific refinements still needed.

  8. 8/10

    Good. Now sweat the details.

    The main promise is clear and supported. Refinement matters more than reinvention.

  9. 9/10

    Whoever did this knows their stuff.

    Clear positioning, thoughtful choices and very few loose ends.

  10. 10/10

    Okay, now you’re showing off.

    An unusually clear, convincing storefront worth learning from.

An editorial verdict on the captured storefront, not a measured ASO score or an assessment of an agency’s private work.

Try this on your app · worksheet and assignment

Your ASO assignment

  1. Verify the current mode and show a representative supported match action.
  2. Use this position for a different genuine core-game decision.
  3. Show authentic progression or its supported consequence without implying mode frequency.

What would change my mind?

  • Current playable scenarios, first-session progression and mode availability.
  • Approved creative assets with a clear distinction between gameplay and illustration.
  • Conversion baseline, acquisition-context research and separate first-session outcome data.
Sources and capture dates

Sources and scope

No private analytics, search-rank dataset or internal keyword field was supplied. Review quotations are short excerpts; explanations are our summaries. App names and screenshots belong to their respective owners. We are not affiliated with Royal Match. Read our editorial methodology.

Your app. Your priorities.

Get an audit you can actually use.

Send your listing, market and the problem you want to solve. I’ll explain the scope and fee before work starts. Your budget should buy decisions, not a longer PDF.

Apply the method to your app

Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.

More app teardowns

Browse the complete app teardown library →

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.