There's a lot of Matter Cast that feels fairly reasonable as a protocol, but the flaws here are so wildly absurd. I want this effort to sink so bad. As a protocol I vastly prefer Open Screen Protocol, which was begat to support W3c Secondary Screen wg's Presentstion API.
https://w3c.github.io/openscreenprotocol/
https://www.w3.org/TR/presentation-api/Matter Cast has what to me are grevious limitations:
1. Connecting clients can only talk to existing Endpoints running on the target device. If I use Tidal for example, the smart speaker or smart TV needs to already be setup with that app, and needs to be willing to let a background service run & register itself with the platform.
https://github.com/project-chip/connectedhomeip/blob/master/...
2. Only native apps are supported. There's no protocol to say open a webpage & control that. As a solo dev I can throw together a universal Presentation API multi-display experience in hours. Shipping even one native app would take many weekends & lots of legal hoops. Getting on the apps store for even 50% of TV's or speakers seems daunting beyond imagining.
3. No support for multi-party sessions. Only one user can interact at a time.
4. No support for the Web's Presentation API. Since it's not based around urls & web pages, it would require lots of additional work to make it support the standard web pages have to spawn a remote display.
By compare, Open Screen Protocol lets any target device open any web page, which is very similar to how Chromecast development works today (and how DIAL worked before). Whether the target device is Android, Apple, WebOS, Windows, Tizen, or other, the expectation that I could Open Screen Protocol cast to it remains the same. Where-as Matter Cast requires a native app on the device & the app has to be installed & potentially even greenlit by the target device platform itself.
OpenScreenProtocol really looks to have it all, & the model is so much more universal. Really wish we saw some device makers pushing for it these days.