ASO AgencyProductivity & AI · US iPhone listing
Does their ASO suck?
Listing creative score · first three captured iPhone screenshots
6/10Useful. Still leaving too much unsaid.
Sunsama clearly says the phone is a desktop companion. That honesty helps. The sales sequence then adds a task and reviews a day where that task is absent. A planner should be able to keep track of its own example.
Gab’s verdict · 6/10Gabriel Machuret
One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.
Gab’s take · Five criteria. Two points each.
The task controls and daily plan provide real product evidence. Calling it a desktop companion also helps set expectations. Now connect that honest scope to a useful reason to open the phone app. The creative still needs stronger benefit copy, larger detail and one continuous task example. Show the entered follow-up reaching the plan and desktop. That would sell continuity more clearly than another whole-screen miniature.
Companion positioning gives existing desktop users a relevant mobile-use context. The specific on-the-go benefit needs a clearer example.
Task inputs and daily planning provide concrete functional evidence.
Repeated purple frames and small interface text reduce impact.
Capture leads to review, but the entered task disappears.
Desktop continuity is specific and partly demonstrated.
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
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
Look at the original: Desktop and mobile views are shown together under an explicit companion label.
Why I’m flagging it: The device pairing does not highlight a useful handoff.
Show one mobile-to-desktop task continuation with a concise benefit.
What the visitor sees → what I’d change
Look at the original: The frame exposes concrete task input fields and a submission action.
Why I’m flagging it: Useful duration and time inputs compete with a full keyboard.
Enlarge the relevant capture controls while keeping the example readable.
What the visitor sees → what I’d change
Look at the original: The screen shows reviewing a day’s work, but the task from frame two is absent.
Why I’m flagging it: The reviewed day does not contain the preceding follow-up.
Use the same task and show its actual scheduled or reviewed state.
Proposed copy for discussion. These are not current listing fields or tested winners.
Observed listing
Daily planner
Proposed alternative
Your desktop plan, on the go
Name 22/30 · Subtitle 28/30 charactersKeep the brand and clear planning category while using the subtitle to reinforce the companion relationship already stated in the creative.
The tradeoff: Generic calendar and task keywords receive less space. Validate existing-customer intent versus new-service interest before rollout, and keep metadata fixed during the task-result test.
Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from Sunsama or tested results.
Proposed headline
Put this in the frame: The verified desktop-and-phone relationship with the actual setup prerequisite.
Why it earns the space: Set the right scope before installation.
Proposed headline
Put this in the frame: The current mobile add flow with one realistic sample task.
Why it earns the space: Make the input understandable.
Proposed headline
Put this in the frame: The actual resulting plan showing that same task and its real time or unscheduled status.
Why it earns the space: Complete the workflow without inventing automatic scheduling.
The test: Does showing the newly added task in frame three improve understanding of the mobile companion workflow? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.
Bring the listing. I’ll help you decide what to keep, what to fix and what to test.
Observed competitor metadata
Task manager & Reminders
Todoist names tasks, calendars and reminders.
The lesson: Sunsama can be precise about its desktop-led planning companion rather than imply all task managers share the same setup.
Observed competitor metadata
Task remind, planner,countdown
TickTick also presents a to-do list and calendar with reminders and planning.
The lesson: The familiar category makes workflow proof more useful than adding another broad productivity claim.
Observed competitor metadata
Visual Calendar & Organizer
Structured emphasises a visual calendar and daily organisation.
The lesson: Show the concrete mobile handoff from the desktop plan; visual planning alone does not explain Sunsama’s role.
Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.
Visitor’s job: Access an existing Sunsama plan away from a computer.
Evidence: The first screenshot and description explicitly define the companion role.
Decision: Protect branded companion intent and make desktop-first setup visible.
Visitor’s job: Review tasks alongside commitments for a day.
Evidence: The subtitle and third screenshot directly support reviewing a daily plan.
Decision: Explain the current mobile scope without treating older desktop-focused praise as proof of every phone capability.
Visitor’s job: Record an incoming task and place it in a plan.
Evidence: The second still shows task text, timing fields and an Add action.
Decision: Demonstrate the resulting task and verify sync; do not introduce AI scheduling claims from user feature requests.
The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.
Three 2024–2025 accounts were selected for companion scope, explicitly desktop-focused feedback and integration expectations. One five-star rating conflicts with its written explanation. Other reviewers’ AI requests and clinical interpretations are not adopted as implemented features or proven benefits.
Sample: 3 selected accounts from 8 displayed reviews. Dates: 14 April 2024–17 January 2025. No sentiment percentage is calculated.
17 January 2025 · 4/5 stars
“companion to the desktop”
A January 2025 user explicitly valued the companion role while reporting recent calendar-sync delays or mismatches.
What I’d investigate: Preserve both the intended scope and reported problem. Test current sync rather than infer a continuing defect from one account.
Listing review source · Review ID 121968667649 October 2024 · 5/5 stars
“I’m not reviewing the mobile app”
An October 2024 reviewer explicitly said most planning happened on desktop and phone use was mainly checking the schedule.
What I’d investigate: Keep that limitation visible. Their broader productivity and stress claims are not evidence of mobile capability or measured outcomes.
Listing review source · Review ID 1181631642514 April 2024 · 5/5 stars
“prevents me from giving it a five star review”
An April 2024 trial user praised the planner while asking for iCloud calendar integration and different sign-in options; the displayed rating is five stars despite that wording.
What I’d investigate: Preserve the star-text conflict. Verify today’s integrations and authentication directly instead of treating requested options as current missing features.
Listing review source · Review ID 11158425510A 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.
The device pairing does not highlight a useful handoff.
Deliverable: Show one supported mobile-to-desktop task continuation with a concise benefit.
Creative brief and current-product checkUseful duration and time inputs compete with a full keyboard.
Deliverable: Enlarge the relevant capture controls while keeping the example readable.
Creative brief and current-product checkThe reviewed day does not contain the preceding follow-up.
Deliverable: Use the same task and show its actual scheduled or reviewed state.
Creative brief and current-product checkDoes showing the newly added task in frame three improve understanding of the mobile companion workflow?
Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.
1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up
The basics need a serious rethink.
Too many obvious things have been left unfinished.
There is a useful product here. The listing needs to show it.
Some basics work, but the opening wastes attention and under-explains the benefit.
There is usable creative here, but too much of the sales argument is left to the visitor.
Real strengths, undermined by meaningful gaps in the opening story or execution.
A clear, useful demonstration with specific refinements still needed.
The main promise is clear and supported. Refinement matters more than reinvention.
Clear positioning, thoughtful choices and very few loose ends.
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.
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 Sunsama. Read our editorial methodology.
Your app. Your priorities.
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.
Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.
