<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jetpack Compose on Tai&#39;s Life</title>
    <link>https://taislife.work/tags/jetpack-compose/</link>
    <description>Recent content in Jetpack Compose on Tai&#39;s Life</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 10 Aug 2026 12:54:22 +0800</lastBuildDate>
    <atom:link href="https://taislife.work/tags/jetpack-compose/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Dev] Speed Camera OUT! Building My Own Android Auto Speed Camera Alert App</title>
      <link>https://taislife.work/blogs/speed-camera-detection-alarm/</link>
      <pubDate>Mon, 10 Aug 2026 12:54:22 +0800</pubDate>
      <guid>https://taislife.work/blogs/speed-camera-detection-alarm/</guid>
      <description>&lt;h2 id=&#34;prologue-three-things-i-could-not-stand&#34;&gt;Prologue: Three Things I Could Not Stand&lt;/h2&gt;&#xA;&lt;p&gt;If you drive, this has probably happened to you: your dashcam proudly advertises &amp;ldquo;built-in speed camera alerts&amp;rdquo;, the feature is switched on, and one day a ticket still shows up in your mailbox. The newly installed camera simply was not in the database.&lt;/p&gt;&#xA;&lt;p&gt;After digging into this product category, I found three fundamental problems:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;First, dashcam map data never updates itself.&lt;/strong&gt; The built-in camera database is a snapshot from the day the device left the factory. Updating it means hunting down a file on the vendor&amp;rsquo;s website, pulling out the SD card, and flashing it through some buried menu. Most people never do it even once, so the data stays frozen in whatever year they bought the device.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
