ASOPROFESSIONALLET’S TALK ↗

THE ASO PROFESSIONAL FIELD GUIDE / ASO for new apps

NO HISTORY.
STILL NEED A REASON.

Plan ASO for a new app using product evidence, audience hypotheses and a reviewable launch listing when performance history is not yet available.

GET INTO THE DETAIL ↓
Gabriel Machuret working through app strategy and implementation priorities
GABRIEL MACHURET / ASO IN PRACTICE

MAKE THE THINKING VISIBLE

Separate facts from assumptions before launch.

Swipe horizontally to compare all columns →

Illustrative editorial review
Evidence statusExampleNext action
Known product factThe current app saves receipt imagesDemonstrate the actual workflow
Audience hypothesisTravellers may want trip foldersResearch the intended task and language
Unknown performanceNo live acquisition historyDefine the first measurement plan

Illustrative planning framework, not client results, a ranking forecast or a universal schedule.

01

Start with what the product can prove.

A new app lacks acquisition history, but it still has a product, an intended user and a supported task. Document those facts before selecting search terms. Separate released capabilities from roadmap ideas so the listing can make an accurate promise.

Use value proposition guidance to define the outcome and the interface evidence behind it. Lack of data is not permission to invent a result or borrow a competitor’s positioning.

02

Research intent without pretending it is validation.

Collect candidate language around the user’s task and inspect relevant alternatives. Record sources, ambiguity and product-fit decisions. This produces a better starting hypothesis, not proof of future demand.

Use seed research and relevance checks. Keep estimates visibly separate from observed app performance, which does not yet exist.

03

Prepare a coherent launch listing.

Connect metadata and screenshots around one clear audience promise. Each frame should demonstrate a useful part of the product rather than repeat a slogan. Assign someone to verify the final text and exported assets.

Follow the screenshot narrative and keep an approved version. Check the intended store and language context rather than assuming a single asset bundle fits everything.

04

Define what launch evidence will mean.

Choose the source reports, metrics and audience filters your team will review. Record release and campaign activity so the first observations are interpretable. Early movement may be noisy or shaped by who first hears about the app.

Use KPI definitions. Avoid treating an initial spike or a quiet first week as definitive validation of the entire listing strategy.

05

Plan the first learning cycle.

Set a review point with enough context to make a useful decision, rather than promising a universal ranking deadline. Decide what would trigger a correction, further research or a focused creative test.

Use the 90-day roadmap as a planning structure. New evidence should update the next action; it should not be squeezed into the original launch story.

CLEAR UP THE DETAILS

Common questions.

Can I do ASO before launch?

Yes. Product positioning, research, metadata and creative preparation can begin before performance data exists.

Should I copy a successful competitor?

Use competitors for context, not as proof that their positioning will work for your product.

How quickly should a new app rank?

There is no universal deadline or guaranteed position. Define a practical release and evidence-review plan.

FOLLOW THE NEXT QUESTION

Keep learning.

PUT IT TO WORK ON YOUR APP

Want a second pair
of experienced eyes?

Explore the scope, deliverables and process before starting a conversation.

ASO SERVICES ↗