Productivity & AI · US iPhone listing
My take: Whoever did this knows their stuff.
Sunsama gets an important thing right immediately: the first screenshot calls it a desktop companion. The next two show adding a task and reviewing a day. That is a clear, restrained story. I would improve the handoff between those last two frames by showing the newly added task in the resulting plan, while keeping the desktop setup requirement visible.
Actual listing creative · App Store source ↗
One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.
Open the source listing ↗. Public text cannot reveal the private keyword field, search volumes, rankings or conversion rates. The recommendations below are proposals to validate.
What I saw. The first still labels the app a desktop companion and places a phone task list beside a desktop view.
My read. This sets a more accurate expectation than a generic all-in-one planning promise. The description adds that the first day must be planned on desktop.
What I’d do. Keep the companion label and clarify that setup prerequisite in current onboarding and supporting copy.
What I saw. The second still shows a follow-up task, a chosen time, duration, channel and Add action above the keyboard.
My read. The visitor can understand task capture without guessing an invisible automation.
What I’d do. Verify the current mobile fields and capture the actual result after adding that task.
What I saw. The third still shows a daily plan with task times, durations and completed items, but not the newly entered follow-up.
My read. It demonstrates reviewing a plan without closing the action-to-result loop.
What I’d do. Test the same daily view with the verified new task present and its scheduling state explained accurately.
The original creative is preserved. Numbered notes sit beside each frame so observations and recommendations stay separate.
The framing is honest about the relationship but does not itself show the required first-day desktop setup.
Test idea: Retain the scope and state the verified setup requirement without implying mobile parity.
Original image source ↗
This demonstrates capture, but does not prove that an input automatically resolves calendar conflicts or appears immediately everywhere.
Test idea: Trace this exact sample task through the current add flow and verify the resulting state.
Original image source ↗
The example list has useful detail while leaving the input-to-plan connection implicit.
Test idea: Use the real resulting plan with the same added task and truthful calendar context.
Original image source ↗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.
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.
Show: The verified desktop-and-phone relationship with the actual setup prerequisite.
Set the right scope before installation.
Show: The current mobile add flow with one realistic sample task.
Make the input understandable.
Show: The actual resulting plan showing that same task and its real time or unscheduled status.
Complete the workflow without inventing automatic scheduling.
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 review frame does not include the task just added.
Deliverable: A verified same-task third-frame plan.
Low capture effortThe description requires the first planned day on desktop.
Deliverable: A current setup and mobile-scope checklist.
Product verificationA selected account reports calendar delays.
Deliverable: A dated task and calendar sync walkthrough across supported services.
Product researchDoes 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.
Whoever did this knows their stuff. The opening states the mobile role instead of implying full desktop parity, and the next frame demonstrates an actual task input. The remaining gap is continuity: the review screen does not show the follow-up task entered in the previous image. This is a small but useful opportunity to prove the result. A static screen cannot establish sync speed, offline behaviour or every calendar integration.
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.
The essentials are there, but there is little to get excited about.
Good ideas, with a few important gaps still to close.
A strong foundation. Look for specific improvements, not a complete restart.
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.
Bring your listing and the evidence behind it. We can turn a public critique into a prioritized plan for your actual audience.
See what an ASO audit includes →
