How we write our fieldnotes.
Useful coverage starts with saying what we know, how we know it and what we have not checked.
Research reviews and hands-on reviews
Research reviews use official developer documentation, genuine store listings and other identified primary sources. They do not represent device testing. Any future hands-on review must identify the tested device or computer, relevant version, testing date and limitations. We do not invent scores, performance measurements, screenshots or download counts.
What our articles explain
We consider documented features, supported platforms, pricing model, account requirements, connectivity and material limitations. Editorial opinions are judgments based on the evidence described. Prices and availability can vary by region and change after a source check.
Events and release schedules
Event briefings identify the official announcement, affected platforms, region, scheduled dates and timing information when supplied. Announced and tentative schedules are distinguished. Dates are a snapshot of the source check, not a guarantee that an organizer will keep the schedule. Check the official source before making plans.
How we check coverage
We compare product claims with the sources cited in each article, distinguish documented features from editorial opinion, and identify important limitations. A source-check date shows when that information was reviewed. It does not mean we tested the product on a device.
Corrections and commercial independence
Use the contact page to flag factual errors or broken official links. Include the article address and supporting evidence. Material corrections should explain what changed. Sponsorship, review copies and affiliate relationships must be disclosed in affected coverage; payment does not purchase a favorable verdict.