<?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>Android on Vasileios Chroniadis blog</title><link>https://chronvas.github.io/tags/android/</link><description>Recent content in Android 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/android/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><item><title>Dagger2 Presentation</title><link>https://chronvas.github.io/posts/2017-05-16-dagger-2/</link><pubDate>Fri, 16 Jun 2017 00:00:00 +0000</pubDate><guid>https://chronvas.github.io/posts/2017-05-16-dagger-2/</guid><description>&lt;p&gt;I have written a small presentation for developers starting on Dependency Injection frameworks in general, and getting a more detailed view of the basics of Dagger2 for Android&lt;/p&gt;
&lt;p&gt;The presentation is hosted at slides.com and you can view it following this link &lt;a href="https://slides.com/chronvas/dagger-2"&gt;https://slides.com/chronvas/dagger-2&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Realm for Android, pre-populating from Json and extracting the database</title><link>https://chronvas.github.io/posts/2016-08-01-realm-for-android-pre-populating-from-json-and-extracting-the-database/</link><pubDate>Mon, 01 Aug 2016 00:00:00 +0000</pubDate><guid>https://chronvas.github.io/posts/2016-08-01-realm-for-android-pre-populating-from-json-and-extracting-the-database/</guid><description>&lt;p&gt;Scroll to read, or continue reding in &lt;a class="social-btn" href="https://medium.com/@chron.vas/realm-for-android-pre-populating-from-json-and-extracting-the-database-8709a2f8db18" target="_blank" rel="noopener noreferrer"&gt;&lt;i class="fa fa-fw fa-medium"&gt;&lt;/i&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I’ve came across the “hustle” of creating an app that will use Realm, having the database previously populated with data and just include the created database file in the published app, omitting the Json (or any other file) that is being used to populate it.&lt;/p&gt;
&lt;p&gt;Doing so for a “to be published” app saves time (parsing the file and populating a db) and space (omitting the file which used to create the database).&lt;/p&gt;</description></item></channel></rss>