The passport renewal sat in my task list for three weeks with a due date on it. The reminder fired at 9:00 in the morning on the day it was due, exactly as I had set it. I was on a bus. I read it, thought "right, the passport office," and swiped it off the screen because there was nothing else to do with it.
The reminder did its job. I still missed the thing.
That gap is the whole problem. People go looking for a reminder app that actually works, and what they describe is never an app that fires. Every app fires. They want one that fires while they can still act, and survives the four seconds after it lands.
The alert is welded to the deadline
In most task tools, reminder and due date are the same field. You set the due date, the alert comes at the due date, and the tool tells you about the job at the exact moment you can no longer do it.
The invoice is due today. You get told today. You needed to be told Thursday, when you had forty free minutes and the file open. The useful alert time is almost never the deadline. It's an earlier point the tool can't represent, because it has one date field and already spent it.
So in Vyneron a task carries a due date and a separate list of extra reminder times. In the web app that field is a list: the first entry is your due date, the rest are extras you stack on top. Or you say it in chat, plain: "also remind me the evening before." The scheduler checks every 60 seconds, so an alert set for 17:20 lands at 17:20, not at the top of the next hour.
One small thing that took me too long to fix: set a due date with no time on it, and the reminder does not fire at midnight. It fires at 08:30 in your own timezone. Midnight alerts are a bug wearing a feature's clothes.
The reminder arrives with nothing to do
Back to the bus. That passport reminder died because it gave me one option: look at it. Nothing to act on inside the notification, so the only move my thumb had was to clear it. And a swipe looks exactly like handling it. The system logged a delivery. I logged nothing. The task went invisible for another three weeks.
A reminder you can't act on the moment it lands isn't a reminder. It's a guilt ping.
Every reminder we send arrives with four actions attached inline: Done, +2h, +1d, Delete. Buttons in the Telegram message, buttons in the web app's chat panel. In the app you can ignore the buttons and reply to the reminder with a word instead: "done", "2h", "tomorrow", "postpone". Those are read in all six interface languages, so a German user never has to switch to English to postpone something. In Telegram, replying to the reminder message works the same way in plain language, because the bot already knows which task that message was about.
The buttons aren't the point. The point is that "I can't deal with this now" becomes a recorded decision instead of a swipe that erases the task from your attention.
Twelve red badges means zero red badges
The other failure is slower, and it killed every reminder setup I've had. Something goes overdue. The app nags. Another thing goes overdue. Now two nags. By the end of a busy month twelve red things sit on the screen and you have stopped reading them, because a wall of red carries exactly as much information as no red at all.
Per-item nagging trains you to stop looking. The feature defeats itself.
So overdue in Vyneron isn't per task. One digest, once per person per day, at an hour you pick (08:00 local by default), covering only tasks past a grace window you set yourself. Grace defaults to 24 hours. The options are 0, 12, 24, 48, 72 hours, or a week. If you always run a day behind, set 48 and it stops naming things you'd have got to anyway.
A second setting decides how many channels fire. We deliver over Telegram, Slack, browser push, email, and an in-app feed, and the default is "single": one ping per reminder, sent to the first channel you have connected, in that order. Switch it to "both" and it fans out to everything. Leave it on single. Four notifications for one task is how you teach yourself to mute an app.
It fires in the wrong reality
Two versions of this. The first is travel. You fly, your phone changes timezone, and yesterday's reminders come back around to hit you again. We log every fired reminder against a key built from its UTC timestamp. Land somewhere new and yesterday's alerts stay yesterday's.
The second is the calendar. A routine set for the first of the month fires on a public holiday, the bank is shut, and you can't do the thing anyway. You dismiss it, mean to fix the rule, never do. Our holiday-aware routines know public holidays in 250+ countries with no calendar sync to set up, and a routine that falls on a holiday doesn't fire that day. Every reminder time is computed in your own timezone, not the server's.
None of this is the product, by the way. Reminders are one layer of a workspace with priorities and statuses, sub-tasks, blockers where one task can't start until another finishes, notes, files, projects, labels, assignees and roles, AI chat and voice. You can set it up from Telegram with @VyneronAIBot in about two minutes, and if you'd rather run the AI on your own API key from Gemini, OpenAI, Groq or Anthropic, it runs at zero markup.
Where this still falls short
The action buttons work from the Telegram message and inside the app. On a browser push notification they aren't wired up yet, so tapping a push reminder just opens the app. If push is your only channel, you get the timing fixed and not the one-tap postpone. It's on the list.
FAQ
Can I get a reminder before the due date instead of on it?
Yes, and that's the normal case, not a special one. A task carries a due date plus its own list of extra reminder times, independent of the deadline. Add them in the web app's reminder list, or say it in chat: "also remind me the evening before."
How do I stop getting buried in overdue notifications?
Overdue arrives as one daily digest per person, not one alert per task, and you pick the hour. You also set a grace window before anything counts as overdue, from zero hours up to a full week, 24 by default. The channel setting defaults to "single", so one reminder is one ping.
What happens to my reminders when I change timezone?
We compute every reminder time in your timezone, and we record each fired reminder against a key built from its UTC timestamp. Old reminders don't re-fire when you land somewhere new. The future ones shift with you.
Seven days of Pro free, no card. After that it's $6/mo or $59/yr.