In the Vibe Coding Era, Using RSS to Share and Discover Personal Apps

When Building Apps Becomes as Easy as Publishing a Blog Post

With the rise of AI-assisted programming—known as "Vibe Coding"—the barrier to developing small tools and micro-applications is dropping dramatically. The term "Vibe Coding" was coined by Andrej Karpathy (former Tesla AI Director and OpenAI co-founder) in early 2025, describing an entirely new programming paradigm: instead of writing code line by line, developers describe their intent in natural language and let large language models generate the complete code implementation. Karpathy described it as "fully giving in to the vibes, embracing exponential growth, and forgetting that the code even exists." This approach has dramatically lowered the technical barrier to software development, enabling non-professional programmers to rapidly build fully functional applications.

More and more developers are "publishing" personal tools as frequently as they write blog posts—small, personalized, and designed to solve problems in specific scenarios. But a new question has emerged: How can these ever-growing numbers of personal apps be discovered and shared?

Prominent developer and blogger Matt Webb recently proposed an inspiring idea: we need an RSS-like mechanism to aggregate and distribute these vibe-coded applications. Matt Webb is a veteran thinker in British design and technology who co-founded the design consultancy Berg. He has long focused on the intersection of IoT, human-computer interaction, and internet culture, and his blog Interconnected is a widely followed independent voice in tech circles. Simon Willison (renowned AI tool developer, Django web framework co-creator, and author of Datasette) quickly responded by adding Atom feed support to his own tools page, validating the idea's feasibility through practice.

Vibe Coding Is Changing the Nature of Applications

From "Product Launches" to "Content Publishing"

Matt Webb precisely identified a trending shift in his article:

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 feels more like publishing a blog post.

This analogy is remarkably apt. Traditional app development cycles are long and expensive, making each release an "event." But with Vibe Coding, a small tool that solves a specific pain point can be completed in minutes to hours. The developer's role shifts from "writer" to "guide" and "reviewer"—they describe requirements in natural language, AI generates the code, and developers review and adjust the results. This human-AI collaborative model is causing developers' tools pages to expand rapidly, turning into "app blogs."

The Explosive Growth of Personal Tools

Take Simon Willison as an example. He maintains a standalone tools site at tools.simonwillison.net, hosting numerous small tools he developed with AI assistance. Simon Willison is the co-creator of the Django web framework and has recently become known for Datasette (an open-source tool that instantly transforms any SQLite database file into a web application with API endpoints and a visual interface, requiring no backend code) and LLM command-line tools. He's an early practitioner and evangelist of AI-assisted programming. The applications on his tools site are highly personalized, often targeting very specific use cases. This phenomenon is spreading across the developer community—more and more people have their own "tools" pages listing various micro-applications.

Why Use RSS to Distribute Personal Apps

The Natural Advantage of Decentralization

Matt Webb's core proposal is: provide RSS/Atom web feeds for these tools pages, with each entry accompanied by an "install" button. The elegance of this idea lies in borrowing a content distribution protocol that has been proven over more than twenty years to solve an entirely new problem.

RSS (Really Simple Syndication) was first created in 1999 by Netscape and evolved through multiple versions. Atom is an alternative protocol standardized by IETF in 2005 (RFC 4287), addressing compatibility issues caused by RSS's multiple coexisting versions. Both share the same core concept: content publishers generate a standardized XML file containing metadata such as titles, summaries, links, and timestamps, while subscribers periodically pull updates through feed readers (like Feedly or Inoreader). This "publish-subscribe" model was a cornerstone of the early open internet, reaching its peak popularity between 2005-2010 with Google Reader. Although social media's algorithmic recommendations once marginalized RSS, it has been experiencing a renaissance in recent years as users increasingly value information autonomy.

The advantages of RSS as an app distribution channel include:

• Decentralization: No platform dependency; each developer publishes independently
• Standardization: A unified format makes aggregation and subscription simple
• Low friction: Subscribe once to receive updates without repeatedly visiting individual sites
• User sovereignty: Users decide who to follow, rather than algorithms deciding for them

Key Unsolved Problems

Of course, Matt Webb himself raised a critical question: "Install to where?" This reveals a gap in the current ecosystem. Blog posts can be read directly in the browser, but apps need a runtime environment. Install locally? Deploy to the cloud? Run in some kind of sandbox? The answer to this question will determine whether this ecosystem can truly take shape. Several possible directions already exist: WebAssembly technology allows running near-native-performance applications in the browser; edge computing platforms like Cloudflare Workers and Deno Deploy offer lightweight cloud deployment options; and the Progressive Web App (PWA) standard gives web apps native-app-like installation and offline experiences. But no single solution has yet emerged as the universal runtime for vibe-coded apps the way browsers serve web pages.

Simon Willison's Rapid Implementation

Here's a telling detail: after seeing Matt Webb's article, Simon Willison immediately took action. He had Claude (Anthropic's AI assistant) help him add an Atom feed and corresponding icon to his tools page. Claude is a large language model series developed by Anthropic, a company founded in 2021 by former OpenAI Research VP Dario Amodei and Daniela Amodei with "AI safety" as its core mission. Claude is known for its capabilities in long-text understanding, code generation, and following complex instructions, particularly excelling in programming assistance scenarios. The entire process was completed through a single GitHub PR.

This itself is a perfect Vibe Coding case study: an idea goes from proposal to implementation in just minutes. And this capacity for rapid iteration is precisely the fundamental reason driving the need for "apps need RSS."

A Paradigm Shift in App Distribution: From App Stores to RSS

If we zoom out further, this discussion actually touches on a deeper question: In an era where AI enables anyone to easily create applications, the mechanisms for app distribution and discovery need fundamental transformation.

The app store model was established by Apple with the launch of the App Store in 2008, and subsequently replicated by Google Play, the Microsoft Store, and other platforms. The core assumption of this model is that app development is a high-barrier professional activity requiring centralized review, distribution, and payment systems. Platforms typically take a 15%-30% revenue cut and hold review authority over app content and functionality. While this model achieved enormous success in the mobile internet era, it also brought problems like platform monopolies, opaque review processes, and weak bargaining power for independent developers. When AI democratizes app development, this heavyweight distribution system designed for "a few professional developers serving large user bases" creates fundamental tension with the new reality of "everyone is a developer."

When the boundary between developers and users blurs, when anyone can be a tool creator, what we need is a lighter, more decentralized distribution method that resembles "content publishing." This aligns with the spirit of the early internet—Tim Berners-Lee's original vision for the World Wide Web was an open information space where everyone could publish and everyone could access.

RSS may not be the final answer, but it points in the right direction—returning app sharing to the essence of the open web. This discussion about vibe-coded app distribution has only just begun, but it may herald an important evolution in the software ecosystem.

Key Takeaways

• AI-assisted programming (Vibe Coding) makes app development as frequent and personalized as blogging, creating demand for new distribution mechanisms
• Matt Webb proposed using RSS/Atom feeds to aggregate and share personally developed micro-apps, leveraging a mature content distribution protocol to solve a new problem
• Simon Willison quickly used Claude to add an Atom feed to his tools page, validating the concept through action
• The core challenge is "install to where"—unlike articles, apps need a runtime environment, and this problem remains unsolved
• This discussion reflects a deeper trend: when anyone can create apps, distribution needs to shift from the app store model to a decentralized, lightweight paradigm