It's worth noting that the current approach for material support is canvas-based. Using canvas means we get good compatibility and interop with other platforms, but comes with some drawbacks (like performance of loading the entire canvas, not being DOM-based impacts SEO and devtools, etc). Depending on your use case, you may still find value in something like kmdc and wrapping HTML/DOM based widgets for use in Compose for Web.

100% of the business use cases that I’ve come up with over the past several years for something like compose-web would be used in place of an authenticated react/angular application. Because it’s behind an auth wall, SEO isn’t a concern. Anything where SEO is a concern, I almost always want a static, or a server rendered page. The one thing that is a concern in a few of the cases though is accessibility. I’m unsure how well compose web canvas would work for accessibility, like screen readers

Could you give us any indication at what timeframe we could expect the first pre-release versions of this technology? Months? A Year?

Aren't they using material-components-web the cousin of material-components-flutter and -android?