What a company publishes
Specs, pricing, release dates, and described features attributed to the manufacturer. This is not an independent test.
What a developer says
An attributed app or accessory claim. We note where and when the developer published it; we do not convert it into a verified result.
What a defined simulation shows
Record simulator, OS, configuration, steps, and limits. A simulator result never implies physical-device fit or behavior.
What we reproduced on hardware
Name the device, OS, app version or accessory variant, procedure, date, reviewer, observed result, and any failed or untested steps.
What people are asking or reporting
Use reports to find questions worth investigating. They are not a compatibility pass, measured failure rate, or representative survey.
What we have not established
Keep the question open. Do not infer success from a press image, old phone, product listing, or a similar-looking accessory.
The test record
Reproducible, or clearly unverified.
Before a hands-on statement is published, an editor records the unit and version, the precise task, expected behavior, result, failures, and evidence media. Another person should be able to understand what was actually checked.
For apps, a test plan can include install and launch, core workflows, outer-to-inner display transitions, layout changes, state continuity, keyboard or pointer input where relevant, and accessibility. We publish only steps we actually performed.
For accessories, a fit plan names the manufacturer, model, variant, and revision. It checks hinge clearance, clasp or adhesive, screen and camera coverage, buttons, ports, charging, magnets, stands, and wear as appropriate. A pass on one variant does not cover every color, revision, or phone case combination.
Minimum record
- Device or exact product variant
- OS, app version, or hardware revision
- Country/region and checked date
- Steps, conditions, and expected result
- Observed outcome and limitations
- Reviewer and source/media record
Image accuracy and rights
Product images must earn trust, too.
We compare product depictions with current manufacturer photos and technical specifications. A real-device depiction must match the published proportions, camera layout, hinge, controls, finish, and screen details. Any AI-generated image needs a recorded fact-check before publication.
If the image cannot be verified or licensed for this site, we use artwork that does not depict a product and link to the manufacturer’s own imagery. A correct-looking image is not automatically a licensed image.
Corrections and updates
Keep the evidence current.
Volatile details, including prices, app versions, stock, compatibility, and software behavior, can change. Substantive changes get a new update date and a short explanation; we do not change dates to make a page look fresh. If a reader identifies an error, the correction is recorded against the affected claim.