How directory listings are prepared
A listing answers what an app does, who might investigate it, and what to check before choosing. It must identify an actual product and link to its official website.
Sources and check dates
Use the vendor’s official product information for identity and general purpose. Record the source URL and the date checked. Verify individual prices, plan limits, platforms, and availability against the relevant current documentation before stating them as facts. A check date describes the stated check; it is not a promise of continuous monitoring.
Documentation and testing
The catalog’s initial profiles are documentation-based. A hands-on review requires a recorded task, plan, platform, date, and observed result. Vendor claims, our observations, and editorial suggestions must remain distinguishable. A security page or a badge is not our own security assessment.
Comparison and alternatives recommendations
Use one primary article for each named comparison and link to it from hubs and profiles. Explain the reason to choose each option, the restriction that can rule it out, and the evidence behind the recommendation. A proposed test is not an observed result. Worked examples must identify hypothetical inputs; do not turn illustrative arithmetic into product performance.
An alternatives guide may include additional officially sourced products beyond the profiled catalog when they answer a distinct replacement need. State that selection scope, link to the official sources, and avoid implying that every named product has a profile or has been tested. A shortlist is not an exhaustive market ranking.
Inclusion and order
Include software with a clear purpose and a verifiable official product page. Place it in the category matching its principal job and explain meaningful overlap in copy. Use alphabetical order rather than an unexplained score or popularity claim. Exclude duplicates, impersonation, and records with unsupported identity or descriptions.
Unknown or changing details
Omit unsupported fields rather than invent a number. If an app changes purpose, closes, or loses a verifiable source, recheck the record and correct or remove the affected claims. A material correction should identify what changed and when; a routine wording edit needs no invented correction history.
Commercial separation
The checked-in listings contain direct official links without referral parameters or paid ordering. Any commercial relationship must be visibly disclosed on the affected surface and must not silently change eligibility or ordering.
Editorial policy · Disclosure · Corrections and suggestions
Ranker.dev is an independent software directory and publication. It is not affiliated with Ranker, Inc. or ranker.com.