# compose-for-web Published articles for compose-for-web. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Compose Multiplatform 1.12.0 Released DevFeed: [Compose Multiplatform 1.12.0 Released]() Original publisher: [Read original article]() Author: Elvira Mustafina Published: 2026-08-26T13:28:41Z Content type: release Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [multiplatform](), [compose-hot-reload](), [MCP Server](), [Model Context Protocol](), [releases](), [Web](), [compose-for-desktop](), [Font]() Tags: [compose-for-desktop](), [compose-for-web](), [compose-hot-reload](), [compose-multiplatform](), [fonts](), [mcp](), [mcp-server](), [model-context-protocol](), [multiplatform](), [releases](), [ui](), [web]() ### AI overview Compose Multiplatform 1.12.0 introduces an experimental MCP server for Compose Hot Reload, enabling AI coding agents to reload applications, inspect rendered UI and semantic trees, simulate interactions, and read logs. The release also adds automatic web font fallback and a more flexible desktop window and dialog API. ### Source excerpt Compose Multiplatform 1.12.0 is out! This version brings new tooling for AI assistants, improvements to web resource management, and finer control over desktop window states. Here are the highlights of this release: For a complete overview of the changes, check out What's new in Compose Multiplatform 1.12.0 or the release notes on GitHub. Get Started [...] ## jetc.dev Newsletter Issue #326 DevFeed: [jetc.dev Newsletter Issue #326]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-11T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [Android](), [compose-for-web](), [debug](), [Design system](), [Testing](), [AI-assisted coding]() Tags: [coding-agents](), [compose](), [compose-for-desktop](), [compose-for-web](), [debugger](), [design-system](), [jetpack-compose](), [testing]() ### AI overview Newsletter Issue #326 covers recent Compose developments, including Places UI Kit discussions, stability considerations, design-system testing, Compose Desktop and Web test bridges, and an Android debugger aimed at coding agents. It also highlights community projects and releases around Compose Multiplatform. ### Source excerpt Why we sometimes still need to think about stability! Compose Desktop/Web test bridge! Android debugger for coding agents! And... Places, everyone?!? ## Listening for element events with Compose for Web - Gustavo Fão Valvassori DevFeed: [Listening for element events with Compose for Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2024-01-26T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-for-web](), [Web](), [draggable](), [Kotlin]() Tags: [browser](), [compose-for-web](), [compose-multiplatform](), [css](), [draggable](), [event](), [kotlin](), [kotlin-js](), [kotlin-multiplatform]() ### AI overview This tutorial explains how to handle HTML element events in Compose for Web. It covers common event listeners, updating composable state from clicks and input changes, and using side effects to implement more complex behavior such as a draggable window. ### Source excerpt In a declarative world, events are the main way to interact with the elements, and most components have a way to listen for them. ## Using CSS libraries with Compose for Web - Gustavo Fão Valvassori DevFeed: [Using CSS libraries with Compose for Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2023-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Compose](), [compose-for-web](), [CSS](), [Webpack](), [Gradle]() Tags: [cdn](), [compose](), [compose-for-web](), [compose-multiplatform](), [css](), [gotchas](), [gradle](), [kotlin-js](), [kotlin-multiplatform](), [npm](), [third-party](), [tips]() ### AI overview A tutorial on importing and using third-party CSS styles in Compose for Web. It explains three approaches: loading styles from a CDN, adding CSS files to project resources, and managing styles with NPM. It also introduces enabling CSS and SCSS support in Webpack through Gradle configuration. ### Source excerpt Using third-party styles have a few gotchas. Here are some tips and tricks to help you out. ## Styling your components on Compose Web - Gustavo Fão Valvassori DevFeed: [Styling your components on Compose Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2023-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-for-web](), [Compose](), [CSS](), [ui](), [web applications]() Tags: [components](), [compose](), [compose-for-web](), [compose-multiplatform](), [css](), [how-to](), [kotlin-js](), [kotlin-multiplatform](), [ui]() ### AI overview This tutorial explains how to style Compose for Web components with CSS. It covers inline styles, reusable stylesheets, custom CSS properties, and element type selectors. ### Source excerpt Styling your UI is a very important part of any application. This article will explore how to style our Compose Web components. ## Getting Started with Compose for Web DevFeed: [Getting Started with Compose for Web]() Original publisher: [Read original article]() Author: Gustavo Fão Valvassori Published: 2023-12-01T21:34:32Z Content type: tutorial Language: en Sources: [Touchlab]() Topics: [compose-for-web](), [Compose](), [Kotlin](), [multiplatform](), [IntelliJ IDEA](), [Gradle](), [HTML](), [Canvas]() Tags: [canvas](), [coding](), [community](), [compose](), [compose-for-web](), [development](), [engineering](), [getting-started](), [gradle](), [how-to](), [html](), [idea](), [inclusive](), [introduction](), [kotlin](), [multiplatform](), [software](), [ui](), [webdev]() ### AI overview A beginner tutorial on building web applications with Compose for Web and Kotlin. It introduces the JS + HTML and Wasm + Canvas runtimes, explains their components and experimental status, and outlines project setup using IntelliJ IDEA, Kotlin Multiplatform, Compose, JavaScript source sets, dependencies, and an HTML entry page. ### Source excerpt If you are a Kotlin developer like me, you are probably very excited about Jetpack Compose. It's a modern UI toolkit for developing apps, and with the great work from JetBrains, it's becoming a really interesting solution. As a mobile developer, I've never gone in the weeds on how to properly develop sites with HTML, CSS, and JS. My closest experience was with React Native back in 2018. But now, with Compose, using a Kotlin DSL, I feel comfortable on doing this. Compose Runtime and Component Library Before creating a project and start coding, it's important to have a small introduction to Compose runtimes. As of now, Compose has two different runtimes on the web: JS + HTML Wasm + Canvas They both use the Compose Runtime underneath, but they use different components. Long story short: The HTML version will have HTML composable components (like H1, P, Span, Input, Div, etc.) The Canvas version will have similar components as the Android version as it uses SKIA to draw on the Canvas. Both of them are experimental. Note that choosing how you want to build your application will impact on possible code-sharing with native if this is what you want. For this series of posts, I'll use the HTML version and I will be able to explore more the web components. Creating the project Now that we know what runtime/components we want to use, we need to create a project. My first idea was to use the KMP project wizard, but unfortunately, the Web target is not available as an option for now. As a workaround, I had to create a new clean project using IntelliJ IDEA and add the dependencies manually. Using a clean template you will reduce the amount of code that needs to be removed/updated to make the project work. But if you prefer to use any other IDE/Template, feel free to do so and share your experience with us later :) With that, the configuration is completed with a few extra lines: Change the Kotlin plugin from JVM to MULTIPLATFORM Add the Compose plugin Declare JS source-sets Impor ## Getting Started with Compose for Web - Gustavo Fão Valvassori DevFeed: [Getting Started with Compose for Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2023-12-01T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-for-web](), [compose-multiplatform](), [multiplatform](), [HTML](), [Kotlin](), [Gradle](), [IntelliJ IDEA]() Tags: [compose-for-web](), [compose-multiplatform](), [cross-platform](), [getting-started](), [gradle](), [how-to](), [html](), [intellij-idea](), [kotlin](), [kotlin-js](), [kotlin-multiplatform]() ### AI overview This tutorial explains how to get started with Compose for Web using its HTML runtime. It introduces the available web runtimes, discusses their implications for code sharing, and describes creating and configuring a Kotlin Multiplatform project with Compose dependencies and an HTML entry point. ### Source excerpt Compose multiplatform is a promising alternative for building cross-platform UIs. In this article, we'll see how to get started with Compose for Web using the HTML version. ## Compose for Web (WASM) - What and Why? DevFeed: [Compose for Web (WASM) - What and Why?]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2023-09-06T02:43:11Z Content type: opinion Language: en Sources: [Handstand Sam]() Topics: [compose-for-web](), [wasm](), [Kotlin Multiplatform](), [Web](), [JavaScript](), [Angular](), [Node.js]() Tags: [angular](), [compose-for-web](), [javascript](), [kotlin](), [kotlin-multiplatform](), [node-js](), [updates](), [wasm](), [web]() ### AI overview An overview of Compose for Web (WASM) in Kotlin Multiplatform, comparing it with Kotlin/JS and Compose HTML. The article discusses browser UI use cases, Kotlin/JS bundle-size tradeoffs, and the potential value of sharing complex business logic across platforms. ### Source excerpt As a former web-developer myself, I still gravitate back to browser-based UIs. They are so easy to access from anywhere, and are globally available. It's hard to argue the utility of the amazing web platform. Compose for Web (WASM) is the latest technology in Kotlin Multiplatform and I'm pretty bullish about it. In this post [...] ## Using Compose Across Platforms - Júlia Jakubcová DevFeed: [Using Compose Across Platforms - Júlia Jakubcová]() Original publisher: [Read original article]() Published: 2022-12-09T15:22:11Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Compose](), [Android](), [iOS](), [compose-for-web](), [Mobile]() Tags: [android](), [compose](), [compose-for-web](), [compose-multiplatform](), [interoperability](), [ios](), [mobile](), [ui]() ### AI overview This article compares using Compose across Android, iOS, Desktop, and Web. It explains how much UI code can be shared, when platform-specific implementations are needed, and how platform components and limitations differ. ### Source excerpt Let's look at the differences you'll encounter when using Compose for different platforms. I have spent more time with some (Android) than the others, but I have experienced how it has progressed from its early states to the current versions. The initial frustration quickly turned into enjoyment. Here are answers to some basic questions you might have such as: How hard is it to set up, use and debug, what is unique for each platform? And what else can Compose be used for? ## When Compose remember cannot forget DevFeed: [When Compose remember cannot forget]() Original publisher: [Read original article]() Published: 2022-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Compose](), [compose-for-web](), [ui](), [color]() Tags: [change](), [compose](), [compose-for-web](), [recomposition](), [state](), [ui](), [update]() ### AI overview This tutorial explains why a Compose composable continued displaying an old value after recomposition in a Compose for Web color utility app. The issue occurred because remember preserves values across recompositions; supplying the changing color value as a key caused the remembered value to update. ### Source excerpt Чытаць на беларускай мове Introduction When developing color-utils app using Compose for Web I faced an issue that remember didn't want to forget the state. It was quite annoying experience as it felt stupid: composable function is recomposed with the new value provided but remember still kept old value. As usual, there is no magic there and the answer is quite simple therefore this article won't be that long. Compose is all about state. In the app I had two levels of state: