Methodology
How we research and verify a comparison
Every comparison on AppVerdict is built the same way. This page states that process plainly — including what it does not currently involve — so you can judge the coverage on its actual sourcing, not on an assumption about how it was made.
What a comparison is built from
- Official store listings. Each app’s current Google Play listing — description, permissions declared, pricing shown, and the listing’s own rating and review count (usually read directly from the listing’s structured data rather than a rendered number, since rendered prices can be geo-served incorrectly).
- The developer’s own documentation. Support pages, pricing pages, changelogs, and published policies from the app or company itself — the primary source for anything the store listing doesn’t cover in full.
- Independent public research. Security audits, breach disclosures, ownership filings (e.g. SEC/regulatory filings for publicly traded owners), and reporting from established technology publications, used to corroborate or correct anything the vendor itself has an incentive to omit.
What “verified” means here
A fast-changing detail — a price tier, a storage limit, a star rating, an ownership stake — is checked against its live primary source before an article is published or updated. Where an article shows a verification date, that is the date those specific figures were last re-checked against the source, not the date the article was first written. Prices and figures on this site are re-checked on an ongoing basis, not on a fixed public calendar; if you spot a stale number, the fastest fix is reporting it via Contact.
What our articles do and don’t contain
Every factual claim in a comparison — a price, a storage limit, a rating, a policy, a security incident — is checked against a primary source and linked inline, so you can follow it and disagree with us. That is the standard we hold ourselves to, and it is the one you can audit from the outside.
What our articles do not currently carry is original test data: we don’t publish our own benchmark numbers, our own screenshots, or measurements taken on a named device over a stated period. Where a claim would need that kind of evidence and can’t be sourced any other way, we leave it out or flag it as unverified rather than present it as a tested result. If a comparison ever does rest on our own measurements, we will say which device, which build, and on what date.
Corrections
When a sourced fact turns out to be wrong — a price changed, an ownership stake shifted, a feature was deprecated — the article is corrected and its “Updated” date changes. See the full Editorial Policy for how corrections and independence work sitewide, and the author page for who researches and publishes this coverage.