Current - An RSS reader

Current removes the pressure of reading

A new RSS reader called Current launched this month with a specific goal: removing the anxiety associated with unread article counts. The app ignores the traditional "inbox" metaphor that has dominated news aggregators for over two decades.

Most modern RSS readers treat the internet like a task list. They use notification badges, bold text for unread items, and "mark all as read" buttons to signal that a user is behind on their content. Current eliminates these features to prevent what its developer calls phantom obligation.

The developer began building the app after realizing that existing tools like Feedly and Reeder felt more like work than leisure. While those apps are technically proficient, their design language suggests that unread articles are a failure state. Current attempts to return the experience to a casual flow of information rather than a mountain of data to be processed.

The legacy of NetNewsWire

The design of the modern RSS reader dates back to 2002. This was the year Brent Simmons released NetNewsWire, an app that effectively set the standard for how we consume feeds. It introduced a three-pane interface that mirrored email clients of the era.

This decision was pragmatic at the time. In the early 2000s, the "Inbox Zero" philosophy was gaining traction, and treating news like email made sense for power users. However, this convention calcified over the next 22 years, turning every news feed into a digital chore.

The "unread count" became a staple of the user interface. It created a psychological trigger that demanded attention, regardless of whether the user actually wanted to read the content. Current argues that this design choice was the moment RSS started making users feel guilty for simply being offline.

Defining the phantom obligation

The core philosophy behind the new app is a concept titled phantom obligation. This term describes the specific guilt a user feels when they fail to complete a task that no one actually assigned to them. In the context of RSS, it is the pressure to clear a list of 500 unread articles.

This feeling is not an accident of the technology but a direct result of UI choices. When an app shows a bright red number next to a feed, it signals that the user is "losing" a game. Current removes these metrics entirely, treating the web as a river to dip into rather than a bucket to empty.

By naming this feeling, the developer identified why many users abandoned RSS for social media algorithms. While algorithms are problematic for many reasons, they rarely make a user feel "behind." Current seeks to marry the control of RSS with the low-pressure environment of a standard social timeline.

How Current changes the feed

The technical implementation of Current is a direct rejection of the NetNewsWire model. It does not track which items you have clicked or how many posts remain in the queue. The interface focuses on the present moment rather than the backlog.

Users will notice several immediate differences in how the app handles data:

• No unread badges appear on the app icon or within the feed list.
• No "Mark as Read" button exists because the app does not keep track of reading status.
• Chronological scrolling allows users to see what is new without feeling pressured to reach the bottom.
• Minimalist typography prioritizes the text of the article over metadata and utility icons.

The app assumes that if an article is important, the user will see it when they open the app. If they miss it, the app treats that as a natural part of consuming media. This removes the "completionist" mindset that often leads to digital burnout.

The return of the slow web

Current arrives during a broader cultural shift toward digital wellness and the "slow web." As platforms like X and Instagram become more chaotic, users are returning to RSS for a curated experience. However, the old tools for RSS often carry the same stress as the platforms users are trying to flee.

The developer spent months refining the code before articulating the philosophy behind it. In January, the retrospective essay on the app's development helped define why the "inbox" model is failing modern readers. The goal was to build a reader that didn't make the user feel like they owed the software their time.

This approach places Current in a niche category of "calm technology." It is designed to be used when the user is curious, not when they feel a sense of duty. By removing the counters, the app effectively removes the "job" of being an internet user.

Redesigning the reading experience

Most software companies focus on engagement metrics and time-in-app. They want users to stay as long as possible and click as many links as possible. Current takes the opposite approach by making it easy to leave the app without feeling like something was left unfinished.

The development of the app suggests that the next phase of the open web isn't just about decentralization. It is about user agency and the right to ignore content. If the last two decades were about organizing the world's information, the next decade might be about making that information less demanding.

Current is currently available for users who want to test this low-pressure environment. It supports standard OPML imports, allowing users to migrate their existing feeds from NetNewsWire, Feedly, or Old Reader. Once imported, those feeds lose their "unread" status and become a simple, ongoing stream of text.

The move away from "phantom obligation" could signal a new trend in app design. If users respond well to Current, other utilities might begin stripping away the gamified elements that have come to define our digital lives. For now, it remains a quiet alternative for those tired of their news feeds looking like a to-do list.