Who writes and reviews our articles
Every article is written by an ASO practitioner and reviewed by our founder before it publishes. We don't outsource our content to writers who have never optimized a store listing. When a post draws on first-hand work, we say so plainly and mark it as our own experience rather than dressing it up as universal fact.
How we source statistics
Every public statistic we cite carries three things: the year it refers to, an inline citation naming the publisher and the specific report, and a link in the article's Sources list with the date we retrieved it. If we can't trace a number to a credible source, we don't publish it. We never invent figures, round vague claims into false precision, or cite a statistic we haven't read in context.
What sources we trust
We prioritize primary and authoritative sources in this order: official documentation from Apple and Google first; then established ASO data providers and analytics platforms; then reputable industry publications. Where a claim is an estimate or an industry consensus rather than a hard measurement, we label it as such instead of presenting it as settled fact.
How we handle our own experience
Some of the most useful things we know come from running campaigns, not from a report. When we share those, we frame them honestly as patterns we've seen across the apps we've worked on — not as guarantees. We don't name clients or share their data without permission, and we don't generalize a single result into a promise about your app.
How often we update
App store algorithms, character limits, and featuring rules change, and stale ASO advice is actively harmful. We review our cornerstone articles regularly and revise them when the stores change or better data emerges. Each post shows a published date, and substantive revisions update the modified date in its structured data.
Corrections
If you spot an error, tell us and we'll fix it. We'd rather correct a number quickly than leave a wrong one standing. Email hello@asoagency.io with the article and the issue, and we'll review it.