Productivity · US iPhone listing

ASO Audit: Todoist

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

7/10Good. The product proof earns it.

Todoist earns its stronger score by showing input becoming structured work. That is actual product persuasion. It still piles small examples and unfamiliar markers onto tilted screens, then changes the task before the calendar payoff.

Editorial illustration of a tangled task list becoming a clear daily plan, with paper checkboxes, calendar blocks and one highlighted completed task for the Todoist ASO audit.
Gabriel Machuret in an ASO Guru T-shirt: approving the idea while flagging a detail.

Gab’s verdict · 7/10Gabriel Machuret

Editorial illustrationUseful capture proof. The tiny syntax still needs a translator.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 · 30/30 characters

Todoist: To Do List & Calendar

Observed subtitle · 24/30 characters

Task manager & Reminders

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

Why this gets 7/10

Turning typed or spoken input into a structured task is a concrete benefit. That earns its good score. The remaining job is making the notation and result easy to read. Improve readability and follow one task from capture through review into planning. Explain unfamiliar notation and access. It needs refinement, but the evidence does not justify pretending it has the same fundamental problems as an award-only introduction.

  1. Reason to care

    2/2

    Fast task capture gives the opener a concrete benefit.

  2. Product evidence

    2/2

    Speech and typed input visibly become structured tasks.

  3. Readable at a glance

    1/2

    Tilted devices and several floating examples reduce readability.

  4. A useful sequence

    1/2

    Capture-to-planning is coherent but changes tasks before completion.

  5. A reason to choose

    1/2

    Structured parsing is specific; unfamiliar syntax needs explanation.

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 useful capture is crowded

Look at the original: Capture is shown as an action with recognizable task examples.

Why I’m flagging it: Awards and several sample tasks compete with the listening action.

Brief this change

Enlarge one authentic capture and its resulting structured task.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The syntax assumes prior training

Look at the original: Several input examples expose the task syntax and resulting fields.

Why I’m flagging it: Projects, people and priority markers need interpretation.

Brief this change

Show one readable input with plainly labelled field outcomes.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The example changes at the payoff

Look at the original: A calendar view gives project work a time-based context.

Why I’m flagging it: The calendar introduces a different task instead of finishing the capture.

Brief this change

Carry the same task into its planning state and show relevant access context.

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

Todoist: To Do List & Calendar

Task manager & Reminders

Proposed alternative

Todoist: To Do List & Calendar

Capture tasks. Plan your day.

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

The candidate retains the specific category name while changing the subtitle from feature nouns to a simple sequence of jobs.

The tradeoff: It removes the explicit reminders term. Review search evidence and the private keyword field before adopting it; do not assume the more natural sentence will rank better.

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

  1. 01Make the benefit clear

    Proposed headline

    Get the task out of your head

    Illustrative layout · verify the real flow

    Put this in the frame: One verified capture action with a short real task example.

    Why it earns the space: Start with a familiar problem and an immediate action.

  2. 02Show useful evidence

    Proposed headline

    Turn a thought into a plan

    Illustrative layout · verify the real flow

    Put this in the frame: One phrase turning into a date and a task, with no unexplained notation.

    Why it earns the space: Make the parsing benefit legible to a newcomer.

  3. 03Move the decision forward

    Proposed headline

    See what fits into today

    Illustrative layout · verify the real flow

    Put this in the frame: A current planning view with the relevant plan access clearly indicated.

    Why it earns the space: Connect a calendar feature with a practical decision.

The test: Does a simpler parsing demonstration improve understanding and then 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

TickTick:To-Do List & Calendar ↗

Task remind, planner,countdown

TickTick also pairs task lists and calendar language in its name.

The lesson: The category nouns are not the differentiator. Todoist should explain its workflow with clearer product proof.

Observed competitor metadata

Things 3 ↗

Organize your life

Things uses a short brand-led name and a broad organization subtitle.

The lesson: Todoist already gives more literal category context. There is no need to make every competitor match its naming strategy.

Observed competitor metadata

Microsoft To Do ↗

Capture Tasks & Set Reminders

Microsoft To Do emphasizes capture and reminders in its subtitle.

The lesson: Fast capture is a shared job. The demonstration must show why Todoist’s approach feels useful, without making an unsupported superiority claim.

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.

to do list / task manager

Visitor’s job: Capture and organize work that needs doing.

Evidence: Both metadata fields and the first two frames support task management.

Decision: Preserve clear category coverage; avoid stuffing alternate spellings into visible copy.

calendar / daily planning

Visitor’s job: Fit tasks into available time.

Evidence: Calendar appears in the name and the third screenshot.

Decision: Explore a planning-led creative for an appropriate audience, with entitlement checks.

reminders / recurring tasks

Visitor’s job: Stop relying on memory for repeated commitments.

Evidence: The subtitle and a recent selected review mention reminders.

Decision: Use a verified recurring example. Do not turn a reviewer’s personal experience into a health-related claim.

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 of the eight displayed reviews were selected to compare setup value, unpredictable work and everyday task organization. Their text is summarized individually; no frequency or market-wide satisfaction claim is inferred.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 11 May 2024–16 August 2026. No sentiment percentage is calculated.

16 August 2026 · 5/5 stars

“takes a bit”

The reviewer values recurring reminders and flexible task views after an initial setup period.

What I’d investigate: Show the first useful outcome without pretending there is no learning curve.

Listing review source · Review ID 14434569726

11 May 2024 · 2/5 stars

“prepare for Sunday”

An older review describes difficulty with date parsing and a task list that feels poorly suited to constantly changing work.

What I’d investigate: Test comprehension with an ambiguous phrase and a rescheduling scenario. Do not treat this as proof of a current parsing bug.

Listing review source · Review ID 11256821406

18 September 2024 · 5/5 stars

“prioritize items”

The reviewer describes organizing work and personal routines while requesting more control over recurring-item visibility.

What I’d investigate: A personal organization story can be specific without suggesting the product solves every workflow equally well.

Listing review source · Review ID 11738931590

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 useful capture is crowded

Awards and several sample tasks compete with the listening action.

Deliverable: Enlarge one authentic capture and its resulting structured task.

Creative brief and current-product check
02

The syntax assumes prior training

Projects, people and priority markers need interpretation.

Deliverable: Show one readable input with plainly labelled supported field outcomes.

Creative brief and current-product check
03

The example changes at the payoff

The calendar introduces a different task instead of finishing the capture.

Deliverable: Carry the same task into its supported planning state and show relevant access context.

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

One test worth running

Does a simpler parsing demonstration improve understanding and then conversion?

Audience
First-time US English iPhone task-app shoppers in a comprehension study; eligible product-page traffic for a later store test.
Control
The current second screenshot with several parsing examples.
Treatment
One verified input phrase and its resulting scheduled task; retain the visual identity and other frames.
Method
First ask participants to explain what the feature does without coaching. If the concept is understood and product-accurate, run an eligible screenshot experiment in App Store product page optimization.
Primary measure
For the study, unaided explanation of the input-to-result behavior; for the store test, platform-reported download conversion. Keep the two results separate.
Guardrails
Monitor expectations about plan access and input availability. Do not select a concept that wins attention by implying unsupported features.
Decision rule
Predefine the comprehension rubric and study recruitment. Size the later conversion test from actual baseline traffic, with a practical effect threshold and inconclusive outcome allowed.
What could muddy the result
A feature release or plan change can change whether the proposed creative is truthful; verify again before launch.

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/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/10Todoist is here

    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 one authentic capture and its resulting structured task.
  2. Show one readable input with plainly labelled supported field outcomes.
  3. Carry the same task into its supported planning state and show relevant access context.

What would change my mind?

  • Current capture and calendar entitlement documentation.
  • Keyword-field and acquisition evidence before changing the subtitle.
  • New-user comprehension observations.
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 Todoist. 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.