Methodology
AppDiscovery publishes factual app profiles and discovery pages from the currently available public record. This page explains how those records are assembled and where their limits are.
What AppDiscovery publishes
AppDiscovery publishes app detail pages, comparison pages, category hubs, platform hubs, regional hubs, collection pages, developer pages, and machine-readable exports. These surfaces summarize the current published app profile, version history when available, supported platforms, pricing, privacy fields, ranking context, and linked source destinations.
How records are assembled
Records are assembled from the site's published catalog and normalized before they are rendered into HTML, JSON-LD, and API exports. Store links, source URLs, screenshots, publisher websites, and privacy-policy URLs are filtered so the public output reflects supported, typed destinations instead of raw unreviewed fields.
- Official store links are preserved when they match the listed platform or source store.
- Publisher websites are excluded when they duplicate store listings or source links.
- Screenshots are only exposed when they resolve to plausible public media URLs.
- Verification and review labels are shared across page HTML, JSON-LD, and exports.
How discovery pages are selected
Regional, platform, and category hubs are only expanded when they pass internal inventory thresholds. This keeps AppDiscovery focused on surfaces with enough underlying app coverage to be useful, distinct, and maintainable.
Editorial boundaries
AppDiscovery does not claim to host install files and does not publish unverifiable hands-on reviews for every listing. Trust, privacy, version, and ranking fields are presented as profile metadata from the published record. Short summaries and comparison copy are meant to help navigation, not replace the underlying source materials.