# Build brief — a focused alternative to Evernote

> **Verdict:** Partly, if you narrow it · **Buildability:** 65/100 · **Category:** Notes Knowledge
> **Source:** https://www.canitbevibecoded.com/evernote
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Evernote. Verify current pricing and capabilities before acting.

## Context

**Evernote** — Long-running note app for capture, search, tasks, and cross-device notes. It currently costs $14.99/mo.

A personal notes app with OCR/search/import is reachable, but the hard parts are migration, sync reliability, clipper UX, OCR quality, and years of user data.

This brief describes a focused, single-operator replacement for the part of Evernote 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 a Markdown/database notes app with tags, attachments, web clipper, OCR pass, and full-text search.

- Capture, organise, search, link, and export personal notes.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Desktop/mobile or web app.
- File storage.
- Search index.
- Browser extension if clipping matters.

### Data and integrations

- OCR library/API.

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 personal capture-and-notes app to replace Evernote. Requirements:

- A local web app: Node + Express + better-sqlite3, server-rendered pages,
  binds to localhost.
- Notes are Markdown stored in SQLite with tags, edited in a textarea with live
  preview via marked.
- Attachments: drag a file or image onto a note, stored in ./data/files/ and
  linked from the note. On upload, run tesseract.js OCR over images and PDF
  pages and store the extracted text so scans and receipts are searchable.
- Full-text search across notes plus OCR text with SQLite FTS5, search box in
  the header, tag filters beside it.
- Capture via bookmarklet: POSTs the current page's title, URL, and selected
  text into a new note. A bookmarklet, not an extension.
- An import script for Evernote .enex exports: notes, tags, and attachments,
  so my old data actually moves in.
- Weekly export of everything to a folder of .md files plus attachments, so
  nothing is ever trapped in the app.
- No accounts, no telemetry, all data on my machine.
- Out of scope: mobile apps, cross-device sync, a real browser extension.
- README: setup steps and where the data lives on disk.

## 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:

- Web clipper quality.
- Mobile apps.
- OCR/search maturity.
- Sync.
- Years of history, configuration, and habits make migration costly.
- 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.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

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

## Prior art

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

- [Joplin](https://github.com/laurent22/joplin) — Mature open-source note app with sync, markdown notes, clipping, and end-to-end encryption

---

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