The Vibe Coding Era: Why We Need RSS to Distribute Personal Apps

When Building Apps Becomes as Frequent as Publishing Blog Posts

Matt Webb recently raised a fascinating point: as vibe coding accelerates app development, we need an RSS-like mechanism to share and distribute the flood of personalized micro-tools and applications that are emerging.

The idea seems simple, yet it touches on a core issue of the AI-assisted programming era—when the barrier to creating apps drops dramatically, how should discovery and distribution mechanisms keep up?

The Fundamental Changes Vibe Coding Brings

Vibe coding refers to the practice of rapidly generating code with the help of AI tools (such as Claude, GPT, etc.). Developers simply describe their intent, and AI handles most of the implementation. The term was coined by Andrej Karpathy (former Tesla AI Director and OpenAI co-founder) in early 2025, who described this programming style as "fully giving in to the vibes, embracing exponential growth, and forgetting that the code even exists." Unlike traditional AI-assisted programming (such as code completion), the core philosophy of vibe coding is that developers rarely read or edit code directly—instead, they continuously converse with AI in natural language, letting it take full responsibility for code generation, debugging, and iteration. This represents an extreme form of human-AI collaborative programming—the developer's role shifts from "the person who writes code" to "the person who describes intent."

This approach brings several notable changes:

Apps Become More Personal

In the past, building a tool required significant time investment, so developers tended to build general-purpose products. Now, spending a few minutes having AI generate a small tool that solves a specific problem means apps naturally become more personalized and context-specific.

Publishing Frequency Increases Dramatically

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

This analogy is spot-on. The rise of blogging gave birth to RSS, and when app publishing approaches the cadence of blog publishing, we genuinely need similar subscription and aggregation mechanisms.

Feasibility Analysis: RSS as an App Distribution Mechanism

Matt Webb envisioned a scenario: every developer's tools page offers an RSS feed, with each entry featuring an "install" button. This idea immediately raises a key question—"install to where?"

To understand the technical foundation of this vision, it's worth revisiting RSS's history. RSS (Really Simple Syndication) was first created in 1999, developed by Netscape for its web portal. It subsequently went through multiple version splits (RSS 0.9x, 1.0, 2.0), triggering the famous "RSS format wars." The Atom protocol (RFC 4287) was published as an IETF standard in 2005, aiming to resolve incompatibilities between RSS versions by providing stricter specifications and better extensibility. Both are XML-based content syndication formats that allow users to subscribe to website updates through readers without visiting each site individually. Despite social media's rise temporarily marginalizing RSS, it has maintained strong vitality in tech communities and podcast distribution.

This question reveals several major gaps in the current ecosystem:

Lack of discovery mechanisms: Countless personally-developed micro-tools are scattered everywhere, with no unified discovery channel
Lack of distribution standards: Unlike mobile apps with App Stores, these lightweight web tools have no standardized distribution method
Lack of subscription mechanisms: Users can't conveniently track which new tools their favorite developers have published

Current mainstream app distribution relies on platform-based models: Apple App Store, Google Play Store, and various mini-program platforms. They form powerful centralized control through review mechanisms, ranking algorithms, and payment systems. This model suits commercial applications, but for lightweight, personalized micro-tools, listing costs and review cycles are excessive. In contrast, the web's openness naturally supports decentralized distribution—anyone can publish tools under their own domain without permission. RSS/Atom is precisely a product of this decentralized web philosophy, establishing direct connections between content publishers and consumers, free from platform algorithm interference or commercial interests.

Simon Willison's Rapid Implementation

Inspired by Matt Webb, prominent developer Simon Willison quickly took action—he had Claude add an Atom feed to his /elsewhere/tools/ page. This page aggregates various tools he has published on tools.simonwillison.net.

Simon Willison is the co-creator of the Django web framework and has become known in recent years for his deep exploration of AI tools and prolific output. His Datasette project is an open-source tool for exploring and publishing data, while his tools.simonwillison.net collects numerous single-page web tools generated with AI assistance—from JSON formatters to image processors, each typically solving one specific problem. His workflow represents a typical vibe coding use case: rapid prototyping, instant publishing, continuous iteration. He's also one of the most active chroniclers in the LLM (Large Language Model) application development space, with his blog serving as an essential source for tracking AI toolchain developments.

A telling detail: this change itself was completed with AI assistance (he noted "have Claude" in his GitHub PR), which perfectly demonstrates vibe coding's efficiency—from inspiration to implementation in minimal time.

A Deeper Reflection: Software Is Shifting from Product to Content

This discussion actually points to a larger trend: software is shifting from product to content.

When the cost of creating software approaches zero:

Software lifecycles may shorten, with use-and-discard "disposable apps" becoming increasingly common
A developer's personal brand and curation ability become more important
We need new infrastructure to support this "apps as content" paradigm

Traditional software engineering emphasizes maintainability, scalability, and long-term support because development costs are high and software is treated as an asset requiring ongoing investment. But when AI can generate a fully functional tool in minutes, "regenerating" may be more economical than "maintaining." This gives rise to the concept of "disposable apps"—tools created for specific scenarios and specific moments that can be discarded after use, with a newer version regenerated when needed. This pattern resembles the shift in consumer mindset from "buying durable goods" to "using disposables," and it poses fundamental challenges to traditional concerns like version management, security updates, and data persistence.

RSS/Atom, as a mature, decentralized content subscription protocol, is naturally suited for this scenario. It doesn't depend on platforms, respects creators' autonomy, and gives users complete control.

Conclusion

From blogs to podcasts to today's micro-apps, RSS—a protocol born in the Web 1.0 era—may be entering its third life. In an age where AI enables everyone to become an app developer, we need open, standardized content distribution mechanisms more than ever before.