A feature matrix should name the controller and app
A tick beside “compatible” does not tell a buyer enough. For a mixed-brand order, ask which exact controller and platform deliver the listed action, and whether the result is the same as in the manufacturer’s own app.
Specify the action
Replace a broad “smart lighting” row with a specific operation such as adjusting a selected light from a wall control. A functional description makes it easier to verify the proposed combination and identify what the customer will actually receive.
Record the access path
List direct platform support, a required bridge or a separate integration where applicable. Matter certification addresses supported device capabilities; it should not be stretched into an assurance that all features from every app appear everywhere.
Use the matrix for sourcing
Send HomeTech the requested actions and existing platform alongside the device list. This gives a technical sourcing review something precise to evaluate and keeps the order aligned with the buyer’s chosen experience rather than general ecosystem logos.
Before you buy
- Write observable actions
- Name bridge and platform
- Separate native and bridged features