ASO AgencyWork directly with Gabriel
App store screenshots. Give people a reason to install.
Your screenshots are a sales argument squeezed onto a phone. A row of tiny interfaces with “powerful features” above them is a remarkably expensive way to say nothing. I review the sequence, sharpen the message and prepare a creative brief and test plan your team can use.
The outputs, fee and handover agreed upfront. Work directly with Gabriel.
The diagnosis
Is this where your listing hurts?
People reach the listing, but the screenshots make them work to understand the app. Use this project to review the opening promise, sequence and supporting proof. Store data helps decide whether conversion is the constraint; the pictures alone cannot establish that.
Tell me what’s going wrong ↗The handover
What lands besides the invoice
An annotated review of the agreed icon, screenshots and product message
A prioritized screenshot sequence with the job of each frame
A creative brief naming the proposed change and required product proof
A test plan covering the audience, metric, owner and next decision
We agree the stores, markets, outputs and review rounds before work starts.
The actual work
Diagnose. Fix. Hand it over.
Review the decision to install
Examine the message, screenshot order and product evidence. Consider acquisition-source differences and identify the uncertainty the next change should resolve.
Write the creative hypothesis
Define control and proposed treatment, what changes and what stays constant. Agree the responsibilities for design, implementation and platform setup.
Interpret the evidence
Document the metric, result guidance and possible decisions before launch. Treat inconclusive results honestly and keep the learning in a reusable test log.
Inside the work
A deliverable, not a séance.
Illustrative hypothesis: show the core workflow in the opening screenshot so first-time visitors understand the task the app helps them complete. The hypothesis must be tested in its actual audience.
An illustration of the work. Your project starts with your own app and evidence.
Before the invoice
The work, the fee and the exit.
I’ll agree the deliverables, responsibilities, fee and schedule with you before work begins. A focused project is fine. Monthly management is optional.
Creative production and hands-on experiment operation depend on the agreed engagement. A particular conversion lift or test duration is never guaranteed.
What to send me
- Current listing assets and target audience
- Available conversion evidence with metric definitions
- Design/implementation capacity and planned releases
The small print, readable
Questions before we start
Will I get new screenshot designs?
The project can provide the message, sequence and creative brief. Final design production is included only when explicitly agreed.
Can you help without enough traffic for an A/B test?
Yes. We can review clarity and accuracy, then document what remains a hypothesis. That does not establish a measured conversion lift.
How long will a screenshot test take?
It depends on eligible traffic, treatments and the effect being investigated. We plan the review rules rather than promise a winner by a fixed date.
Do I need to give you console access?
A public listing review can start with a URL. Performance diagnosis needs relevant reports or agreed access. We decide what is needed for your question before the project starts.
Your turn
Get my screenshot review scope
Your store link and main question are enough to start. Include the priority market if you know it.
I’ll recommend a starting point and explain the scope, fee and information needed. No account-manager relay race.