Loading content…
The amplitude of an app's category-position changes over a rolling window — measured as the standard deviation of daily rank across (typically) the last 30 days. A low-volatility app moves ±1-2 positions per day in a steady channel; a high-volatility app may move ±10-20 positions per day.
Also known as: rank instability, position volatility, rank churn
Volatility is independent from headline rank: an app stable at #4 and an app cycling 2-15 may both have the same 30-day median rank but very different competitive positions. AppRanks surfaces volatility on the trends page and inside the per-app rank history so an operator can tell whether a #5 placement is a defended position or a churning slot. High volatility is usually a signal that the marketplace ranking algorithm is weighing a metric (e.g., very-recent install velocity, freshness of reviews) that the app's underlying signals can't sustain.
Rank volatility separates real competitive standing from coincidence at any given snapshot. The strategic question is rarely "are we #5 today?" — it's "is #5 our defended floor or our peak?" An app whose rank cycles 2-15 is competing on a metric the algorithm rewards transiently (recent installs, freshness); an app stable at #5 is sitting on durable signals (accumulated reviews, install-velocity inertia, badge status). Knowing which condition applies decides whether to invest in acquisition-tactical pushes (for the cycling app) vs moat-deepening work (for the defended app).
AppRanks computes rank volatility as the standard deviation of daily category position over the rolling 30-day window. Days where the app didn't appear in the category leaderboard at all are excluded from the std-dev calculation rather than treated as rank=∞. We display volatility as a raw number alongside the median rank so operators can read both together; the std-dev is rounded to one decimal.