Should I vibe code
Cross-platform task manager for projects, reminders, and recurring tasks
Natural-language date parsing is the only hard bit, and it is a solved library.
?
Their verdict, the Pro price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-03.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
A cross-platform task manager is ambitious; a single-device one that syncs a plain file is not, and it covers most of what you actually do.
What actually breaks
not "if". the specific failures.
- Natural-language dates, where 'next Friday' on a Thursday means one thing to your parser and another to the person typing it
- Ambiguity resolved silently, so a task lands on a date nobody chose and is discovered by missing it
- Cross-platform, which is where the effort actually goes — the same behaviour on desktop, phone and web is three implementations
- Reminders, which require notification permissions, background delivery and a scheduler that survives a device restart
- Recurring rules expressed in prose, which is the natural-language problem again with more edge cases
You type 'call the plumber next Tuesday' on a Tuesday. Your parser resolves it to today, because the current day is technically the next occurrence of Tuesday, and files it as due now. You meant a week away. Nothing warns you, because the parse succeeded — parsers do not know when they have picked the less likely reading — and the only signal is a task appearing in Today that you were sure you had scheduled for later.
Is that you?
the verdict is a default, not a law
- The parsed date is always shown before the task is saved
- You use an established date-parsing library rather than regular expressions
- It is your own list and a misparsed date costs you a reminder
- Parsed dates are committed without being displayed back
- You are writing the parser yourself with regular expressions
- Reminders are the point and you have not tested them surviving a restart
- You need identical behaviour across three platforms and have budgeted for one
If you build it anyway
the checklist, then the prompt that enforces it
- Always echo the interpretation: show the resolved date, in words, before saving. This single habit makes a wrong parse harmless.
- Use a maintained natural-language date library. 'Next Friday' alone has multiple defensible readings and the ambiguities are well documented.
- Set the reference timezone explicitly and test around midnight and daylight saving boundaries.
- Make the parse undoable and the date editable in one keystroke, since correcting is the common path rather than the exception.
- For recurrence, translate prose into an explicit rule and show that rule to the user rather than storing the prose.
- Test reminders across a device restart before relying on them — a scheduler that lives in memory is not a reminder system.
Before you build a task manager with natural-language dates, apply these and push back if I ask you to break them. 1. Always display the resolved date back to me, in unambiguous words, before the task is saved. Tell me that a parser cannot know when it has chosen the less likely reading, and that echoing the interpretation is what turns a wrong parse into a two-second correction. 2. Use a maintained natural-language date parsing library rather than writing regular expressions. Explain that phrases like 'next Friday' have several defensible interpretations depending on the current day. 3. Set the reference timezone explicitly rather than relying on the system default, and write tests for parsing near midnight and across daylight saving transitions. 4. Make the parsed date editable in one keystroke without retyping the task. 5. For recurring tasks, convert the phrase into an explicit rule such as RRULE, display that rule, and store the rule rather than the original prose. 6. If reminders are in scope, use the platform scheduler and verify delivery after a device restart before treating them as reliable. 7. Ask me how many platforms this must work on, and tell me honestly that each one is a separate implementation of the same behaviour. 8. Keep tasks exportable as plain text or CSV from the first version. 9. Out of scope unless I ask: collaboration, sub-projects, filters and labels with query syntax, karma or gamification.
That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
$7 a month buys date parsing tuned against enormous real usage plus native apps on every platform. The parser is a solved library and the single-platform version is a genuinely good weekend — buying is mostly about wanting the same list on a phone without building it twice more.
Export tasks with their resolved dates rather than the phrases that produced them, since the phrase is only meaningful relative to when it was typed. Plain CSV or Markdown keeps years of completed tasks readable without the parser that created them.
Open-source task/project management app suitable as a Todoist-style alternative.
Questions
What does 'next Friday' actually mean?
It depends who you ask, which is the problem. On a Wednesday, some people mean in two days and others mean the Friday of the following week; on a Friday, almost nobody means today. There is no correct answer to encode — which is why the fix is not a better rule but showing the resolved date so the human can disagree with it.
Is date parsing really the only hard part?
It is the only conceptually hard part on one platform. The rest of the effort is breadth — the same behaviour on a phone, a laptop and the web, plus reminders that survive restarts. Those are not difficult so much as three times the work, which is what the subscription is mostly paying for.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
Merging tasks and calendar is easy. Merging them without one corrupting the other is not.
A personal task manager is the app every developer builds. Yours will fit your brain better.
Tasks, habits, a timer. Three small features you will actually use because you chose them.
last reviewed 2026-08-03 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice