Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Love/Hate: Upgrading to Web2.5 with Local-First...

Love/Hate: Upgrading to Web2.5 with Local-First (abbr)

Millions of developers have made their careers in the age of Web2, and most weren't even around for the days of Web1. Yet it's no shocking claim that Web2 still has a lot of problems that weigh it down, despite all the amazing advancements.

For years now, hopes of fixing those problems have largely hung on the promises of Web3 (blockchain and crypto). But just as other classic "version upgrades" (like Python 2 vs Python 3) lingered and stagnated, so too has Web3 largely failed yet to bridge the divide and pull along those of us stuck in Web2.

Big changes are usually the sum of many smaller changes. Web3 is too big a leap for many, so we need to look to more immediate and tangible evolutions.

Luckily, the web has a new way forward. Let's explore how local-first will upgrade the world to Web2.5.

Kyle Simpson

April 03, 2025
Tweet

More Decks by Kyle Simpson

Other Decks in Programming

Transcript

  1. Web

  2. vs

  3. Local-First 1. No spinners: your work at your fingertips 2.

    Your work is not trapped on one device 3. The network is optional Seamless collaboration with your colleagues The Long Now Security and privacy by default You retain ultimate ownership and control https://www.inkandswitch.com/local-first/ https://localfirstweb.dev/
  4. ▪ Not just data, though ▪ The app itself should

    act installed and remain persistently on the device, and should update atomically (IWA) Local-First
  5. 1. Your public-key is your identity 2. Local data protection

    (encryption at rest, E2E transmission) 3. Keys protected by biometric passkeys Zero-Server Identity
  6. 1. Local Identity 2. Surf To Install (PWA, IWA, etc)

    3. Peer-First / Server-Last (Direct Sockets, LP2P, etc) Web2.5 Steps
  7. ▪ Autonomous, user-defined identity ▪ Data ownership ▪ Users locally

    mix/share their own data across apps ▪ App ownership ▪ Reduce distinctions between web, apps, and data Web2.5 Principles