Recipe Keeper: CookBook
Summary
Start here: Start with #7. Keep the main headline and a small set of adjustment examples. Reduce the number of floating tags or consolidate them so the adaptation promise reads first.
Recommended actions
Recommended change · #7
#7: The adaptation promise is apparent, but the extra 'AI powered' line and four floating tags create more scan stops before the core message settles.
Start with #7. Keep the main headline and a small set of adjustment examples. Reduce the number of floating tags or consolidate them so the adaptation promise reads first.
What this helps: Competing selling elements make visitors work to identify the main benefit before they can decide to explore the app.
How to check: View the revised screenshot at 220px wide and check whether a new visitor can identify its main benefit and product proof at a glance.
Recommended change · #8
#8 claims "Calculate macros & nutrition," but the small macro values in the top floating stats card are strained at preview size.
Enlarge or crop the top floating stats card so the macro values visibly substantiate "Calculate macros & nutrition" while keeping the clear headline.
What this helps: Visitors may understand the feature but miss the concrete proof that the app actually shows usable nutrition results.
How to check: Compare whether more viewers can identify a visible calorie and macro result on #8 at store preview size.
Optional test · #1
At a 220px store preview, the supporting caption on #1 requires effort to read.
Enlarge or simplify the supporting caption on #1 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
The first 3 screenshots have the bones of a clear install story.
Main use case appears in first 3 is one of the stronger parts of this listing.
The screenshots use decorated store creative or benefit-led framing that explains value outside the app UI.
First 3 Screenshots
First 3
How quickly the listing explains what the app does and why to install.
#1 makes the app category and core recipe-organizing use case clear, with a broad benefit-led promise.
The lead screen communicates core value, though it uses a promotional opener instead of direct product proof.
No specific change is recommended here.
#1
Audit notes
At a 220px store preview, the supporting caption on #1 requires effort to read.
#2
#3
View findings and assessment details
Available evidence: Some checks could not be assessed. This score describes only the available evidence.
Actions (0)
No supported actions identified from the available evidence.
Working (4)
Screenshot 1 explains the app
First 3 tell a clear install story
No low-value lead screens
Main use case appears in first 3
Not assessed
These checks have insufficient evidence and are excluded from new score calculations.
Real app UI appears early: The cited screenshot numbers do not match the supplied evidence.
Screenshot Messaging
Messaging
Whether captions are useful, specific and proven by the visible UI.
#7: The adaptation promise is apparent, but the extra 'AI powered' line and four floating tags create more scan stops before the core message settles.
Start with #7. Keep the main headline and a small set of adjustment examples. Reduce the number of floating tags or consolidate them so the adaptation promise reads first.
View findings and assessment details
Actions (1)
Working (5)
Benefit-led captions
Decorated store creative
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.
The gallery covers many distinct verified reasons to install, though at least one useful described benefit remains undemonstrated.
The screenshots show some category differentiation through import, scanning, adaptation and nutrition workflows.
No specific change is recommended here.
Rest of gallery
The first 3 win attention. The rest helps convinced users learn more.
#4
#5
#6
#7
#8
#9
#10
View findings and assessment details
Available evidence: Some checks could not be assessed. This score describes only the available evidence.
Actions (0)
No supported actions identified from the available evidence.
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.
Not assessed
These checks have insufficient evidence and are excluded from new score calculations.
Repetition and duplicate value: The assessment does not identify verifiable evidence.
Visual Quality & Readability
Readability
How easily users can scan the screenshots, trust the visuals and recognize category fit.
#7: The adaptation promise is apparent, but the extra 'AI powered' line and four floating tags create more scan stops before the core message settles.
Start with #7. Keep the main headline and a small set of adjustment examples. Reduce the number of floating tags or consolidate them so the adaptation promise reads first.
View findings and assessment details
Available evidence: Some checks could not be assessed. This score describes only the available evidence.
Actions (2)
Working (5)
App UI is large enough
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.
Composition, spacing and padding: The assessment does not identify verifiable evidence.
Trust & Social Proof
Trust
Available public ratings, update history and product-specific trust evidence.
Average rating: 4.8
The screenshots make capability claims that are supported by visible product demonstrations and do not rely on questionable trust badges or adoption claims.
No specific change is recommended here.
Trust signals
- Average rating
- 4.8 stars
- Rating count
- 2,649 ratings
- App update freshness
- Last updated Sep 27, 2026
View findings and assessment details
Actions (0)
No supported actions identified from the available evidence.
Working (1)
Screenshot trust cues
Listing context
The public rating is context. It does not establish which creative change to prioritize.
Public rating volume is context, not a required creative change.
The update date does not by itself establish a product or security problem.
Metadata & Search Alignment
Metadata
How well title, secondary metadata and screenshots sell the same intent.
The proposed replacement adds no verified category, use case or benefit beyond the existing fields.
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
- Recipe Keeper: CookBook
- Subtitle
- Al Import & Grocery List
- Category
- Food & Drink
- Public rating
- 4.8 average · 2,649 ratings
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
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