Are there plans to port Google's material design components to the web at some point? I understand some of them work for desktop already?

Yes, they'll use skiko to render on canvas. Note that this will come at a cost of bundle size and losing accessability.

There are ways to make accessibility work, as it does in android and very recently in flutter too. Bundle size is going to be a big problem. Might make compose for web unusable.

Thanks for the info, Martynas

You mean DCE?

DCE is already in place for JS. Using the Google Closure Compiler the size can be reduced further (~25% in my experience) but it's still going to be multiple megabytes

...or maybe it's time for us to think beyond JavaScript? 🤔 https://developer.mozilla.org/en-US/docs/WebAssembly/Caching_modules

How much smaller? Downloading 2MB of dependencies, even first time only, is still a problem.

Not necessarily - It depends on the use-case. If you're dealing with high-volume consumer facing webpage, it may be an issue. However if I have a business web-application for a more targeted audience, and it caches after the first 2MB download (which anyway is going to happen in <5s on modern 4G/5G connections) then it's still a viable solution IMO. It's easy to balk at the size some web-pages are becoming (I sometimes do); but honestly if it's just an up-front loading cost (showing progress bar) followed by the web-App effectively being 'installed' in the browser cache, then I don't see how this is much different to the Mobile App installation lifecycle - just in the browser. With the richer client-side capability then afforded by Kotlin + Compose, an App built & loaded in this way could end up offering a much better UX overall. That said, I'd hope JB put some thought into how we can structure a WebAssembly App for progressive loading where needed.

Just to add to that, Skia already has a canvas API for WASM...

Do you know when we can receive build with such support? It's days, weeks or rather months?

I'd guess months. Main focus right now seems to be DOM rendering

Ehh good and bad, I hoped it could be easy Android-desktop port to the web, but not having it means quite big amount of work and I cannot decide what to do :D however now I have at least hope to port my app at low cost in the future

Compose android+desktop+web still makes sense IMHO, you're able to share your business logic, networking, view models and even compose effects. The only bits remaining are actual UI layout and that's it.

A 2MB web app is completely in the realm of acceptable I think. Even last year my web team was shipping an 8MB app due to polyfills and support for ie. Honestly, if I can provide a reasonable experience to a user and share code between web, android and desktop, I’m a pretty happy camper.

I have a hunch that this is being worked on more actively than has been let on - probably via Kotlin/JS but perhaps even as a WASM tie-in. It makes too much sense. @Dominaezzz pass me the envelopes; I'm making a prediction that Canvas-rendered 'Material Compose' for Web will get a surprise mention during the 2021 Premier week.

Sealed!

Ooh yeah 😎

I'm waiting for

skiko.ios.enabled=true