Can Akiflow be vibe coded?

Build brief — a focused alternative to Akiflow

**Verdict:** Partly, if you narrow it · **Buildability:** 63/100 · **Category:** Tasks Calendar

**Source:** https://www.canitbevibecoded.com/akiflow

Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Akiflow. Verify current pricing and capabilities before acting.

Context

**Akiflow** — Command-center planner that merges tasks, calendar, and time blocking. It currently costs $34/mo.

The planner UI can be built, but bringing every task source into one reliable, two-way calendar workflow means OAuth, APIs, sync conflicts, and maintenance.

This brief describes a focused, single-operator replacement for the part of Akiflow 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

Ingest tasks from selected tools, show an inbox, drag into a calendar, create time blocks, and push updates back.

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

Integrations to task apps.

Hosted backend.

Background sync.

Notifications.

Data and integrations

Google/Microsoft OAuth.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

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 daily planner with time blocking to replace Akiflow. Requirements:

Local web app: Node + Express + better-sqlite3; the day/week grid is

FullCalendar with vanilla JS, no build step.

A capture inbox: one text box, Enter saves a task; tasks have title,

minutes estimate (default 30), and a done flag.

Drag a task from the inbox sidebar onto the grid to create a time block;

drag to move or resize; block and task stay linked, completing one

completes the other.

My real calendar shows behind the blocks as a read-only overlay of ICS

feed URLs from .env; Google Calendar's secret ICS address works and needs

no OAuth.

Keyboard-first: n for new task, t for today, arrows move selection, Enter

schedules the selected task into the next free slot.

Morning rollover: unfinished blocks from yesterday return to the inbox

with a reschedule counter, so chronically avoided tasks are visible.

SQLite storage, localhost only, no accounts, no telemetry.

Out of scope: two-way Google/Outlook sync and pulling tasks in from other

apps. Read-only overlay only; OAuth plus sync-conflict handling is exactly

the maintenance that makes Akiflow worth paying for.

README: how to find a calendar's secret ICS URL.

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:

Wide integrations.

Two-way sync.

Keyboard UX.

Mobile/desktop apps.

Connectors, OAuth flows, and vendor API changes require constant upkeep.

The last 20 percent is sync, migration fidelity, speed, and edge cases.

What you still own after launch

Secure credentials, rotate secrets, and handle provider rate limits.

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:

[Super Productivity](https://github.com/johannesjo/super-productivity) — Open-source personal productivity app that covers portions of time blocking and task plann

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