Methodology

How DuelVS handles data

A comparison site lives or dies on trust. This page explains what happens to a spec before it reaches a table, and where the limits are.

1. Where data comes from

  • Official manufacturer specifications: product pages and datasheets are the primary source.
  • Technical documentation: white papers, spec sheets and official announcements.
  • Verified reviews: cross‑referenced against reputable tech review sites.
  • Product databases: industry‑standard databases with verified information.

2. Verification

  1. Source validation: the data comes from a reliable source.
  2. Cross‑reference: values are compared across sources for consistency.
  3. Unit standardization: every measurement is converted to one unit.
  4. Format normalization: values follow one format per field.
  5. Quality review: flagged or unusual values are reviewed manually.

3. Normalization, with real examples

Normalization is what makes rows line up. In this redesign it’s also visible:

As collectedAs shownRule
Wi‑Fi 6 (802.11ax), Wi‑Fi 5 (802.11ac), Wi‑Fi 4 (802.11n), Wi‑Fi 7 (802.11be)Wi‑Fi 7Lists collapse to the newest supported standard.
4 months ago09/09/2025Sep 2025Absolute dates only. Relative dates go stale.
2160 x 60 fps4K · 60 fpsHuman‑readable video modes.
48 MP & 48 MP48 + 48 MPOne separator, one unit.

4. How comparisons work

Like with like. Comparisons are limited to one category. You can’t compare a phone with a laptop, because they don’t share fields. Every product in a category is described with the same field schema, so any two or three line up row for row.

Comprehensive, then focused. All available specs are shown. “Differences only” hides identical rows, and “Focus” reorders rows by topic. Neither one scores products.

5. Differences vs “better”

DuelVS’s methodology notes that some metrics are better when lower (weight, price) and others when higher (battery capacity). Many aren’t that simple. A larger card isn’t better, a higher TDP isn’t better, and a bigger screen depends on the buyer. So:

  • Every row highlights a difference and states it plainly (“15 g lighter”, “+308 mAh”).
  • A direction label appears only on fields where a preferred direction is defensible. Here’s the full list:
CategoryFieldPreferred
PhoneWeight↓ lower
PhoneRAM↑ higher
PhoneStorage (max listed)↑ higher
PhoneBattery capacity↑ higher
PhoneWired charging (rated)↑ higher
PhoneWireless charging (rated)↑ higher
LaptopRAM↑ higher
LaptopStorage↑ higher
LaptopWeight↓ lower
LaptopBattery capacity↑ higher
Graphics cardVRAM↑ higher
SmartwatchBattery life (claimed)↑ higher
SmartwatchCharge time↓ lower
HeadphonesWeight↓ lower
HeadphonesBattery life (ANC on)↑ higher
HeadphonesBattery life (max)↑ higher
HeadphonesFull charge time↓ lower

Every other field is shown as a difference with no winner. There’s no overall score.

6. How rankings work

Rankings sort products by one objective, measurable metric: battery capacity (mAh), RAM (GB), storage (GB), screen size, resolution, or benchmarks. They sort in the direction that fits the metric. Product pages show where a device sits in its category, for example “#1,024 of 1,439 by battery capacity”.

7. Generated FAQs

FAQs are generated from the data: the metrics with meaningful differences, category context, ranking position, and notable yes/no features. In this redesign every answer quotes the values it’s based on, and the same text appears on the page and in structured data.

8. Errors & corrections

DuelVS aims for 100% accuracy, but mistakes can happen. If you find an incorrect value, tell us and it will be corrected. New products are added shortly after announcement, specs are updated when manufacturers publish corrections, discontinued products stay for reference, and rankings recalculate automatically as products are added.

10. Limitations

Specs don’t tell the whole story. Software, build quality, support and ecosystem all matter. Use DuelVS to understand the differences, then read detailed reviews for the things a spec sheet can’t measure.

Proposed improvements not live

These are design proposals from this redesign. They are not current DuelVS behavior.

  • Field‑level provenance. A source type and last‑checked date on every value.
  • Consistency checks. Flag values that conflict with the product name (e.g. a listed “16 GB” configuration whose RAM field says 32 GB), or sibling products with the same chip but different benchmark scores.
  • Coverage indicators. Separate “not listed for this product” from “not yet collected for this category”.
  • Ranking segments. “Released since 2024”, “Exclude rugged phones”, “Consumer GPUs only”.
  • Public change log. What changed, when, and why.
  • One canonical URL per comparison. The same set of products always resolves to one URL.

← Start comparing