Notesnook vs Rize
Side-by-side trajectory, velocity, and editorial themes.
Notesnook is on a steady alternating Desktop/Android point-release cadence with no inline changelog detail.
Notesnook is shipping a Desktop or Android point release roughly every 3–4 days (Desktop v3.3.15 → v3.3.19, Android v3.3.20 → v3.3.24). The GitHub release notes are uniformly empty — each one points to the blog rather than enumerating changes. The one detail-bearing release in the window (Desktop v3.3.16) was entirely bug fixes: scrollbar cutoffs, submenu lazy-item cutoffs, urgent-reminder segfault on Linux, backspace crash, paddle iframe crash, note-subtitle length cap.
The product is in a maintenance-and-polish phase on both Desktop and Mobile, judging from the one release that did publish detail and the steady point-bump pace. The opaque release notes are themselves a signal: directional reading has to come from the company blog, not the repo. There is no public hint of a 3.4 or 4.0 cut in this window.
Cadence continues — another paired Desktop/Android release within the next week, almost certainly more crash and UI fix work in line with the v3.3.16 pattern.
Rize pivots from passive tracker to live, AI-queryable work data substrate.
Rize landed two directional moves in the last 30 days: live time-entry creation that replaces the previous batched-after-the-fact model, and a Beta MCP server that exposes time tracking data to Claude and ChatGPT for natural-language analysis. Around those, the team rebuilt the time-entry review panel and added an alternative Work Hours calculation that excludes break time the way most teams actually want. Cadence is high and the releases are coherent, not scattered.
The product is repositioning itself from 'passive tracker that classifies activity later' to 'live work-data platform other AI tools can read.' MCP integration signals Rize wants to be the data layer external assistants reach into, not a self-contained reporting app. The live-entries shift is the user-experience counterpart: data is current and editable in the moment instead of reconstructed later.
Expect the next moves to lean into the new substrate: manager-facing project-overrun alerts, budget-vs-actual dashboards, or richer outbound webhooks. A natural follow-on is broader MCP exposure (write-side actions, not just read), or a chat surface inside Rize itself.
See more alternatives to Notesnook →
See more alternatives to Rize →