My Read-Later List Had 1,200 Articles

My Read-Later List Had 1,200 Articles

A few months ago I opened my read-later app and noticed something uncomfortable. I had saved **1,200 articles**.

Most of them looked interesting. Many of them were probably good.

But the truth was simple: I wasn’t going to read them. Saving articles had quietly turned into a habit that felt productive but wasn’t. Every time I saved something, I got the small dopamine hit of *“I’ll read this later.”* Later rarely arrived. Over time the list stopped feeling useful and started feeling like guilt.

The Quiet Failure of Read-Later Apps

Most read-later tools follow the same design pattern. You see something interesting. You press **Save**. And that’s it. The tool is optimized for collecting things, not processing them. Which leads to a predictable outcome: ```text save → save → save → save ```

But almost never: ```text save → read → learn ``` The list grows faster than your available time ever could. Eventually it becomes a kind of digital hoarding.

What If Saving Required a Decision?

While staring at my 1,200-article backlog, I started wondering if the problem wasn’t the users. Maybe it was the tools. Saving an article requires **zero intent**. It’s just a button. So I tried a small experiment. Instead of one save button, what if saving required a tiny decision?

Something like: * **Read soon** * **Maybe later** * **Archive**

Nothing complicated. Just a moment of triage. That small change shifts the mental model completely. You’re no longer building an archive. You’re managing a queue.

A Reading Inbox Instead of a Reading Archive

Email works because it’s an inbox. Things arrive. You process them. They leave.

A reading system could work the same way. Articles enter the inbox. Some get read. Some get postponed. Some disappear.

The goal isn’t to preserve everything you might want to read someday. The goal is to surface the few things that actually deserve your attention.

Highlights Are Where the Value Actually Lives

When people do read articles, something interesting happens. They highlight things. A sentence. A paragraph. An idea.

Those highlights are usually the only parts we truly remember. Which means the real value of reading isn’t the article itself. It’s the **ideas that survive it**.

So the workflow becomes something closer to: ```text capture → read → highlight → remember ```

Instead of: ```text capture → hoard → forget ```

The Experiment

This line of thinking eventually turned into a small project I’ve been building called **Sigilla**. The idea is simple: * Treat saved articles like a **reading inbox** * Require a tiny decision when capturing something * Focus on highlights and ideas instead of collecting links

I’m still experimenting with it, but it’s already changed how I read. My list is smaller. I actually finish things. And I remember more of what I read.

Which, in the end, was the whole point.