Methodology
We build each page from primary documentation: Google, Apple, Android, Chrome and Firebase developer pages, store policies, regulators and standards bodies. We date what we read, label every example as invented, and say what we did not test.
1. Choose one question per page
Each guide answers one job and each research note one comparison or behavior. Before writing, we check that no other page on the site already targets the same question, so pages do not compete with each other.
2. Read the primary source
We read the platform's own documentation or the regulator's own page, not a summary of it. Quotations are copied exactly and linked. If a page shows a "last updated" date we record it; if not, we write "no date shown". All sources for this edition were read between October 27 and October 28, 2026.
3. Separate documentation from observation
We do not test operators' apps or measure their routes. When a page describes behavior, it is behavior the documentation describes. Code and file samples use example domains, placeholder identifiers and invented values, and are labeled as such.
4. State scope and limits
Every research note opens with a scope box that says what it covers and what it does not. Store policies and platform behavior change; each page shows when it was last updated.
5. Check before publishing
Before publication, each page is checked for exact quotations, correct dates, working links, consistent terminology and the writing rules in our editorial policy. The full source list is on data sources.
6. Review and correct
We recheck pages when a cited source changes or a reader reports an error. Corrections are made on the page and the update date changes.