# Build brief — a focused alternative to Dabble

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

## Context

**Dabble** — Plan chapters, draft a manuscript, track plot threads, and sync a structured writing project. It currently costs $14/mo.

The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Dabble, plan chapters, draft a manuscript, track plot threads, and sync a structured writing project. The hard boundary is cloud sync, mobile access, goals, and polished manuscript organization, plus polish, integrations, and proprietary language models.

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

Plan chapters, draft a manuscript, track plot threads, and keep the structured writing project in local Markdown files that sync and export without uploading the document.

- 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

- MacOS, Windows, or Linux.
- Local files.

### Data and integrations

- Optional OpenAI or Anthropic API key for semantic rewrites.

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 a personal replacement for Dabble in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks.
The core loop is: plan chapters, draft a manuscript, track plot threads, and keep the structured writing project in local Markdown files that sync and export without uploading the document.
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 a three-pane editor with source text, suggestion list, and accepted-result preview.
Implement deterministic checks for repeated words, sentence length, passive constructions, and typography.
Add an optional API-backed rewrite action that sends only the selected passage.
Show every change as an accept-or-reject diff and support undo.
Import and export .txt and .md while preserving headings and lists.
Persist user rules, ignored terms, and recent documents in SQLite.
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 a browser extension.
Deliberately leave out Office or Google Docs plugins.
Deliberately leave out collaborative editing and cloud sync.
Finish by running the tests and listing the exact commands used.

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

- Cloud sync, mobile access, goals, and polished manuscript organization.
- Cross-device sync.
- Large proprietary style models.
- Browser and office-suite extensions.
- 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:

- [LanguageTool](https://github.com/languagetool-org/languagetool) — Mature open-source grammar and style checker with desktop and server components

---

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