# Build brief — a focused alternative to Todoist

> **Verdict:** Yes, for personal use · **Buildability:** 81/100 · **Category:** Tasks
> **Source:** https://www.canitbevibecoded.com/todoist
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Todoist. Verify current pricing and capabilities before acting.

## Context

**Todoist** — Cross-platform task manager for projects, reminders, and recurring tasks. It currently costs $7/mo.

A personal task app with projects, recurring due dates, filters, and reminders is a one-sitting/contained build; collaboration and sync polish are the product moat.

This brief describes a focused, single-operator replacement for the part of Todoist that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Create task/project tables, natural-language due date parsing, recurring rules, reminders, filters, and local notifications.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Local or hosted database.
- Date parser.
- Notification channel.
- Optional mobile/desktop wrappers.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal task manager to replace Todoist. Requirements:

- A local web app: Node + Express + better-sqlite3, server-rendered, binds to
  localhost only. Keyboard-first: n for new task, x to complete, / to search.
- Quick-add parses natural language with chrono-node: "call Sam tomorrow 4pm
  #home p2" sets due date, project, and priority in one line.
- Projects via #tags, priorities p1-p3, free-text notes on any task.
- Recurring tasks stored as rrule strings ("every 1st", "every mon,thu");
  completing one schedules the next occurrence.
- Views: Today, Upcoming (next 7 days grouped by day), and per-project. Overdue
  tasks pinned red at the top of Today.
- Reminders: node-cron checks each minute and pushes due tasks to my phone via ntfy
  (topic in .env), plus a 7am digest of today's list.
- A t add "..." CLI for capture from any terminal.
- No accounts, no telemetry, everything in one SQLite file I can back up.
- Out of scope: collaboration, native mobile apps, and offline sync. Phone access
  is ntfy notifications, that is the trade.
- README: ntfy app setup on the phone and where the DB lives.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Native apps.
- Offline sync.
- Collaboration.
- Reminders reliability.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Vikunja](https://github.com/go-vikunja/vikunja) — Open-source task/project management app suitable as a Todoist-style alternative

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/todoist