Markdown Task Planner
Product Shape
Local-first Markdown-native planning app with Linear-like keyboard UX, fast search, local files as source of truth, and cross-platform desktop availability.
Ladder Result
Pick desktop shell plus sidecar. The research recommendation is Electron + Go sidecar for this specific app shape.
Why Electron Can Beat Tauri Here
| Constraint | Stack implication |
|---|---|
| Command-palette-heavy UX | Chromium consistency matters for focus, positioning, keyboard behavior |
| Cross-platform desktop | One renderer lowers UI testing variance |
| Markdown file watching | Go sidecar handles filesystem/indexing work |
| SQLite/FTS cache | Sidecar keeps heavy work out of renderer |
| Developer audience | Desktop app is justified, but CLI integration can still exist |
Avoided Stacks
- Pure PWA: weak for local folder watching and editor-adjacent workflows.
- Tauri by default: lighter, but WebView variance can create UX support burden.
- Backend SaaS: violates local-first Markdown ownership.
- Mobile-first: not the core user workflow.
First Quality Gates
- Watch a folder of Markdown files.
- Build an SQLite/FTS index from tasks.
- Command palette responds instantly with keyboard navigation.
- Package a desktop build on the first target OS.
- Verify file changes round-trip without corrupting source Markdown.