The Vibe Coding Era: Why We Need RSS to Share Personal Micro-Apps
AI coding makes software development as easy as blogging—RSS may become the new distribution layer for micro-apps.
As vibe coding (AI-assisted programming) lowers the barrier to building micro-apps, software output is shifting from "products" to "content." Matt Webb proposes using RSS feeds to share personal micro-apps, and Simon Willison quickly put this into practice by having Claude add an Atom feed to his tools page. This reflects three major trends: the content-ification of software, the renaissance of personal tools, and a gap in distribution infrastructure. RSS—a venerable protocol—may serve as the starting point for lightweight distribution in the vibe coding era.
When Coding Becomes as Easy as Writing a Blog Post
With the rise of AI-assisted programming (vibe coding), the barrier to developing small tools or micro-apps is dropping dramatically. Vibe coding—a concept coined by OpenAI co-founder Andrej Karpathy in early 2025—refers to a programming approach where developers describe their needs to AI in natural language, and large language models automatically generate the code. Instead of writing code line by line, developers act more like "directors" guiding AI to handle the implementation. This approach drastically lowers the programming barrier, enabling non-professional programmers to quickly build functional applications while multiplying the productivity of experienced developers.
Matt Webb recently proposed an intriguing idea: we need an RSS-like mechanism to share the flood of personal apps emerging from this new paradigm.
The idea seems simple, but it touches on a profound shift already underway—software development output is evolving from "products" to "content."
From Launching Websites to Publishing Blog Posts: The Transformation of Software
Matt Webb's core insight is:
When vibe coding accelerates app development, apps become more personal, more contextual, and 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 precise. In traditional software development, releasing an application is a "big deal"—requiring planning, design, testing, deployment, and maintenance. But under the vibe coding paradigm, you might spend just a few minutes having AI generate a small tool that solves a specific problem. These tools might serve only you, or they might be useful to others with similar needs.
The question is: when everyone is producing these micro-apps at high frequency, how do we discover and access them?
Distributing Micro-Apps via RSS: An Old Yet Elegant Solution
Matt Webb's proposed solution is to add RSS/Atom feeds to personal tool pages, with each entry featuring an "install" button. To appreciate the cleverness of this approach, some background is helpful: RSS and Atom are both XML-based content syndication protocols born in the early 2000s during the Web 1.0 era. These protocols allow websites to publish update summaries in a standardized format, enabling users to subscribe to multiple sources through RSS readers (like Feedly, Inoreader, etc.) without needing to visit each site individually. RSS was once the core infrastructure of the blogging era but faded as social media platforms like Twitter and Facebook rose to dominance. In recent years, however, as people grow weary of algorithmic recommendations and rediscover the value of decentralized information access, RSS is experiencing a renaissance. Atom is an improved version of RSS, standardized by the IETF (RFC 4287), offering better format specification and internationalization support than RSS 2.0.
The elegance of this idea lies in:
- Decentralization: No need for a unified app store to review and distribute
- Subscription model: You can follow developers you're interested in and automatically receive their new tools
- Low friction: Completely consistent with how blog content is already distributed
Of course, Matt Webb himself raises a critical question: "Install to where?" This exposes the immaturity of the current ecosystem—we have efficient AI-powered production methods, but the distribution and runtime infrastructure hasn't caught up. This challenge spans multiple technical layers: traditional apps require specific runtime environments—native apps depend on operating systems, web apps need server hosting, desktop apps need installer packages. Currently, most micro-apps exist as static HTML+JavaScript (runnable directly in browsers) or rely on serverless platforms like Cloudflare Workers or Vercel for hosting. PWA (Progressive Web App) technology offers one possible direction—it allows web apps to be "installed" on devices like native apps, supporting offline operation and push notifications—but its ecosystem maturity and user awareness remain limited.
Simon Willison's Practice: Using AI to Solve AI Output Distribution
Inspired by this idea, prominent developer Simon Willison immediately put it into action. Simon Willison is a co-creator of the Django web framework and the author of the data tool Datasette. He has long been active in the open-source community and at the forefront of AI tool exploration. His personal site simonwillison.net is a benchmark in the tech blogging space, while tools.simonwillison.net hosts a large collection of practical small tools he's developed with AI assistance—he's one of the early advocates of vibe coding in practice, frequently sharing his complete development process using AI tools like Claude.
He had Claude add an Atom feed and icon to his /elsewhere/tools/ page. This page aggregates the various tools he publishes on tools.simonwillison.net.
What's interesting is that this modification itself was completed through AI—he created a PR on GitHub, with Claude implementing the actual code. This creates a fascinating loop: using vibe coding to solve the distribution problem of vibe coding output.
Deeper Trends: A Paradigm Shift in Software Development
This discussion reflects several trends worth paying attention to:
The "Content-ification" of Software
When AI programming drives development costs toward zero, software is no longer scarce. It becomes like blog posts—abundant, personal, and time-sensitive. We need to treat these software artifacts the way we treat content.
The Renaissance of Personal Tools
In the SaaS-dominated era, we've grown accustomed to using generic tools. SaaS (Software as a Service) has been the dominant business model in the software industry for the past two decades, where users pay monthly or annually for cloud-hosted general-purpose software (like Notion, Slack, Figma, etc.). The advantage of this model is zero maintenance and continuous updates, but the trade-off is that users must adapt to the software's generic design rather than the software adapting to users' personalized needs.
But vibe coding makes "tailoring tools for yourself" feasible, potentially sparking a renaissance of personal software. Notably, this isn't entirely new—before SaaS, in the early days of personal computing (1980s-90s), there was a rich culture of personal tools where users customized solutions using HyperCard, Excel macros, AutoHotkey, and similar tools. Vibe coding is reviving this tradition of "end-user programming," but with AI as the medium, elevating customization capabilities by an order of magnitude.
The Distribution Infrastructure Gap
The app store model is too heavy, and GitHub repositories are too technical. We need a lightweight distribution method that sits between the two. RSS might be a starting point, but the complete solution remains to be explored—perhaps future platforms will emerge specifically for micro-app aggregation, or existing RSS readers will evolve the ability to "run" micro-apps with one click.
Conclusion: From RSS to App Store and Back to RSS
Technological progress sometimes moves in spirals. When AI makes software development as effortless as writing, perhaps we truly need to return to the fundamental paradigms of content distribution to rethink how software spreads. RSS—a protocol born in the Web 1.0 era—might just be the most fitting distribution vehicle for the vibe coding age.
Key Takeaways
- Vibe coding makes app development as frequent and personal as blogging, demanding new distribution mechanisms
- Matt Webb proposes using RSS feeds to share personally developed micro-apps and tools
- Simon Willison, inspired by the idea, used Claude to add an Atom feed to his tools page
- Software is undergoing a "content-ification" transformation, shifting from scarce products to high-frequency personal output
- The current ecosystem faces a distribution infrastructure gap—app stores are too heavy, GitHub is too technical
Related articles
Expert OpinionsOutdoor Coding: You Can Touch Grass AND Build Things
When AI coding assistants free developers from their desks, outdoor coding becomes a real trend. Explore how cloud IDEs, voice coding, and AI tools enable creativity in nature.
When AI Treats Humans as Subagents: Ro…
When AI Treats Humans as Subagents: Role Reversal and Hidden Risks in Human-AI Collaboration
Exploring the paradigm shift where humans become "subagents" in AI Agent architectures. Analyzes human node design in LangChain and AutoGen, and the risks of ceding control and cognitive atrophy.
Expert OpinionsThe Lazy Person's Productivity Theory: Why Being 'Lazy' Actually Drives Peak Performance
Explore the engineering philosophy behind 'lazy people are most productive': how constructive laziness drives automation, AI tools amplify efficiency, and systems thinking eliminates wasted effort.