<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Kotlin on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/kotlin/</link>
		<description>Recent content in Kotlin on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 18:20:00 +0200</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/kotlin/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Android App Architecture: UI, Domain, and Data Layers</title>
				<link>https://www.compilemymind.com/posts/android-app-architecture-ui-domain-data-layers/</link>
				<pubDate>Sun, 19 Jul 2026 23:35:17 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/android-app-architecture-ui-domain-data-layers/</guid>
				<description>&lt;p&gt;An Android architecture is useful when it answers three ordinary questions without a team meeting:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Where does this state come from?&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Who is allowed to change it?&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;How can I test the behavior without starting an emulator?&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The practical answer is usually a UI layer backed by a data layer, with a domain layer only where reusable or complex business rules justify it. The point is not to collect &lt;code&gt;Repository&lt;/code&gt;, &lt;code&gt;UseCase&lt;/code&gt;, and &lt;code&gt;ViewModel&lt;/code&gt; classes. The point is to make state ownership and dependency direction obvious.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
