<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Local-First on App Coding</title>
    <link>https://appcoding.com/tags/local-first/</link>
    <description>Recent content in Local-First on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/local-first/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Database-to-Database Sync for Local-First Apps Lives or Dies on Conflict Rules</title>
      <link>https://appcoding.com/database-to-database-sync-for-local-first-apps-lives-or-dies-on-conflict-rules/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/database-to-database-sync-for-local-first-apps-lives-or-dies-on-conflict-rules/</guid>
      <description>&lt;p&gt;Take a field technician who edits a work order on a tablet in a basement with no signal. Upstairs, the office edits the same order from a desk. Both hit save at 10:42 by their own clocks, and one of those clocks is ninety seconds off. When the tablet finds a signal, the sync layer has to produce one order that both people can live with. That decision is the product. Offline-first apps are &lt;a href=&#34;https://appcoding.com/building-offline-first-mobile-apps-is-harder-than-it-looks-and-worth-it/&#34;&gt;harder than they look&lt;/a&gt;, and a large share of the difficulty sits in this one step.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
