Productivity & AI · US iPhone listing

ASO Audit: Forest

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Forest has a memorable metaphor and surrounds it with clipped devices, audience claims and a garden. The useful question is simpler: what happens when I start a session, stay focused or leave? Show that before planting more scenery.

ASO Audit: Forest illustration: A thriving tree under glass contrasts with a locked barren tree.
Gabriel Machuret in an ASO Guru T-shirt: waiting for the finished result.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationA lovely forest. The focus rules need daylight.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
1 October 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 30/30 characters

Forest: Focus for Productivity

Observed subtitle · 28/30 characters

Pomodoro Timer, ADHD & Study

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

Why this gets 5/10

The tree mechanism gives the app a memorable identity. Keep it. The explanation needs to connect the timer, tree outcome and current blocking behaviour rather than expecting the metaphor to explain everything. The screenshot execution still needs a complete, readable demonstration and consistent claim wording. Follow one session into its actual result, then explain blocking and access. The metaphor should make the behaviour clearer, not carry the explanation alone.

  1. Reason to care

    1/2

    Smarter time is broad; the tree mechanism provides some specificity.

  2. Product evidence

    1/2

    Timer and garden states appear without a complete focus session.

  3. Readable at a glance

    1/2

    Split devices and decorative gardens compete with useful controls.

  4. A useful sequence

    1/2

    Planting and withering connect, but blocking arrives as a separate story.

  5. A reason to choose

    1/2

    The tree metaphor differentiates without fully explaining current access.

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 tree hides the control

Look at the original: The large tree and timer dominate the frame, with the device continuing toward the next composition.

Why I’m flagging it: Decoration and audience artwork compete with the actual timer action.

Brief this change

Enlarge a complete session setup and verify the audience claim.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The consequence needs context

Look at the original: The left edge continues the phone from the first still; the garden includes a visibly withered tree.

Why I’m flagging it: The withering message does not fully explain the session rules.

Brief this change

Show one genuine session outcome with accurately scoped behaviour.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The blocking panel needs a clean crop

Look at the original: The artwork combines a block list and schedule; the visible icon strip and app-count label also warrant consistency checking.

Why I’m flagging it: Schedule detail and icon counts demand closer inspection.

Brief this change

Recapture consistent current controls and make access conditions readable.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 1 October 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

Forest: Focus for Productivity

Pomodoro Timer, ADHD & Study

Proposed alternative

Forest: Focus Timer

Grow trees, block distractions

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

Keep the brand and timer category while connecting the visual reward with the distinct blocking feature.

The tradeoff: This removes ADHD and study wording from the proposed subtitle and may narrow some discovery cues. Validate intent and claim support separately; do not change metadata during the scheduled-blocking test.

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 Forest or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Choose your focus session

    Illustrative layout · verify the real flow

    Put this in the frame: The authentic timer, chosen tree and duration within a complete opening composition.

    Why it earns the space: Explain the commitment without inventing a productivity result.

  2. 02Show useful evidence

    Proposed headline

    See your forest grow

    Illustrative layout · verify the real flow

    Put this in the frame: The matching garden with accurate mode-specific completion and interruption context.

    Why it earns the space: Retain the emotional reward and connected design.

  3. 03Move the decision forward

    Proposed headline

    Schedule the distractions out

    Illustrative layout · verify the real flow

    Put this in the frame: A current enabled blocking schedule and its real blocked-app state, with access context.

    Why it earns the space: Separate the blocking rule from the tree-session rule.

The test: Does showing an active scheduled block clarify Forest’s Time Guard feature? 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

Focus To-Do: Focus Timer&Tasks ↗

Pomodoro timer for work&study

Focus To-Do names a timer and tasks for work and study.

The lesson: Forest can keep its reward distinction while clearly explaining what the timed session measures.

Observed competitor metadata

Opal: Screen Time Control ↗

Focus, App Blocker & Timer

Opal names screen-time control, an app blocker and a timer.

The lesson: Blocking intent overlaps directly. Explain the exact scheduled-block behaviour rather than relying on the tree metaphor.

Observed competitor metadata

Freedom: Screen Time Control ↗

Block Apps. Stay Focused.

Freedom names screen-time control and blocking apps.

The lesson: Forest should state supported devices and rules precisely without adopting broad cross-platform or impossible-to-bypass claims.

Competitor comparison. US listing names and subtitles captured 1 October 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.

focus timer / study timer

Visitor’s job: Commit to a chosen period of work with a visible reward.

Evidence: The timer and virtual tree appear in the opening pair.

Decision: Explain session settings and interruption rules without claiming measured attention or treatment for a condition.

app blocker / scheduled focus

Visitor’s job: Restrict selected distractions during defined times.

Evidence: The third screenshot and Time Guard description support scheduled blocking.

Decision: Demonstrate configuration and an actual block, including supported OS and plan requirements.

gamified focus / grow a forest

Visitor’s job: Use a growing collection as motivation to return.

Evidence: The second screenshot shows the virtual collection and the description names rewards.

Decision: Distinguish virtual rewards from real-tree programmes and verify their separate access and fulfilment terms.

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 2019–2024 accounts were selected for starting friction, mode choice and a resolved labelling issue. Historical purchase prices and coin rules do not define the current Plus offer. Personal study and health experiences are not evidence of clinical effectiveness or measured productivity gains.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 5 November 2019–1 December 2024. No sentiment percentage is calculated.

15 November 2022 · 5/5 stars

“actively make every day”

A November 2022 reviewer found the tree consequence motivating but emphasised the difficulty of choosing to start the app consistently.

What I’d investigate: Retain that limitation. A personal ADHD account does not establish a clinical effect or automatic habit formation.

Listing review source · Review ID 9293210464

1 December 2024 · 5/5 stars

“stopwatch and timer”

A December 2024 reviewer valued choosing modes when session length was uncertain and liked the allow list, while asking for scheduled Pomodoro breaks.

What I’d investigate: Verify current modes rather than repeating the old break request as an active omission; the present subtitle now names a Pomodoro timer.

Listing review source · Review ID 12014273120

5 November 2019 · 5/5 stars

“bug fixed”

A November 2019 reviewer liked the visible record and reported a labelling issue that support fixed.

What I’d investigate: Preserve the resolution. Do not reuse the historical price, reward economy or support turnaround as current guarantees.

Listing review source · Review ID 5090428056

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 tree hides the control

Decoration and audience artwork compete with the actual timer action.

Deliverable: Enlarge a complete supported session setup and verify the audience claim.

Creative brief and current-product check
02

The consequence needs context

The withering message does not fully explain the session rules.

Deliverable: Show one genuine session outcome with accurately scoped behaviour.

Creative brief and current-product check
03

The blocking panel needs a clean crop

Schedule detail and icon counts demand closer inspection.

Deliverable: Recapture consistent current controls and make supported access conditions readable.

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

One test worth running

Does showing an active scheduled block clarify Forest’s Time Guard feature?

Audience
US English iPhone visitors seeking scheduled distraction control, with existing Forest timer users identified separately.
Control
The captured connected first pair and blocking setup frame after claim, icon-count and access inconsistencies are corrected across variants.
Treatment
Replace only frame three with a verified scheduled-block setup and resulting blocked-app state. Preserve the complete opening pair, metadata and offer.
Method
Verify OS permissions, schedule activation, pause and interruption behaviour first. Randomize store-sized comprehension research and eligible App Store product page optimization.
Primary measure
Correct understanding of when selected apps are blocked and how this differs from a tree session; platform-reported download conversion in the store.
Guardrails
No belief that all apps are always blocked, every virtual tree plants a real tree or every feature is included free. Preserve access to the stated allowed-app workflow.
Decision rule
Predefine a useful comprehension gain and required sample from baseline data. Ship only if mode and access expectations improve without material harm to qualified activation; retain control if inconclusive.
What could muddy the result
Exam seasons, existing collections, Plus promotions, OS permissions, existing screen-time restrictions and campaign audiences can affect behaviour.

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/10

    Recognisable. Not convincing.

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

  5. 5/10Forest is here

    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. Enlarge a complete supported session setup and verify the audience claim.
  2. Show one genuine session outcome with accurately scoped behaviour.
  3. Recapture consistent current controls and make supported access conditions readable.

What would change my mind?

  • Current mode interactions, required permissions and schedule override behaviour.
  • Plan entitlements and dated support for audience and planting claims.
  • Baseline comprehension and scheduled-block activation by visitor intent.
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 Forest. 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.