WriteDaily Today: 12 Years of Daily Writing, and Where It Could Go

WriteDaily launched in March 2013. Twelve years later, it’s still running — over 300,000 writing sessions, a Laravel migration, a gamification engine, and zero lost words.

This post is a checkpoint. Where we’ve been, where we are, and where I’m curious about going.

The State of the Product

WriteDaily is stable and well-maintained. The stack has been incrementally upgraded from the 2019 Laravel migration and now runs Laravel 10. The gamification engine has shipped 14 badge types and over 3,200 earned badges. LIWC sentiment analysis still runs locally against the original LIWC2007 dictionary. Export to Markdown and plain text is lossless. Annual security audits are in place, backups are encrypted, and there are no third-party trackers or analytics. No external APIs touch user data.

The product works. Users write daily. The stats accumulate. It’s exactly what I wanted it to be in 2013.

The Technology Arc

Watching the technology shift around a 12-year-old project has been fascinating:

WriteDaily has never been on the latest. It’s been on the reliable edge — using proven technology, shipping incrementally, prioritising stability over novelty. That choice has served the product well.

Where I’m Curious

Three directions I’m genuinely interested in, none of which are commitments:

AI-Powered Writing Feedback

The prototype works. A local model provides pattern recognition, thematic summarisation, and stylistic observations — all running on WriteDaily’s own server. The quality is good. The privacy architecture is sound. The question is whether the operational complexity is worth the user value.

Agentic Development

Coding agents are changing how I build software. For WriteDaily, the immediate application is maintenance — automated dependency updates, test expansion, security patches. Longer term, an agent that participates in feature development alongside human review could change the cadence of side project iteration.

The 2025 Rewrite Question

If I were building WriteDaily from scratch today, it would look different. Probably a lightweight frontend (HTMX or Alpine) with a minimal backend. Probably WebAssembly-based sentiment analysis running entirely in the browser. Probably no server-side processing of entry text at all.

But WriteDaily doesn’t need a rewrite. It needs maintenance, occasional features, and continued reliability. The Laravel stack is solid. The product works. A rewrite would solve problems the users don’t have.

What Stays the Same

The core offering hasn’t changed in 12 years: write 750 words a day, get data-driven insight into your patterns, and build a habit that compounds.

That’s still valuable. In an era of AI-generated content, the act of sitting down and writing your own words — honestly, daily — matters more, not less.

WriteDaily is here for that. Twelve years in, and still counting.