<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metro on</title><link>https://thomaskioko.me/tags/metro/</link><description>Recent content in Metro on</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thomaskioko.me/tags/metro/index.xml" rel="self" type="application/rss+xml"/><item><title>Breaking Up a Complex Screen with Decompose</title><link>https://thomaskioko.me/posts/composing-complex-screens-with-decompose/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://thomaskioko.me/posts/composing-complex-screens-with-decompose/</guid><description>This is the first post in a multiple part series on building Tv Maniac&amp;rsquo;s screens and navigation with Decompose. The next two posts will cover navigation and codegen. I&amp;rsquo;ll walk you through how I use Decompose to navigate between screens while keeping screens and features free of navigation logic. Code generation writes all the DI bindings, so adding a new feature and wiring up its navigation stays simple.
Tv Maniac is a Kotlin Multiplatform app that runs on Android and iOS.</description></item></channel></rss>