AdPocket
Summary
Start here: Enlarge or simplify the supporting caption on #1, #2, #3, #4, #5, #6 until it can be read comfortably without zooming.
The opening screenshots require material effort to read or separate the selling message at store preview size.
Recommended actions
Recommended change · #1, #2, #3, #4, #5, #6
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6 requires effort to read.
Enlarge or simplify the supporting caption on #1, #2, #3, #4, #5, #6 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.
Recommended change
The title is only the brand name, while the subtitle carries the main use-case signal.
Rewrite the title around a specific task supported by the supplied product description. Preserve the app's current scope; verify any new capability before naming it.
What this helps: Users scanning search results may not immediately understand what the app does from the title alone, reducing clarity and possible tap relevance.
How to check: Compare current metadata against a title that communicates the dashboard/statistics use case more directly and measure tap-through and install intent.
Optional test
These source-supported benefits lack a demonstrated screenshot in the supplied coverage evidence.
Test 2 additional screenshots: Show notification scheduling or a daily summary example so visitors can see passive monitoring without opening the app.; Show the alert configuration or an alert example that makes drop detection visibly understandable and clearly on-device..
What this helps: Visitors may not realize the app can notify them without opening the dashboard.
How to check: Test the current gallery against a version with one added monitoring screenshot and compare store conversion.
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 a mobile ad revenue dashboard use case and the main benefit of seeing today's revenue fast.
The first three screenshots present a clear story of checking revenue, building reports, and monitoring trends with coherent product proof.
No specific change is recommended here.
#1
Audit notes
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6 requires effort to read.
#2
Audit notes
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6 requires effort to read.
#3
Audit notes
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6 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 captions are mostly benefit-led and tie each screen to a specific user outcome such as revenue checks, reports, trends, widgets, account switching, and privacy.
The captions naturally align with likely partner-dashboard intent through revenue, reports, trends, accounts, and security messaging.
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.
These source-supported benefits lack a demonstrated screenshot in the supplied coverage evidence.
Optional test: Test 2 additional screenshots: Show notification scheduling or a daily summary example so visitors can see passive monitoring without opening the app.; Show the alert configuration or an alert example that makes drop detection visibly understandable and clearly on-device..
Rest of gallery
The first 3 win attention. The rest helps convinced users learn more.
#4
#5
#6
View findings and assessment details
Actions (2)
Working (4)
Sequence logic
Repetition and duplicate value
Differentiation vs generic category claims
Shows result, not just process
Visual Quality & Readability
Readability
How easily users can scan the screenshots, trust the visuals and recognize category fit.
At a 220px store preview, the supporting caption on #1, #2, #3, #4, #5, #6 requires effort to read.
Enlarge or simplify the supporting caption on #1, #2, #3, #4, #5, #6 until it can be read comfortably without zooming.
View findings and assessment details
Available evidence: Some checks could not be assessed. This score describes only the available evidence.
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.
The provider reports 0 public ratings.
Optional test: Use the in-app review prompt after users have had time to try the app.
Trust signals
- Average rating
- No public average available
- Rating count
- 0 ratings
- App update freshness
- Last updated Oct 15, 2026
View findings and assessment details
Available evidence: Some checks could not be assessed. This score describes only the available evidence.
Actions (1)
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.
Metadata & Search Alignment
Metadata
How well title, secondary metadata and screenshots sell the same intent.
The title is only the brand name, while the subtitle carries the main use-case signal.
Rewrite the title around a specific task supported by the supplied product description. Preserve the app's current scope; verify any new capability before naming it.
Metadata
- Title
- AdPocket
- Subtitle
- YAN partner stats in pocket
- Category
- Business
- Public rating
- 0 ratings
View findings and assessment details
Actions (1)
Working (4)
Title/secondary metadata keyword overlap
Secondary metadata is not slogan fluff
Screenshot-to-metadata alignment
Category expectation match
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.255