<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Android - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Android Articles feed</description>
    <item>
      <title>Article: The App Is Just the Tip: What It Takes to Build Mobile Infrastructure at Scale</title>
      <link>https://www.infoq.com/articles/mobile-app-infrastructure-at-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Android-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/mobile-app-infrastructure-at-scale/en/headerimage/mobile-app-infrastructure-at-scale-header-1793263251757.jpg"/&gt;&lt;p&gt;What determines whether your app feels fast, ships often, and stays stable at scale is not the app itself. It is what sits behind it. This article is about that layer: what it does, why it exists, what it takes to design it correctly, and what happens when you try to migrate a live, high-traffic product onto it without a safety net.&lt;/p&gt; &lt;i&gt;By Kirill Sokolov&lt;/i&gt;</description>
      <category>Mobile</category>
      <category>iOS</category>
      <category>REST</category>
      <category>Microservices</category>
      <category>API</category>
      <category>Android</category>
      <category>Architecture</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 04 Nov 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/mobile-app-infrastructure-at-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Android-articles</guid>
      <dc:creator>Kirill Sokolov</dc:creator>
      <dc:date>2026-11-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/mobile-app-infrastructure-at-scale/en</dc:identifier>
    </item>
    <item>
      <title>Article: Building an Offline-First AI Coding Tutor for Low-End Android Phones</title>
      <link>https://www.infoq.com/articles/building-offline-first-android-app-low-end-devices/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Android-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/building-offline-first-android-app-low-end-devices/en/headerimage/building-offline-first-android-app-low-end-devices-header-1792571789716.jpg"/&gt;&lt;p&gt;This article is about engineering an offline-first app for low-end devices based on our experience in  Nigeria and India. The interesting problems in this space are storage, quota, cold start, and failure-path design. Our approach applies to any product whose users are on constrained devices and intermittent connections, when the assumption they have a laptop and broadband access do not hold.&lt;/p&gt; &lt;i&gt;By Chidi Nwaogu&lt;/i&gt;</description>
      <category>Africa</category>
      <category>Mobile</category>
      <category>Mobile-first in Africa</category>
      <category>WebAssembly</category>
      <category>Android</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 28 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/building-offline-first-android-app-low-end-devices/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Android-articles</guid>
      <dc:creator>Chidi Nwaogu</dc:creator>
      <dc:date>2026-10-28T09:00:00Z</dc:date>
      <dc:identifier>/articles/building-offline-first-android-app-low-end-devices/en</dc:identifier>
    </item>
  </channel>
</rss>
