<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Compose Multiplatform on Vasileios Chroniadis blog</title><link>https://chronvas.github.io/tags/compose-multiplatform/</link><description>Recent content in Compose Multiplatform on Vasileios Chroniadis blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chronvas.github.io/tags/compose-multiplatform/index.xml" rel="self" type="application/rss+xml"/><item><title>From Android-Dependent to Platform-Agnostic - The 3 Modern Android Library Categories</title><link>https://chronvas.github.io/posts/2026-7-16-from-android-dependent-to-platform-agnostic-the-3-modern-android-library-categories/</link><pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate><guid>https://chronvas.github.io/posts/2026-7-16-from-android-dependent-to-platform-agnostic-the-3-modern-android-library-categories/</guid><description>&lt;p&gt;Over the past decade of building Android libraries, I’ve realized they differ not just by what they do, but by &lt;strong&gt;how tightly they’re coupled to the Android OS&lt;/strong&gt;.&lt;/p&gt;
&lt;figure&gt;
&lt;a href="https://chronvas.github.io/img/android-to-kmp.png"&gt;&lt;img src="https://chronvas.github.io/img/android-to-kmp.png"&gt;&lt;/a
&lt;/figure&gt;
&lt;p&gt;When designing or choosing a library today, understanding this level of coupling is crucial. Historically, libraries fell into two buckets. Thanks to &lt;strong&gt;Kotlin Multiplatform (&lt;a href="https://kotlinlang.org/multiplatform/"&gt;KMP&lt;/a&gt;)&lt;/strong&gt;, we now have a clear third category.&lt;/p&gt;
&lt;p&gt;Through my own experience, I’ve found it helpful to group these libraries into three main categories, ranked from &amp;lsquo;deeply Android&amp;rsquo; to &amp;lsquo;completely platform-agnostic.&lt;/p&gt;</description></item></channel></rss>