Replace Routine?
KINDA · weekend projectThe core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Routine, combine calendar, tasks, notes, and a command palette into one personal workspace. The hard boundary is calendar integrations, cross-platform apps, capture speed, sync, and polish, plus cross-device reliability and workflow polish.
Build a personal replacement for Routine in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and desktop notifications; do not offer alternative stacks. The core loop is: combine calendar, tasks, notes, and a command palette into one personal workspace, schedule or repeat tasks, work from a focused today view, and keep history locally. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create inbox, today, upcoming, someday, and completed views with fast keyboard capture. Support projects, tags, due dates, start dates, priorities, notes, subtasks, and attachments. Implement robust daily, weekly, monthly, and custom recurring rules with tests. Add a focus view with one active task, timer, and optional desktop notification. Provide search, saved filters, undo, and a completed-task archive. Export and import a documented JSON format and make automatic local backups. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out team assignment and comments. Deliberately leave out two-way calendar or email synchronization. Deliberately leave out native mobile apps and cloud accounts. Finish by running the tests and listing the exact commands used.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
People still pay for Routine because task software is sticky because trust, speed, and ubiquitous capture matter more than the database schema. The recurring cost buys recurrence edge cases, notifications, sync conflicts, calendar APIs, mobile capture, and backups, not just the visible interface.
xcalendar integrations, cross-platform apps, capture speed, sync, and polish
xperfect mobile sync
xcalendar and email integrations
xshared workspaces
xbehavioral coaching polish
What does the Routine verdict mean?
The core job looks buildable, with meaningful gaps: calendar integrations, cross-platform apps, capture speed, sync, and polish, perfect mobile sync. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for Routine?
The directory records $12/month for Professional, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing Routine?
Honestly: calendar integrations, cross-platform apps, capture speed, sync, and polish; perfect mobile sync; calendar and email integrations; shared workspaces; behavioral coaching polish. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Routine?
The listed prior art includes Vikunja (Mature open-source task and project manager with lists, kanban, and recurring work.). Inspect those projects before starting from a blank prompt.