<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Development - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Development Articles feed</description>
    <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=Development-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>Mobile</category>
      <category>Africa</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=Development-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>
    <item>
      <title>Article: Multi-Cloud FinOps: an Engineering Framework for Cross-Cloud Cost Optimization</title>
      <link>https://www.infoq.com/articles/multi-cloud-finops-cost-optimization/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/multi-cloud-finops-cost-optimization/en/headerimage/multi-cloud-finops-cost-optimization-header-1792499448017.jpg"/&gt;&lt;p&gt;Multi-cloud flexibility comes with hidden egress costs driven by service placement and communication patterns. This article applies Backend FinOps to cross-cloud architecture, covering cost visibility through FOCUS, workload placement, synchronization models, and CI/CD-integrated cost governance. A controlled experiment shows architecture changes saved far more than rate negotiation alone.&lt;/p&gt; &lt;i&gt;By Vivek Arora&lt;/i&gt;</description>
      <category>Cost Optimization</category>
      <category>Cloud</category>
      <category>Cloud Computing</category>
      <category>FinOps</category>
      <category>Architecture</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 23 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/multi-cloud-finops-cost-optimization/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Vivek Arora</dc:creator>
      <dc:date>2026-10-23T11:00:00Z</dc:date>
      <dc:identifier>/articles/multi-cloud-finops-cost-optimization/en</dc:identifier>
    </item>
    <item>
      <title>Article: Distributed Spring Batch without a Message Broker</title>
      <link>https://www.infoq.com/articles/spring-batch-without-broker/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/spring-batch-without-broker/en/headerimage/Distributed-Spring-Batch-Without-a-Message-Broker-header-1792419294298.jpg"/&gt;&lt;p&gt;Distributed Spring Batch partitioning already needs a shared, persistent job repository. This article makes that database the whole coordination plane and drops the message broker, sizing work to the live node count, a per-job master with no standing coordinator, compare-and-set claiming that prevents double-execution, two-phase heartbeat failover, and where a broker is still the right choice.&lt;/p&gt; &lt;i&gt;By Janardhan Reddy Chejarla&lt;/i&gt;</description>
      <category>Data Partitioning</category>
      <category>Spring Batch</category>
      <category>Java</category>
      <category>Messaging</category>
      <category>Distributed Systems</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 21 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/spring-batch-without-broker/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Janardhan Reddy Chejarla</dc:creator>
      <dc:date>2026-10-21T09:00:00Z</dc:date>
      <dc:identifier>/articles/spring-batch-without-broker/en</dc:identifier>
    </item>
  </channel>
</rss>
