<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Crashlytics on</title><link>https://thomaskioko.me/tags/crashlytics/</link><description>Recent content in Crashlytics on</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 28 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thomaskioko.me/tags/crashlytics/index.xml" rel="self" type="application/rss+xml"/><item><title>Adding Firebase Crashlytics to a KMP Project Using Dependency Inversion</title><link>https://thomaskioko.me/posts/kmp-firebase-crashlytics-dependency-inversion/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><guid>https://thomaskioko.me/posts/kmp-firebase-crashlytics-dependency-inversion/</guid><description>Crash reporting is one of those things you don&amp;rsquo;t think about until your app is in production and users are hitting issues you can&amp;rsquo;t reproduce. I recently added Firebase Crashlytics to TvManiac, a Kotlin Multiplatform project that targets both Android and iOS. The project already had a Logger interface backed by Kermit, used across the app for console debugging. The goal was to layer crash reporting on top of that without touching any of the existing consumers.</description></item></channel></rss>