<?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 VisorCraft News</title><link>https://www.visorcraft.com/news/tags/local-first/</link><description>Recent content in Local-First on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 05 Sep 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/local-first/index.xml" rel="self" type="application/rss+xml"/><item><title>Local-First Apps in 2026: The Case for Offline by Default</title><link>https://www.visorcraft.com/news/2026/09/local-first-apps-in-2026-offline-by-default/</link><pubDate>Sat, 05 Sep 2026 10:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/09/local-first-apps-in-2026-offline-by-default/</guid><description>&lt;p&gt;Somewhere around 2015 the industry quietly redefined the word &amp;ldquo;app&amp;rdquo; to mean &amp;ldquo;a thin shell around somebody else&amp;rsquo;s server,&amp;rdquo; and the redefinition stuck so thoroughly that a piece of software which opens its own files without asking permission from a data center now feels almost eccentric. We did not set out to be eccentric; we set out to build tools that keep working when the Wi-Fi drops, when the vendor sunsets the product, when the account gets locked by an automated fraud system at 2 AM, and the shortest path to all three of those guarantees turned out to be the same one: make the app complete on the machine it runs on, and treat the network as an optional extra rather than a load-bearing wall.&lt;/p&gt;</description></item></channel></rss>