
Strikethrough
A daily to-do list as satisfying as crossing tasks off
I built a to-do list app because I couldn't stand all the various task manager apps I tried.
Every app buried "add a task" under projects, tags, and priority levels. And when I finally did complete something, there was no satisfaction, just a checkbox and an ever growing backlog. It stopped feeling like a tool and started feeling like a management chore.
So I built Strikethrough — a daily to-do list that works more like a paper list than a productivity system.
How it works:
Double-tap anywhere to add a task instantly.
Swipe right to strike it through when it's done. See the task you completed that day.
Then the list resets every morning, so you only ever see today's tasks, never last week's leftovers.
Deliberately minimal: no accounts required, no gamification, no notifications. Just tasks, a satisfying strikethrough, and a clean slate every morning. Have tried to build in delight and make it feel a little different to other to-do list apps.
It's live on Android now, about two weeks in, early days on a few installs, currently working on organic discovery.
Honest question for the IH community: most to-do apps feel functional but joyless, therefore does something built around the simplicity and metaphor of a paper list actually feel more delightful to use? Is adding a task and striking it through genuinely more satisfying than whatever you're using now, or is the paper list idea just nostalgia?
Play store link: https://play.google.com/store/apps/details?id=com.strikethrough.app
Website: https://ripetungi.com/strikethrough/
About
Hi đź‘‹ I built Strikethrough because every to-do app I tried looked and worked the same. So I created something closer to a real paper list. Simply add a task and strikethrough when its done.

3 Comments
This is interesting because it doesn’t try to improve task management—it changes what “completion” feels like. Most to-do apps optimize organization, but the real emotional driver is closure. The daily reset + visible strike-through is basically a system designed around that moment of closure rather than backlog accumulation.
Thanks. Yes it is, because thats what matters most.
I think that's where the bigger strategic decision starts.
The interesting part isn't optimizing for closure—it's deciding what behavior your product is quietly teaching users to repeat.
I have a couple of thoughts on that which are easier to explain than squeeze into a thread. If you're interested, what's the best email to reach you on?