Notesnook vs Aha!
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.
Aha! Builder is reshaping the product — prototypes, databases, and an MCP server land in the same week.
Aha! is shipping at a daily cadence and pushing in two directions simultaneously. First, the Builder surface is being fleshed out into a full prototype-and-validate environment: built-in databases with preview/production split, in-app feedback widgets, prototypes saved as records linked to product work, AI-assisted feature mockups. Second, AI is being layered across the existing PM workflow — an MCP server that exposes Aha! data to Claude, ChatGPT, and Copilot; AI-built customer-insights reports; AI-assisted roadmap presentations. A new HubSpot integration on the Ideas side rounds out the recent moves.
Aha! is positioning to defend its roadmap-software seat against AI-native challengers (the Productboard comparison post is a tell) by becoming the layer where product managers prototype, validate with users, and connect the result back to the roadmap. The Builder line is the strategic bet — taking PMs out of Figma/Retool tooling and keeping them in Aha!. The MCP server matters in parallel: it positions Aha! as a data source for any agent runtime, not just as a destination workflow tool.
Expect Aha! Builder to be packaged as a standalone SKU (or upgraded tier) within the next quarter, given how complete the prototype-database-feedback loop now is. The MCP server is likely the first of several agent-integration surfaces; a second wave will probably target Linear/Jira-style sync agents that bridge Aha! into engineering execution tools.
See more alternatives to Notesnook →
See more alternatives to Aha! →