Still trying to figure out how to talk about our Patchwork project: it's a local-first malleable software system that builds on our past work. It's shadertoy and a markdown editor but it's also a minecraft clone and an ohmjs programming language workbench. It's also none of those things, or more?
Feb 27, 2025 at 4:27 AM
Steven Vandevelde (@tokono.ma)
Looks like what I've been building is quite similar to what the foundation of Patchwork-26 is. Lots of "tiny apps" (atomization of software, loosely coupled) + just the web. Local-first and where everything revolves around the content (data-first, can use preferred UI/view). Happy to see this! 🎉
patchwork-system/core at main · inkandswitch/patchwork-system
Patchwork system. Contribute to inkandswitch/patchwork-system development by creating an account on GitHub.
Local-first Software
Exploring software architecture that returns data to users and enables collaboration in every tool.
Local-first software: pragmatism vs idealism
The Architecture Of Local-First Web Development — Smashing Magazine
An honest perspective on building local-first web apps in 2026, written for developers who’ve been doing this long enough to be skeptical of silver bullets.
Local-First Software Unconference · Luma
On Sat September 23, 2023, immediately following the Strange Loop conference, we are holding a community event for everybody interested in local-first software…
Patch the Planet: a Daybreak initiative to support open source maintainers
OpenAI introduces Patch the Planet, a Daybreak initiative helping open-source maintainers find, validate, and fix vulnerabilities with AI and expert review.
Patchwork Notebook
Internal notes from our ongoing research into soft, softer and softest software
Please
Please is a cross-language build system with an emphasis on high performance, portability, extensibility and correctness.
A Call to Build Models Like We Build Open-Source Software
1 Introduction 2 A brief explanation of open-source software development 3 Community-developed and continually-improved models 3.1 Incremental and cheaply-communicable updates 3.2 Merging models 3.3 Vetting community contributions 3.4 Versioning and backward compatibility 3.5 Modularity and distribution 4 An example future 5 Conclusion
big milestone at the day job where we open sourced Resident, our low-level core tech aimed at hardware device developers: code sandboxes for microcontrollers idea is that end users can infinitely reprogram the products in their home info + GitHub over here... news.inanimate.tech/p/lab-notes-drum-loops-protot…
New thing! @jrcpl.us and I have been exploring home-made software. We made a prototype of a tool for making scrappy little apps for you and your friends. pontus.granstrom.me/scrappy/
Scrappy
pontus.granstrom.meSemble API Project Showcase
An open collection to showcase your projects made using the Semble API
zzstoatzz.io/semble
pdewey.com/semble
Semble Zotero Plugin (by 𝕮) — Semble
pdelfan/semble-mcp
