A Shared To-Do App for Couples, Minus the Nagging

The boiler service needed booking three weeks ago. You mentioned it on a Tuesday, in the kitchen, while one of you was doing something else. It was received the way things said in kitchens are received: a noise of agreement, no memory formed.

So you mentioned it again on the Sunday. And again the Sunday after that, this time with a note of something in your voice. And now there's a small, stupid argument happening that isn't about the boiler at all.

That's the thing nobody says out loud about household admin. The job is fine. Booking a boiler service takes four minutes. What costs you something is the asking — the second ask, the third ask, and the moment your partner hears a request as an accusation because it's the third time it's arrived.

Why a shared list on its own doesn't fix it

Two of you can absolutely keep a shared list. Plenty of couples do. We've written about the shared list as a couples tool and it earns its keep — for places, for shopping, for the things you're collecting together.

But a list is a noticeboard. Anything on it belongs to everyone, which in practice means it belongs to nobody. You both look at ring the plumber and you both think, reasonably, that the other one might. A week later it's still there, and now it's evidence.

The other direction is worse. Reach for a proper project tool and you get boards, subtasks, dependencies, priority fields — an apparatus built for a team of nine shipping software, pointed at two people trying to remember the recycling. Nobody sustains that. The overhead of logging the job exceeds the job.

What's missing sits in between. Not a list, not a project. A single thing, owned by one person, that both of you can see the state of.

Ask for something, or promise it

That's the sentence Blinko puts on the empty Tasks tab, and it's the whole design in eight words: ask for something, or promise it — tasks keep it honest.

A task in Blinko goes to exactly one person. Not the household, not "whoever gets to it" — one name. You can assign it to your partner, which is an ask, or to yourself, which is a promise. There is no third option, no shared ownership, no splitting it into subtasks and dividing them up. That constraint is the feature. The reason ring the plumber survived three weeks on your list is that it never had a name on it.

And it isn't final until they say so. A task arrives as a request, and the other person accepts it or declines it. Until they accept, the card says so in as many words — it's waiting on them, by name. A fact, plainly stated, rather than a mood you have to interpret.

Decline is a real answer, by the way, and it's worth saying that clearly. No, not this week is information. It's better information than an unspoken no, which is what an ignored list item actually is. You'd rather know.

Let the reminders do the chasing

Here's the part that quietly saves your Sunday evenings.

Once a task has a due date, Blinko does the follow-up. On the day it's due, a nudge. If it's still open the next day, another one, and this time it says overdue. Still open at three days, and at a week, and by then it says a week overdue — which lands differently, without either of you having chosen a tone.

Each of those fires once, in the morning, in the assignee's own timezone. Not a badge that pulses forever, not a red number that becomes wallpaper by Thursday. One notification per rung, and then silence until the next rung.

At the week mark it escalates to the person who asked, too — still open — so you find out from the app rather than by discovering, again, that it hasn't happened.

Which is the point. The reminding still has to happen; someone has to be the one who remembers the boiler. The change is that it stops being a person in your house. You wrote the ask down once, and after that the chasing is the app's job. You get to just be someone who lives there.

Done is theirs to mark

Only the assignee can mark a task done. Not the person who asked, however sure they are that they saw the plumber's van.

That sounds like a small permissions detail and it isn't. It means done is a statement made by the person who did the thing, which means it can be trusted, which means nobody has to audit anything. The requester's affordance is a Remind button. That's the correct amount of power to hold over another adult.

Tapped it by accident? There's an Undo right there in the confirmation, and it puts the task straight back. Discovered a fortnight later that the plumber patched it rather than fixed it? Either of you can reopen it.

Both routes are the same move underneath, and both are visible. The other person is told the task is back on their list, and if it lives in a group, the group sees it was reopened. The app warns you about that before you tap, in as many words. Nothing gets quietly un-done behind someone's back — which is the only reason done was worth trusting in the first place.

What it deliberately doesn't do

No priority matrix. No recurring-chore engine. No points, no streaks, no dashboard of who did more this month — which is a scoreboard, and scoreboards are how a shared to-do app for couples turns into a shared grievance.

Tasks sit in the same place as the rest of your life together: your chat, alongside the plans. The wine bar you keep meaning to book and the boiler you keep meaning to service are the same kind of object, which is honest, because they're both just things that need a name and a date before they'll happen. If the fun half is the bit you'd rather sort out first, that's the date night loop, and it works exactly the same way.

The version worth having

You don't need a system. You need the boiler booked, and you need to not be the person who has to bring it up again.

One name on it. One accept. Four reminders that arrive without your fingerprints on them, and a done that only the doer can say.

Blinko is free on iOS and Android, on a free forever plan — every feature, both of you, no ads.

See what Blinko Spots does →