Practice the Device Experience
Practice the Device Experience
Start by listing those separate islands. Test setup, local control, shared control, loss of the internet, a second home admin, and a bridge to an older device. Record which part works directly and which part depends on a vendor or bridge.
Make one row for each product. Name its setup tool, main app, network, trust owner, local control, cloud need, update path, and removal path. Add the exact feature that the shared home action needs. Do not replace a blank with a guess.
Test one new product first. Add it to the first home. Share it with a second admin. Use it from a second platform. Turn off the internet. Remove and add it again. Keep the result for each feature, not just the setup result.
Then test an old product through a bridge. Mark which features the bridge maps and which it does not. Restart the bridge. Remove its cloud path. Check who owns its update. A bridge can help a move, but it can also keep an old trust or service link in the new home.
Write the release claim in narrow words. State the tested products, versions, platforms, features, and failure cases. Add a retest trigger for an update or new admin. This keeps “works with Matter” from becoming a claim that the evidence never proved.
Use one plain home task as the first check. Add a lamp from one maker and a motion sensor from another. Set a rule that turns on the lamp after motion. Run it from each approved home app. Keep the setup and run result for both.
Now change one thing at a time. Add a second admin. Turn off the outside link. Restart the border unit. Update the lamp. Remove and add the sensor. Check that the rule, names, rights, and local path still match the claim.
Try one feature that is not shared. The lamp may have a maker-only scene or effect. Mark it as outside the common claim. Do not call the whole device bad, and do not hide the gap. A clear edge helps people choose the right app or product.
Finish with a home support note. State who fixes setup, the local network, the bridge, the maker cloud, and the common app. Give each fault a first check. Shared use becomes real when the home can recover, not only when setup passes once.