In the Vibe Coding Era, Why We Need RSS to Share Personal Apps

When Building Apps Becomes as Simple as Writing a Blog Post

With the rise of AI-assisted programming (what everyone's calling "Vibe Coding"), an interesting phenomenon is emerging: more and more developers are rapidly building large numbers of small tools and micro-apps. These applications are highly personal, context-specific, and produced at an extremely high frequency. Matt Webb recently raised a thought-provoking idea—we need an RSS-like mechanism for sharing these "abundant" vibe-coded applications.

The term Vibe Coding was first coined by Andrej Karpathy (OpenAI co-founder and former Tesla AI Director) in February 2025. He described an entirely new way of programming: instead of writing code line by line, developers describe their desired functionality in natural language, and large language models (the models behind tools like Claude, GPT-4, Cursor, etc.) generate complete code implementations. The developer's role shifts from "writer" to "guide" and "reviewer"—you just need to describe the "vibe," and AI handles turning it into working software. This paradigm dramatically lowers the barrier to software development, enabling non-professional programmers to build fully functional applications while multiplying professional developers' productivity by several times or even orders of magnitude.

Prominent developer Simon Willison wholeheartedly agreed and immediately put it into practice, having Claude add Atom feed support to his tools page.

A Paradigm Shift in App Development: From Product Launches to Daily Creation

From "Shipping Products" to "Publishing Posts"

Matt Webb's core insight cuts right to the heart of the matter:

When vibe-coding accelerates app development, apps become more personal, more contextual, more frequent. Publishing a tool or micro-app no longer feels like launching a website—it's more like publishing a blog post.

Matt Webb is a renowned British technology thinker and product designer who co-founded the design consultancy Berg. He has long focused on the evolution of internet infrastructure and human-computer interaction, and his blog Interconnected is one of the most widely followed sources of ideas in tech circles. Simon Willison is the co-creator of the Django web framework and the author of the data tool Datasette. In recent years, he has become one of the most active practitioners in AI-assisted programming, continuously publishing a large number of AI-assisted small tools on his personal website while documenting his development process with remarkable transparency. Their dialogue represents the deep thinking and rapid response of internet veterans to new paradigms.

This analogy reveals a profound shift. Traditional app development is a heavyweight process—requirements analysis, architecture design, development and testing, deployment and launch—each step carrying significant costs. But with AI-assisted programming, a useful small tool might only take minutes to hours to build. When creation costs drop dramatically, output naturally takes on "blog-like" characteristics: high-frequency, personal, and fragmented.

It's worth noting that the "creatorification" of software development didn't begin with Vibe Coding—it's the latest stage in a long evolutionary path. From personal homepages (GeoCities) in the 1990s to blogging platforms (WordPress, Blogger) in the 2000s, to no-code/low-code tools (Notion, Airtable, Webflow) in the 2010s, each technological step-down has enabled more people to "create" digital products. But each previous step-down came with a significant loss of expressive power—no-code tools can do far less than actual programming. The revolutionary aspect of AI-assisted programming is that, for the first time, it dramatically lowers the barrier while sacrificing almost no expressive capability: you can describe arbitrarily complex logic in natural language, and AI-generated code theoretically has the same upper limit of capability as hand-written code. This means software creation may truly enter an era of "universal accessibility," with output volumes far exceeding any previous wave of technological democratization.

The Distribution Problem Emerges

However, when app production becomes this lightweight, a new bottleneck emerges—distribution.

Currently, developers typically place these small tools on a page of their personal website or scatter them across GitHub repositories. There's no unified discovery mechanism, no standardized subscription method. You might stumble upon someone sharing a useful tool on social media, but it's nearly impossible to systematically track all the ongoing output from a given developer.

Matt Webb therefore proposed an intuitive solution:

I want those tools and apps pages to have an RSS web feed, with each entry having an "install" button. (But install to where?)

RSS: A New Mission for an Old Protocol

Why RSS Is the Ideal Choice for Micro-App Distribution

RSS (and its close relative Atom feed) is one of the most mature content subscription protocols on the internet. RSS (Really Simple Syndication) was born in 1999, originally developed by Netscape for content aggregation on its portal site. Atom is an alternative protocol standardized by the IETF in 2003 (RFC 4287) that resolved the chaos of RSS's multiple incompatible versions, providing stricter XML specifications and richer metadata support. Both share the same core principle: content publishers maintain a structured XML file (feed) on their server containing the title, summary, link, timestamp, and other information for their latest content entries; subscribers' readers (such as Feedly, NetNewsWire, Miniflux, etc.) periodically poll these feed files and pull new content for local display.

RSS/Atom experienced its golden age between 2005-2010, then declined with the rise of social media (especially Twitter and Facebook) and the shutdown of Google Reader in 2013. But in recent years, as users grow fatigued with algorithmic recommendations and increasingly value information sovereignty, RSS is experiencing a notable renaissance.

Its core advantages include:

• Decentralization: No platform dependency—anyone can publish and subscribe
• Standardization: Uniform format, mature ecosystem, rich tooling
• User sovereignty: Subscribers have complete control over their information feed, free from algorithmic interference

These properties align perfectly with the distribution needs of vibe-coded micro-apps. Each developer maintains their own tools feed, users subscribe to developers they're interested in, and browse newly published tools in their feed reader—a model that's simple and elegant.

Simon Willison's Atom Feed in Practice

Simon Willison's response speed itself embodies the Vibe Coding spirit. He had Claude add Atom feed support to his tools page (/elsewhere/tools/), completing the entire process through a single GitHub PR.

His tools site tools.simonwillison.net has accumulated a large collection of practical small tools, and now anyone can track his new tool releases via RSS/Atom subscription. This implementation provides a directly referenceable template for other developers.

The Unsolved Challenge: Install to Where?

When proposing the RSS solution, Matt Webb also astutely identified a key question—"But install to where?"

This question seems simple but touches on the core challenge of the micro-app ecosystem:

• Web apps can run directly in the browser, making distribution simplest, but functionality is limited by the browser sandbox. The browser sandbox is a core security mechanism of modern browsers that restricts webpage code execution to an isolated environment, preventing malicious code from accessing users' file systems, operating system resources, or data from other tabs. This model is built on a series of security specifications including the Same-Origin Policy. For micro-app distribution, the browser sandbox is both an advantage and a limitation: the advantage is that users don't need to install anything—they can safely use an app just by opening a link; the limitation is that apps cannot access local files, perform system-level operations, or function well offline (although Service Worker and PWA technologies partially mitigate this). The maturation of WebAssembly (Wasm) technology is expanding the capability boundaries of the browser sandbox, making it possible to run complex applications at near-native performance in the browser, which could provide the technical foundation for future micro-app runtimes.
• Desktop/mobile apps require installation processes involving platform review and security trust issues
• CLI tools target developer audiences and can be distributed through package managers like npm and pip. The npm registry hosts over 2 million packages, and PyPI (behind pip) has over 500,000 projects. They greatly simplify code distribution and reuse through standardized metadata descriptions (package.json / setup.py), version management (semantic versioning), dependency resolution, and one-click install commands. However, these package managers primarily target developers—installation requires command-line operations and runtime environments, making them inaccessible to ordinary users. The challenge for micro-app distribution is: how to maintain the standardization advantages of package managers while providing a simple experience for end users—similar to a smartphone app store's "one-click install" but without relying on centralized platform review.
• Browser extensions have their own distribution channels, but review cycles are lengthy

There is currently no universal "micro-app runtime" that elegantly solves this problem. Perhaps what we need in the future isn't just RSS for apps, but also a lightweight application sandbox—allowing users to one-click "install" and safely run micro-apps from their feeds.

Looking Ahead: Software Distribution Infrastructure for the Age of Abundance

Vibe Coding is pushing software development from "engineering" toward "creation." When everyone can easily produce useful small tools with AI programming assistants, we need to rethink how software is distributed, discovered, and managed.

RSS/Atom, as a classic content distribution protocol, may be entering its second spring—this time, what it distributes isn't articles, but applications.

This trend is worth watching closely. When creation costs approach zero, the value of infrastructure becomes paramount. Whoever first solves the distribution and runtime problems for vibe-coded micro-apps may define the ecosystem of the next generation of personal software.

Key Takeaways

• Vibe Coding makes app development as frequent and personal as blogging, rendering traditional app distribution methods obsolete
• Matt Webb proposed using RSS feeds to share and subscribe to vibe-coded micro-apps, and Simon Willison has already put this into practice
• The decentralized, standardized nature of RSS/Atom protocols aligns perfectly with micro-app distribution needs
• "Install to where" remains the core unsolved challenge, requiring new infrastructure like lightweight application sandboxes
• When software creation costs approach zero, distribution and runtime infrastructure will become the key competitive differentiator