Productivity & AI · US iPhone listing

ASO Audit: Motion

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

3/10The app deserves better.

Motion's opener has AI attached to practically everything, including agents labelled coming soon. That is a roadmap wearing a sales badge. The phone's actual job deserves a clearer introduction than this capability inventory.

ASO Audit: Motion illustration: Task cards connect desktop and mobile scheduling.
Gabriel Machuret in an ASO Guru T-shirt: challenging the ai label.

Gab’s verdict · 3/10Gabriel Machuret

Editorial illustrationAI seven times. A finished mobile job zero times.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 · 29/30 characters

Motion: Tasks & AI Scheduling

Observed subtitle · 29/30 characters

A.I. Time and Project Manager

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

Why this gets 3/10

The task form shows that there is a real product behind the AI language. Start from that. A scheduling app should let me see the schedule, not leave the result to my imagination. A platform claim, navigation hub and task form do not demonstrate scheduling value. Show an task becoming a reviewable schedule, and explain desktop dependencies clearly. Future features should not be carrying today's install argument.

  1. Reason to care

    1/2

    The task and scheduling context establishes a relevant productivity use case, but platform and AI labels make the concrete mobile benefit harder to identify.

  2. Product evidence

    1/2

    A task form appears, but the scheduling result is not demonstrated.

  3. Readable at a glance

    1/2

    Dense lists and full-screen forms dilute readable hierarchy.

  4. A useful sequence

    0/2

    A feature list, hub and form do not complete one task.

  5. A reason to choose

    0/2

    Number-one and productivity language supply assertions rather than demonstrated advantage.

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 roadmap hijacks the opener

Look at the original: The creative is a platform claim and capability list rather than a working phone screen.

Why I’m flagging it: A long AI list includes an unreleased capability instead of phone-level proof.

Brief this change

Replace it with one currently mobile task and a specific benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Navigation is not a productivity result

Look at the original: The phone presents a hub for accessing several kinds of work.

Why I’m flagging it: Recent items and workspaces demonstrate access, not completed work.

Brief this change

Show the same task moving from capture into its scheduling flow.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Scheduled needs a visible destination

Look at the original: The example exposes scheduling inputs and a scheduled-state label.

Why I’m flagging it: Inputs and a status label leave the actual calendar result unshown.

Brief this change

Show the resulting schedule and correction controls, with accurate mobile limitations.

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

Motion: Tasks & AI Scheduling

A.I. Time and Project Manager

Proposed alternative

Motion: AI Task Planner

Your workspace on the go

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

Retain the brand and scheduling-related task category while positioning mobile as access to an existing workspace. The wording fits the companion role described by the publisher.

The tradeoff: Calendar and project-manager terms lose explicit subtitle space. The proposal is a clarity hypothesis, not a finding about search demand; subscription and computer requirements still need visible supporting copy.

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

  1. 01Make the benefit clear

    Proposed headline

    Keep your Motion work with you

    Illustrative layout · verify the real flow

    Put this in the frame: A verified phone workspace with concise current account and companion context.

    Why it earns the space: Qualify the mobile promise before listing every platform capability.

  2. 02Show useful evidence

    Proposed headline

    Update a task’s real constraints

    Illustrative layout · verify the real flow

    Put this in the frame: The actual duration, deadline and priority controls on iPhone.

    Why it earns the space: Explain what information the user supplies.

  3. 03Move the decision forward

    Proposed headline

    Check where the work fits

    Illustrative layout · verify the real flow

    Put this in the frame: The genuine resulting calendar state with the task and fixed events identifiable.

    Why it earns the space: Close the input-to-output loop without guaranteeing that every schedule can be completed.

The test: Does a companion-specific first frame attract visitors with more accurate mobile-use expectations? 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

Structured: Daily Planner Todo ↗

Visual Calendar & Organizer

Structured centres a daily planner and visual calendar.

The lesson: Motion can explain its companion scheduling role without equating a shared calendar category with the same automation or setup requirements.

Observed competitor metadata

Todoist: To Do List & Calendar ↗

Task manager & Reminders

Todoist combines a to-do list and calendar with task management and reminders.

The lesson: Show what happens to a Motion task after its constraints are entered rather than rely on general task-management language.

Observed competitor metadata

TickTick:To-Do List & Calendar ↗

Task remind, planner,countdown

TickTick names lists, calendars and reminders.

The lesson: The task-planning intent overlaps, but a metadata comparison cannot establish that Motion is faster or that the products have identical mobile scope.

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.

AI scheduling / automatic task planner

Visitor’s job: Place work into a calendar using task requirements.

Evidence: The current name and third still support scheduling intent.

Decision: Explain the supported inputs and constraints without promising a perfect day, guaranteed completion or a measured speed gain.

Motion mobile / project updates

Visitor’s job: Access an existing Motion workspace away from a computer.

Evidence: The description explicitly calls the iPhone app a companion, and the workspace and task screens show mobile access.

Decision: Make account, subscription and computer requirements clear before acquisition.

AI meeting notes / work documents

Visitor’s job: Access notes and documents related to work.

Evidence: The first two stills name notes and documents.

Decision: Verify current creation, recording and editing scope on iPhone before treating every platform feature as a mobile acquisition promise.

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 2024 accounts were chosen for schedule adaptation, setup learning and mobile-scope expectations. The short trial is retained and planned integrations are not presented as completed use. Allegations of deliberate targeting or fraud and unverified explanations of the AI system are excluded from factual conclusions.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 18 May 2024–19 September 2024. No sentiment percentage is calculated.

19 September 2024 · 5/5 stars

“to do items shift around”

A September 2024 reviewer valued rescheduling when the day changed and described a recurring payroll task with a completion window.

What I’d investigate: Use the concrete planning job, but do not turn one person’s experience into a deadline guarantee or a measured productivity gain.

Listing review source · Review ID 11739533628

18 May 2024 · 5/5 stars

“like 4 days”

A May 2024 new customer liked prioritisation across client projects while still learning task setup and planning to configure Siri.

What I’d investigate: Preserve the short trial and incomplete setup. Planned Siri use is not evidence they had successfully used that integration.

Listing review source · Review ID 11281245915

14 June 2024 · 2/5 stars

“compared to even the most basic calendar apps”

A June 2024 reviewer criticised the iPhone experience and listed missing or limited calendar, widget and notification features.

What I’d investigate: Treat the list as historical research questions, not today’s feature matrix. Verify the current mobile scope against the publisher’s companion-app description.

Listing review source · Review ID 11378847136

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 roadmap hijacks the opener

A long AI list includes an unreleased capability instead of phone-level proof.

Deliverable: Replace it with one currently supported mobile task and a specific benefit.

Creative brief and current-product check
02

Navigation is not a productivity result

Recent items and workspaces demonstrate access, not completed work.

Deliverable: Show the same task moving from capture into its supported scheduling flow.

Creative brief and current-product check
03

Scheduled needs a visible destination

Inputs and a status label leave the actual calendar result unshown.

Deliverable: Show the supported resulting schedule and correction controls, with accurate mobile limitations.

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

One test worth running

Does a companion-specific first frame attract visitors with more accurate mobile-use expectations?

Audience
Eligible US English iPhone default-page visitors, with research separated between existing Motion customers and people evaluating the product for the first time.
Control
The current opening structure after required corrections to unsupported claims and outdated feature-availability wording. Those corrections precede the experiment.
Treatment
Replace only frame one with a verified mobile workspace task and concise account, subscription and companion context. Keep frames two and three, metadata, pricing and product behaviour fixed.
Method
Verify current requirements with the product team, run task and access comprehension research, then eligible randomized App Store product page optimization. Measure qualification separately; a lower raw conversion rate may reflect clearer requirements.
Primary measure
Correct identification of the mobile role and access requirements in randomized comprehension research; store download conversion is a separate acquisition measure.
Guardrails
Visitors must not assume a standalone phone product, included future agents, perfect rescheduling or guaranteed productivity gains. Analyse existing-customer and new-customer responses separately where measurement supports it.
Decision rule
Predefine the required comprehension improvement, sample size and acceptable acquisition tradeoff using baseline data. Do not choose a higher-converting version that materially misstates mobile scope.
What could muddy the result
Platform launches, subscription changes, desktop campaigns, new AI features and existing-customer traffic can change intent.

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

    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/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. Replace it with one currently supported mobile task and a specific benefit.
  2. Show the same task moving from capture into its supported scheduling flow.
  3. Show the supported resulting schedule and correction controls, with accurate mobile limitations.

What would change my mind?

  • Current mobile capability, subscription and computer requirements.
  • Claim substantiation and task-conflict handling.
  • Baseline intent mix, comprehension and attributable acquisition.
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 Motion. 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.