About Quell: built by one developer
Skip to content
QUELL

About the developer

One developer. One opinion.
One hard limit.

The limit isn’t the bug. The limit is the product.

Why one person built this

Every read-later app I used had the same shape: unlimited saving, an archive stretching back years, and a quiet, growing shame about the unread pile. The tools were excellent at storage and useless at follow-through.

Quell started as a personal constraint, a list that refuses to grow past a few items. It became a product with a single, unusually blunt promise.

Being one developer keeps that promise safe. There is no growth team asking for infinite saving, no engagement metric that improves when your queue gets longer. The only number worth optimising is whether you actually read what you chose.

Designed, built & maintained by
Palfalvi Lorand
Published by
Software Flow Yard S.R.L.
Quell queue screen showing an empty feed with an invitation to add your first source.

What I refuse to break

Five principles the app refuses to break.

  1. 01

    Saving is a commitment

    Every save costs you one of five slots. That price is the point, it turns a reflex into a decision.

  2. 02

    Your queue holds up to ten

    There is no unlimited tier, no archive to hide in. A small queue forces you to pick what matters this week.

  3. 03

    The score can hurt

    Stats show real follow-through, not saves. When the number is low, that discomfort is the feature.

  4. 04

    Nothing auto-completes

    Opening content never marks it done. “Mark as consumed” is always a deliberate tap you make yourself.

05

Unread means expired

Deadlines matter. Content you don't follow through on leaves on its own, no guilt pile, no growing backlog, no notification begging you to come back.