Productivity · US iPhone listing

ASO Audit: TickTick

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

TickTick's strongest opening material is a spoken request becoming separate tasks. It arrives third, after the standard all-in-one pitch and a small calendar collage. Lead with the useful demonstration. The adjectives can take a day off.

ASO Audit: TickTick illustration: A voice waveform becomes a clear list of everyday tasks.
Gabriel Machuret in an ASO Guru T-shirt: waiting for the finished result.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationThe useful voice example is buried behind all-in-one waffle.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

TickTick:To-Do List & Calendar

Observed subtitle · 30/30 characters

Task remind, planner,countdown

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

Why this gets 5/10

The structured capture example is doing real work. Keep it prominent. The broader feature tour needs a clearer connection to that useful first action, not another all-in-one slogan. The rest of the opening needs tighter benefit copy, larger detail and a continuous task example. Demonstrate capture, correction and scheduling instead of advertising three departments. Integration artwork should clarify behaviour rather than merely decorate the calendar.

  1. Reason to care

    0/2

    All-in-one productivity partner is a broad category promise. Useful task functionality earns proof credit, but the opener does not establish a specific payoff beyond that slogan.

  2. Product evidence

    2/2

    Speech becomes concrete task cards with editable structure.

  3. Readable at a glance

    1/2

    Small calendars and a long voice bubble dilute readability.

  4. A useful sequence

    1/2

    Tasks, calendar and speech are useful but disconnected examples.

  5. A reason to choose

    1/2

    Structured voice capture is specific; integration logos need context.

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

All-in-one says very little

Look at the original: The interface groups tasks by today and tomorrow with example times.

Why I’m flagging it: Awards and a generic productivity claim delay the useful action.

Brief this change

Lead with a specific capture-to-task benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The calendar is a collage

Look at the original: The image places multiple calendar views alongside recognisable service logos.

Why I’m flagging it: Multiple views and logos make the key interaction small.

Brief this change

Enlarge one scheduling action and state the relevant integration scope.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The good example needs editing

Look at the original: The example maps times, work and fitness lists, and a gym duration into separate entries.

Why I’m flagging it: A long speech bubble makes the transformation harder to scan.

Brief this change

Use a shorter authentic request and readable resulting task cards before Save.

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

TickTick:To-Do List & Calendar

Task remind, planner,countdown

Proposed alternative

TickTick: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.

Retain the name’s core task and calendar coverage and replace the compressed subtitle list with two plain-language jobs. The proposed copy describes activity rather than guaranteed productivity.

The tradeoff: It removes explicit reminder and countdown terms from the subtitle. Those may be valuable queries, so the cleaner wording needs actual search and intent evidence before replacing the current coverage.

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

  1. 01Make the benefit clear

    Proposed headline

    Say what you need to do

    Illustrative layout · verify the real flow

    Put this in the frame: A verified spoken example with multiple tasks, accurate dates and language.

    Why it earns the space: Make task capture concrete.

  2. 02Show useful evidence

    Proposed headline

    Check it before saving

    Illustrative layout · verify the real flow

    Put this in the frame: The real parsed output and available correction controls, with the confirmation action visible.

    Why it earns the space: Set a realistic expectation of review and user control.

  3. 03Move the decision forward

    Proposed headline

    See the plan in your calendar

    Illustrative layout · verify the real flow

    Put this in the frame: The saved tasks in the current calendar view, with access requirements checked.

    Why it earns the space: Connect capture to planning without implying every external calendar syncs the same way.

The test: Does leading with the voice-to-task example improve first-action understanding and qualified 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

Todoist: To Do List & Calendar ↗

Task manager & Reminders

Todoist uses a similar to-do-list and calendar name with task-manager and reminder language.

The lesson: Generic organisation terms provide little creative distinction. TickTick’s specific multi-task capture example can explain its own workflow.

Observed competitor metadata

Microsoft To Do ↗

Capture Tasks & Set Reminders

Microsoft To Do explicitly says capture tasks and set reminders.

The lesson: A concrete action is easy to understand. Show how TickTick handles a real input without asserting it is faster or more reliable.

Observed competitor metadata

Things 3 ↗

Organize your life

Things 3 uses the broad Organize your life subtitle.

The lesson: A broad benefit can support a recognised product, but a current task-to-schedule example is more useful proof for someone comparing unfamiliar tools.

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 reminders

Visitor’s job: Capture obligations and remember when to act.

Evidence: The observed name, subtitle and opening inbox all support task management.

Decision: Keep this core intent visible; verify reminder permissions and behaviour before making reliability claims.

calendar planner / time blocking

Visitor’s job: See tasks in time and plan a day.

Evidence: The second screenshot shows calendar views, and the voice example includes a duration.

Decision: Verify calendar access, duration controls and integration scope rather than claiming every calendar works identically.

voice task capture / AI task entry

Visitor’s job: Turn a spoken set of instructions into organised tasks.

Evidence: The third frame explicitly demonstrates AI Voice Add and a reviewable output.

Decision: Research whether this example is clear and relevant; do not assume query volume or perfect extraction.

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 2021–2026 accounts were selected for task capture, schedule handoff and day-boundary expectations. They are not a representative productivity study. Current AI behaviour is assessed from the captured creative and needs a walkthrough; these reviews do not validate it. Old pricing and feature requests remain historical.

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

3 August 2026 · 5/5 stars

“add a quick task”

An August 2026 reviewer valued quick task entry and daily scheduling alongside a wider set of features.

What I’d investigate: Verify each current feature and plan separately; the reviewer’s affordability and productivity judgements are personal opinions.

Listing review source · Review ID 14384676280

13 January 2026 · 5/5 stars

“adding a location”

A January 2026 reviewer praised lists and reminders but wanted smoother handling of addresses.

What I’d investigate: Investigate the current task-to-map handoff rather than assuming that the reported copy-and-paste workaround is still necessary.

Listing review source · Review ID 13626833050

16 October 2021 · 4/5 stars

“end of day”

An October 2021 reviewer preferred core tasks and widgets and requested a configurable day boundary.

What I’d investigate: Use this as a scheduling-expectation question, not evidence that the current product lacks a setting or that all users want fewer features.

Listing review source · Review ID 7919700330

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

All-in-one says very little

Awards and a generic productivity claim delay the useful action.

Deliverable: Lead with a specific supported capture-to-task benefit.

Creative brief and current-product check
02

The calendar is a collage

Multiple views and logos make the key interaction small.

Deliverable: Enlarge one supported scheduling action and state the relevant integration scope.

Creative brief and current-product check
03

The good example needs editing

A long speech bubble makes the transformation harder to scan.

Deliverable: Use a shorter authentic request and readable resulting task cards before Save.

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

One test worth running

Does leading with the voice-to-task example improve first-action understanding and qualified conversion?

Audience
Eligible US English iPhone default-page visitors, with separate research among voice-entry prospects and manual-entry planners.
Control
The current 1–2–3 sequence after verifying awards, integration scope and the current AI example.
Treatment
Reorder the same complete frames to 3–1–2, preserving Save, all output details, metadata and later assets; confirm no connected composition is broken.
Method
Reproduce the example and validate access, then use comprehension research and eligible App Store product page optimization. The test compares sequence, not speech recognition or productivity performance.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Participants should recognise the review-and-save step and avoid assuming perfect parsing, automatic reminder delivery or universal calendar access. Track manual-entry comprehension separately.
Decision rule
Predefine useful effect, sample requirement and analysis timing using baseline traffic. Retain control if inconclusive or if a lift depends on mistaken automation expectations.
What could muddy the result
AI feature rollouts, language support, calendar-provider changes and changes in the manual-versus-voice audience mix can affect results.

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/10TickTick 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. Lead with a specific supported capture-to-task benefit.
  2. Enlarge one supported scheduling action and state the relevant integration scope.
  3. Use a shorter authentic request and readable resulting task cards before Save.

What would change my mind?

  • Current AI capture accuracy examples, correction controls and supported access.
  • Calendar synchronisation scope and reminder-permission requirements.
  • Baseline conversion and manual-versus-voice intent research.
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 TickTick. 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.