What's next for deariary

deariary launched on March 10 with eight integrations, three pricing plans, and a simple promise: your diary writes itself. Thank you to everyone who signed up in the first week.

Now that the product is live, we want to share what we are focusing on next. Four areas, in order of priority.

1. Diary generation quality and reliability

This is the foundation. If the diary entry is not good, nothing else matters.

We are working on:

• Sync reliability. Some integrations occasionally miss events or delay data collection. We are tightening the pipeline so every day’s context arrives before diary generation runs.
• Better writing. The LLM-generated entries today are functional, but we want them to feel more natural. Short-term improvements include better prompt tuning and smarter context selection (picking the moments that matter instead of listing everything).
• Error handling. When an integration connection breaks (expired tokens, API changes), you should know immediately, not discover it three days later in a thin diary entry. We are adding health checks and notifications.

2. More integrations

Eight integrations cover a lot of ground, but everyone’s daily life is different. The integrations we are evaluating next:

• Weather: daily weather is one of the strongest memory triggers, and it requires no user authentication
• Discord: for communities, gaming groups, and teams that live in Discord
• Strava: for runners and cyclists who want their routes in context
• GitLab: the same developer diary experience we built for GitHub, for GitLab users
• Trello: board activity, card completions, and due dates
• Last.fm: what you listened to is surprisingly good at bringing back a day
• Swarm (Foursquare): check-ins add a physical layer that pure digital tools miss

We prioritize based on user requests. If a service you use is missing, let us know.

3. Blog content and SEO

We are investing in this blog as a resource, not just a changelog. Upcoming content includes:

• Integration deep dives for every supported service, showing exactly what your diary entry looks like with each one connected
• Comparison guides so people evaluating journaling tools can make an informed choice
• Guides and tips to help existing users get better diary entries

We have already published a guide for GitHub, with more integrations coming soon.

4. User support

Right now, support runs through email. That works at our current scale, but we want to do better:

• Faster response times. Our target is same-day replies for all support requests.
• Documentation. We are building out a help section on deariary.com with setup guides, troubleshooting steps, and FAQs so you can solve common issues without waiting for us.
• Feedback loop. Feature requests and bug reports go directly into our planning. If you tell us something is broken or missing, it moves to the top of the list.

The principle behind all of this

deariary exists so that you can look back on an ordinary day and feel something. Every decision we make, from which integration to add next to how the LLM phrases a sentence, is measured against that goal.

We will keep shipping and keep writing about it here. If you have feedback, reply to any email from us or reach out at [email protected].