Hungry Pop: Food Runner
Summary
Start here: Remove or replace #8, keeping #1 as the core gameplay opener and using that slot for a different demonstrated workflow.
The opening screenshots require material effort to read or separate the selling message at store preview size.
Recommended actions
Recommended change · #1, #8
#1 and #8 both sell the same core gameplay promise with the same caption and similar combo-run proof.
Remove or replace #8, keeping #1 as the core gameplay opener and using that slot for a different demonstrated workflow.
What this helps: Visitors spend a slot on repeated value instead of seeing another distinct part of the game.
How to check: Compare the current gallery against a version where #8 is replaced by a distinct existing app workflow and measure screenshot engagement or install conversion.
Recommended change · #1, #2, #3, #4, #5, #6, #7, #8
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 requires effort to read.
Enlarge or simplify the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 until it can be read comfortably without zooming.
What this helps: Larger, shorter supporting captions would make the selling message easier to read without zooming.
How to check: View the revised images at 220px wide without zooming and check that the cited text or product detail is comfortably readable.
What is working
Screenshot 1 explains the app is one of the stronger parts of this listing.
The first 3 screenshots have the bones of a clear install story.
The first screenshots show real app UI quickly, which helps users understand the product before they scroll.
First 3 Screenshots
First 3
How quickly the listing explains what the app does and why to install.
#1 clearly communicates an arcade food runner where you jump, eat and chain combos through a timed meal.
#1 to #3 tell a coherent install story from core play to themed variety and hazard variety.
No specific change is recommended here.
#1
Audit notes
#1 and #8 both sell the same core gameplay promise with the same caption and similar combo-run proof.
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 requires effort to read.
#2
Audit notes
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 requires effort to read.
#3
Audit notes
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 requires effort to read.
View findings and assessment details
Actions (0)
No supported actions identified from the available evidence.
Working (5)
Screenshot 1 explains the app
First 3 tell a clear install story
Real app UI appears early
No low-value lead screens
Main use case appears in first 3
Screenshot Messaging
Messaging
Whether captions are useful, specific and proven by the visible UI.
The gallery uses clear benefit-feature captions, with stronger payoff framing in gameplay shots than in some shop-focused shots.
The captions reinforce runner-game intent with terms tied to jumping, combos, hazards and power-ups.
No specific change is recommended here.
View findings and assessment details
Actions (0)
No supported actions identified from the available evidence.
Working (7)
Benefit-led captions
Decorated store creative
Caption matches visible UI
One idea per screenshot
Business clarity
Keyword and intent alignment in captions
Avoid generic claim words without proof
Screenshot Set / Story
Story
How well the full gallery builds distinct reasons to install.
#1 and #8 both sell the same core gameplay promise with the same caption and similar combo-run proof.
Remove or replace #8, keeping #1 as the core gameplay opener and using that slot for a different demonstrated workflow.
Rest of gallery
The first 3 win attention. The rest helps convinced users learn more.
#4
#5
#6
#7
#8
View findings and assessment details
Actions (1)
Working (4)
Full gallery covers distinct reasons to install
Sequence logic
Differentiation vs generic category claims
Shows result, not just process
Listing context
Screenshot count is context. Additional images are useful only when they answer an unanswered visitor question.
Visual Quality & Readability
Readability
How easily users can scan the screenshots, trust the visuals and recognize category fit.
Assessment details: Some checks could not be assessed. This score describes only the available evidence.
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 requires effort to read.
Enlarge or simplify the supporting caption on #1, #2, #3, #4, #5, #6, #7, #8 until it can be read comfortably without zooming.
View findings and assessment details
Actions (1)
Working (7)
App UI is large enough
Visual hierarchy
Composition, spacing and padding
Design consistency
Visual polish and category fit
Synthetic or untrusted creative cues
Text density
Not assessed
These checks have insufficient evidence and are excluded from new score calculations.
Essential text contrast: The assessment does not identify verifiable evidence.
Trust & Social Proof
Trust
Available public ratings, update history and product-specific trust evidence.
Assessment details: Some checks could not be assessed. This score describes only the available evidence.
Visible product evidence credibly supports the screenshot claims and no misleading trust claim is identified.
No specific change is recommended here.
Trust signals
- Average rating
- No public average available
- Rating count
- Not supplied by provider
- App update freshness
- Last updated Sep 30, 2026
View findings and assessment details
Actions (0)
No supported actions identified from the available evidence.
Working (1)
Screenshot trust cues
Listing context
The update date does not by itself establish a product or security problem.
Not assessed
These checks have insufficient evidence and are excluded from new score calculations.
Average rating: No valid public average rating is available.
Rating volume confidence: The listing provider did not supply a valid rating count.
Metadata & Search Alignment
Metadata
How well title, secondary metadata and screenshots sell the same intent.
The title and secondaryMetadata together clearly communicate a casual food-running game and the timed combo mechanic.
The title and secondary metadata do not repeat meaningful wording; complementary category and benefit terms are useful.
No specific change is recommended here.
Metadata
- Title
- Hungry Pop: Food Runner
- Short description
- Jump, eat and chain food combos through a three-course meal in two minutes.
- Category
- Casual
- Public rating
- Not supplied
View findings and assessment details
Actions (0)
No supported actions identified from the available evidence.
Working (5)
Public metadata clarity and field usage
Title/secondary metadata keyword overlap
Secondary metadata is not slogan fluff
Screenshot-to-metadata alignment
Category expectation match
Website badge
Show this ASO score on your site
Embed a live AppScreens score badge on your website, launch page or changelog.
HTML embed
The badge links back to this public ASO review and updates with the reviewed score version.
Turn this audit into screenshots
Use the audit notes to build clearer App Store and Google Play screenshots, or run another free ASO review.
© 2026 AppScreens, a registered business name of Salty Bytes Pty Ltd. All rights reserved | v1.1.259