Gadget Audit
Home / Methodologies / Smart home
Methodology · version 1.1

Utility with privacy attached

Version 1.1 took effect September 22, 2026. This transparency revision adds the two-score policy; it is not a silent rewrite. It applies to every Smart Home review, guide and comparison on this site.

Version 1.1Effective September 22, 2026Research Desk

01 · Map the ecosystem before the features.

Alexa, Google Home, HomeKit, Matter — routines break at platform boundaries. Compatibility is verified per platform from documentation, not assumed from a logo on the box.

02 · Separate local capability from cloud dependence.

What works with no internet decides whether a device is robust or fragile. Fallbacks — physical keys, local recording, manual switches — are documented, never implied.

03 · Review permissions and data handling as a feature.

Microphone state, video storage location, account requirements and voice-history controls are evaluated alongside performance. Privacy is part of the verdict, not an appendix.

04 · Check the install format against real homes.

Mortise versus deadbolt, wired versus battery, renter versus owner — a device that does not fit the door or the lease does not fit the recommendation.

What we check in smart-home

Ecosystem matrix: which platforms each device genuinely works with, Matter support for future-proofing, and whether a hub is required for full features.

Privacy review: physical mute controls, local versus cloud storage options, voice-history management, and the scope of app permissions requested at setup.

Physical fallbacks: keys, keypads, manual switches and local recording — what keeps working when the cloud, the app or the internet does not.

Installation reality: door prep measurements, wiring needs, power placement and landlord constraints, checked before the recommendation rather than after the purchase.

Outage behavior: which features pause when connectivity drops, stated plainly so readers know what they are depending on before they depend on it.

Maker track record: firmware support longevity and whether account requirements or subscriptions have changed after purchase in the past.

Scoring gate

Hands-on lab-test score: Used exclusively for products the editorial team has physically tested and measured under a documented setup.

Research-based editorial score: Editorial judgment from published review consensus, specification analysis and third-party hands-on reports. It is not a lab result: it follows the article’s relative ranking and cited pros, cons and verdict, and products without an honest differentiating basis are marked Not scored.

Read the two-score policy →

Why versioned and dated

Trust in a review starts before the first product appears — it starts with knowing how the reviewer works. This page is versioned and dated so that standard is checkable, not just claimed.

We practice evidence honesty throughout: sources reviewed are reported, manufacturer claims are labeled, and nothing implies product access or measurements that did not happen. The article receipt is where that honesty becomes visible.