As I mentioned in the last update, the Kotlin team...

# decouple

[CLOVIS]

As I mentioned in the last update, the Kotlin team has fixed a major bug blocking Decouple recently. The technical aspects are therefore sorted out, it's time for a big cleanup.

I'm searching for people who are interested in design systems and UI kits in general. The objective is to put in place a list of the most common components, and organize them by the reason they are used. In different UI kits, components are often named after what they look like, so it isn't obvious when two components are direct equivalents in terms of user experience. If you're interested in this subject, or know someone who is, please reach out.

The most complicated part of Decouple is, and will remain, the polymorphic component concept. To decrease friction in the future, this concept has been moved to its own module (decouple-core) with proper documentation explaining its objectives and usage.

On the Kotlin/JS side specifically, we have hit the classic issue that resources/assets are not published as part of libraries, and are thus not available to downstream projects. We want to expose default CSS files to users, so we need this feature. We are experimenting with a Gradle-based approach to solve this—but it's not as simple as it seems.

Last but not least, this Slack channel is dedicated to Decouple itself, yet we often end up talking about our other projects, and it doesn't feel like the correct place to exchange about them. We're opening a Discord server to discuss all our projects, even when they are not related to Kotlin or UI development. Please join us 🙂