Replace Dabble?
KINDA · weekend projectThe core loop is buildable, but a dependable replacement becomes a real weekend or multi-day 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.
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.
$ 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 Dabble because the paid tool is already present everywhere they write and its suggestions have been tuned across millions of documents. The recurring cost buys model quality, extension compatibility, dictionaries, releases, and sync, not just the visible interface.
xcloud sync, mobile access, goals, and polished manuscript organization
xcross-device sync
xlarge proprietary style models
xbrowser and office-suite extensions
xteam style guides
What does the Dabble verdict mean?
The core job looks buildable, with meaningful gaps: cloud sync, mobile access, goals, and polished manuscript organization, cross-device 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 Dabble?
The directory records $14/month for Basic, 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 Dabble?
Honestly: cloud sync, mobile access, goals, and polished manuscript organization; cross-device sync; large proprietary style models; browser and office-suite extensions; team style guides. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Dabble?
The listed prior art includes LanguageTool (Mature open-source grammar and style checker with desktop and server components.). Inspect those projects before starting from a blank prompt.