The one framework: identify your controller, then check the one feature you want by name - never trust the label alone

Every question in this cluster comes back to the same fact: a “Matter” or “Matter-certified” label on a box only promises that a device speaks a shared local-network language and can join more than one app. It says nothing about whether the one feature you actually care about - voice-unlocking a door, tap-to-unlock with your phone, a light’s color effects, a camera’s live feed - survives the trip into your specific app. The label is a floor, not a ceiling. Confirming what’s actually on the other side of that floor takes three steps, in order.

Step 1: Name your controller specifically

Not “I use Matter” - “I use Google Home,” “I use Apple Home,” “I use Alexa,” or “I use SmartThings.” Every gap documented in this cluster (Google’s remote/voice-unlock restriction on non-PIN locks, Apple’s Aliro-based Home Key, a light losing its effects on the way into a different app) is a per-platform decision, not a per-Matter one. The same device can behave completely differently depending on which of the four you’re actually running.

Step 2: Check that platform’s own supported-device documentation, not the retailer’s listing

Google, Apple, Amazon, and Samsung each publish their own supported-device-type pages for developers. They’re written for developers, not shoppers - which is exactly why they’re worth the five minutes: they state what the platform actually implements today, not what a marketing page implies. A retailer’s product description will tell you a device is “Matter compatible.” It will not tell you that your specific platform disables one of its features.

Step 3: Go deep on the one device category you’re actually buying

The general framework only gets you so far - the specific gaps are different for every device type. This cluster covers them one category at a time:

• Buying any Matter device and want the core “certified doesn’t mean it just works” case, with the version-gap problem explained? Start with [matter-certified-doesnt-guarantee-compatibility].
• Specifically comparing smart locks? The single biggest surprise - that Apple’s tap-to-unlock isn’t even a Matter feature - plus Google’s PIN-dependent unlock restriction and the manufacturer-app requirement for fingerprint setup, is covered in [matter-smart-lock-features-differ-by-app].
• Shopping for a security camera or video doorbell? Camera support only exists in Matter 1.5 (not 1.4), and as of this writing only one major hub has actually shipped it - see [matter-security-camera-what-to-check-before-buying] for which one, and why even Matter-friendly camera makers sometimes skip it on a specific model.
• Wondering what “Matter 1.4” actually changed? Two concrete setup/sharing improvements, both CSA-documented, not marketing language - see [matter-1-4-smart-home-setup-got-easier].

Who this framework doesn’t fit

If you’re already running Home Assistant or another local automation hub instead of a corporate app, your situation is different - local hubs often expose far more of a device’s native capability, and several restrictions described in this cluster (Google’s lock policy, Apple’s Aliro requirement) may not apply to you the same way. This also isn’t a guide to which single ecosystem to pick overall; that decision depends on which voice assistant and other devices you already own, which is outside what a compatibility checklist can answer.

Where to go next

Three steps, then one companion article per device category: identify your controller, check that platform’s own documentation, then read the specific piece for the device you’re actually buying. Start with whichever category you’re shopping for right now.