Ago

The dog bath situation clarified what Ago should and shouldn't be. We never failed at bathing Hanx by breaking a streak - we just didn't have a neutral way to see the fact. What we needed wasn't a counter we could fail, it was an honest answer: it's been 23 days.

That framing ruled out a lot of what competitors build. No streaks - missing a log shouldn't feel like failure. No achievement systems. No nudges framed as "don't break the chain." No copy that implies you're behind. Every word in the app is written around one principle: show the elapsed time accurately, let the user decide what to do about it.

The design language follows the same logic. Large readable number, muted palette, no flashing overdue states beyond a clear color shift. One thing came up consistently in the reviews: users don't want to feel judged by their own app. "I get angry at notifications and rebel against my own authority." That's not a niche user psychology - it's how most people feel about reminders. Building against it wasn't a constraint, it was the product.

Every competitor in the category frames around habits, sobriety, milestones, or countdowns. None frame around the gap between those categories - the recurring-but-irregular task that resists a fixed schedule.

That framing had a direct consequence for how reminders work. When you log something done, the deadline resets from that date - not from when it was originally scheduled, not from when you forgot. From when you actually did it. This is what Todoist and Apple Reminders both get wrong: a missed recurring task doesn't restart from completion, it just accumulates.

A thread from r/adhdwomen made this concrete: when you miss a monthly task and eventually get to it late, the reminder should restart from when you actually did it, not from the original schedule. Several people in the thread said the same thing independently. Ago's notification model works exactly this way - deadline days always count from last done.

The subscription resentment in this category isn't subtle. Days Since - Track Memories sits at 3.4 stars largely because it moved previously-free features behind a paywall. Since: Day Counter, the most feature-complete app in the space, gets regular one-time purchase requests despite charging $49.99 lifetime. Last Time Tracker's $2.99 pay-once pricing is essentially invisible as a complaint driver - users describe it as "best two dollars I ever spent."

I chose $4.99 deliberately. Lower ($2.99) now reads as the price of an abandoned app - Last Time Tracker set that association. Higher ($6.99+) generates sticker shock in a niche where the review data showed a clear price ceiling around $5. The free tier gives users three real items before asking for anything, which means anyone who hits the paywall has already seen value.

Pay-once also serves as a trust signal. The phrase "bait and switch" appears across category reviews more than almost any other. A clean one-time unlock is a promise - it's the opposite of what users are angry about.

Every app in the 500-review corpus had users asking the same thing: can I log something that happened yesterday? Or last week? "I forgot." "I only log it the morning after." "I wanted to start it from when I actually quit." No app had built it into v1. Most hadn't built it at all.

I shipped it in v1.0. From the item detail screen, "Log for a different date" opens a date picker with a minimum of one day after the last log and a maximum of yesterday. An undo toast handles miskeys. It's not buried in settings - it's on the main detail view because the review data showed it wasn't an edge case, it was a normal behavior that every competitor was missing.

This wasn't driven by my own use - I hadn't needed backdating yet when I built it. It was a direct read from competitor reviews. If every app in a category misses the same thing and users ask for it in every single review corpus, it's a baseline expectation that nobody has met - not a feature request to consider for later.

The first shipped version used a 2-column card grid. It looked clean. It was also wrong for the job. The home screen's primary function is comparison - you want to scan elapsed times and see at a glance what's been neglected. A grid forces lateral eye movement; you're jumping between columns instead of reading down a single line. Switched to full-width single-column rows. 7-8 items visible at once instead of 4, and the elapsed number on every row is left-aligned at the same position - one vertical scan tells you everything.

The sort default matters for the same reason. Overdue-first sounds obvious, but it creates anxiety in an app built around calm - every open feels like a task list of failures. The default is longest-elapsed-first instead: you see what you've left longest, not what you've "failed." Overdue sort is available one tap away for users who want it.

The log-done interaction is the highest-frequency action in the app, so it lives on the card itself - a check button on the right edge, no need to open the item first. Every other app in the category requires tapping into a detail screen before you can log. That's one extra tap on the thing you do most often.

After logging, there's no confirmation dialog. Confirmation dialogs interrupt the flow at exactly the moment it should feel satisfying. Instead: an undo toast appears for 4 seconds. Same safety net, zero friction on the happy path. The card holds its position for 650ms after the checkmark animation before re-sorting - enough time to see the number reset before the list rearranges, so you don't lose your place.

The onboarding is four slides. No feature tour, no permission request upfront, no "here's how Ago works" wall of text. The first thing you see is a large typographic "23 days" - the app's output, distilled. The second slide shows items you might track, animated as cards. The third shows what a notification looks like when something's actually overdue. The fourth transitions directly into the app.

The first-launch prompt is "What's the last thing you did?" - not "Add your first item." One framing asks you to engage with the concept; the other asks you to perform a UI action. Most people know something they haven't done in a while. Giving them that as the entry point means the app has value the moment they finish onboarding, not after they've spent time setting it up.

Notification permission isn't requested on launch. It comes up the first time you set a deadline - contextually, at the exact moment where it's obvious why the app needs it. Asking on cold launch is almost always a mistake. There's no reason for the user to say yes yet.