Hey everyone, if you give nocal a try, we'd love to hear your feedback here, or feel free to email us at inquiries@nocal.app.
I also wanted to share a preview of the roadmap that should take us through the summer. We are largely driven by user feedback, so please feel free to give ideas, weigh in, etc.
By priority:
Calendar defrag (Automatically surface and execute opportunities to better stack meetings and reclaim more focus time
Write-to-local. Point nocal at a directory with markdown files and read an write to that location. This allows easier transport between nocal, other tools like obsidian, and AI, but has some really complicated aspects to it since nocal is based on ydoc and is a set of rich components that can fully be represented in markdown.
nocal for iPad and Android tablets (and foldable phones)
UI improvements and reworking: As we see everyone using nocal, continuing to iterate on the form factor for mobile and desktop.
nocal
The workspace-calendar blend is interesting — most calendar apps treat tasks and events as separate, but they're really the same thing with different urgency. How do you handle the capture side? Getting tasks in quickly is usually where these tools lose people
nocal
@soygus nocal is all about the idea of the weekly scratchpad. Tasks are captured as markdown checklists, given UUIDs, and tracked throughout their lifecycle. This way as tasks get moved from week to week, or copied to other notes, the lineage is retained, and tasks benefit from being a first-class entity that can be surfaced in interesting ways.
But capturing tasks is as easy as writing markdown, which works really well when you connect your existing agents in via mcp.
I really appreciate how nocal rethinks the calendar as more than just a grid of events. The ability to write Markdown notes and tasks directly in the weekly view, reference events with @‑mentions and even have AI assistants update your notes via MCP is a unique take on unified productivity. A couple of things I’m curious about: How deep does the task management go (e.g., reminders and deadlines), and what safeguards are in place when letting agents write back to our notes?. Keep it up :-)
"Calendar that thinks like a workspace" maps onto the broader pattern that single-purpose tools (calendar, notes, tasks) collapse into one when the underlying state is the project, not the artifact. The real test for this category is whether the unified view actually changes how you make decisions, not just where the data lives. Tangentially relevant — we hit the same problem on DishRoll (a weekly meal-planning PWA): the value isn't a calendar of meals, it's the planning loop (preferences → plan → grocery → cook → feedback) reflected back as one workspace. Curious whether nocal's Spaces concept handles cross-project dependencies (a meeting in Project A that references a doc in Project B), or if Spaces stay siloed by design?
Been using nocal for a while and it's really changed how I plan my week. Having notes, tasks, and meetings all in one place instead of bouncing between apps is exactly what I didn't know I needed. Love the direction of 4.0 with the cross-platform support. Congrats on the launch @brianmuse
nocal
@ola_halvorsen Thanks Ola! nocal has been incredibly fulfilling to build out, and the "didn't know I needed it" line is the highest compliment. Collapsing calendar, notes, and tasks into one place was the bet I most wanted someone outside my head to validate. v4 cross-platform was a long road but feels worth it.
PoemGPT
Love this direction calendars should work the way projects actually work. Meetings, notes & tasks together just makes sense 👏
nocal
@basavaraja Thank you for the support <3
Theneo
This looks amazing, congrats
nocal
@ana_robakidze Thanks! It's been a blast working on it.