DSpace
DSpace 10.0 lands and the 7.x line that most repositories run is now end-of-life.
A side-by-side editorial comparison of Seesaw and Blockly — release velocity, themes, recent moves, and the top alternatives to consider.
Seesaw's feed is marketing, not a changelog — case studies and district thought-leadership.
The Seesaw feed continues to be a marketing blog, not a product changelog. Recent posts are school success stories, district-leader thought-leadership on AI and system fragmentation, and partnership/localization announcements. There is no product-release signal here to read a roadmap from.
Accessibility moved from plugin to core, and v13 is now being hardened around that default.
Blockly shipped v13.0.0 in mid-June: keyboard navigation and screenreader support are on by default, and the separate keyboard-navigation plugin is folded into core and meant to be uninstalled. The two point releases since have been consolidation — a FOCUSABLE capability on IComponent, paste-near-focus, more navigation shortcuts, and a long tail of ARIA-label fixes. The v13 line arrived through nine betas, several of them carrying breaking changes that forced custom blocks and fields to declare their own roles and labels.
The Seesaw feed continues to be a marketing blog, not a product changelog. Recent posts are school success stories, district-leader thought-leadership on AI and system fragmentation, and partnership/localization announcements. There is no product-release signal here to read a roadmap from.
The messaging is aimed squarely at district-level buyers — framing Seesaw as the consolidating platform against tool fragmentation, and positioning around the AI conversation in K-5 without shipping AI features in this feed. It reads as top-of-funnel demand generation for the elementary LXP category.
Expect continued case-study and district-leadership content; genuine product news would need a different source than this blog feed.
Blockly shipped v13.0.0 in mid-June: keyboard navigation and screenreader support are on by default, and the separate keyboard-navigation plugin is folded into core and meant to be uninstalled. The two point releases since have been consolidation — a FOCUSABLE capability on IComponent, paste-near-focus, more navigation shortcuts, and a long tail of ARIA-label fixes. The v13 line arrived through nine betas, several of them carrying breaking changes that forced custom blocks and fields to declare their own roles and labels.
The work is shifting from making accessibility correct to making it fast and localizable. v13.2.0 rewrites insertion markers for performance and memory-leak reasons, exposes setAriaTypeName on fields, and allows translated field labels — the first release in this window where the accessibility surface is being tuned rather than built. Invalid-input handling that no longer relies on color alone points the same direction: the a11y pass is now reaching the visual layer, not just the ARIA tree.
Expect continued 13.x point releases in the same shape — ARIA and focus-behavior fixes plus targeted performance work on drag and rendering paths, with translation coverage extending to more built-in block strings.
Other EdTech products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Seesaw or Blockly.
DSpace 10.0 lands and the 7.x line that most repositories run is now end-of-life.
eduMe's feed is search-led L&D content, with personalized learning paths as the recurring pitch.
ProProfs Training publishes buyer-intent listicles, not releases.
A student information system that ships once a year and barely says what changed.
A French LMS shipping monthly patch releases with no story attached.
AI drafting reaches the slide deck — iSpring's core authoring format is now generated, not built
See all Seesaw alternatives → · See all Blockly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Seesaw and Blockly are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Seesaw and Blockly are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top Seesaw alternatives in EdTech are ranked by recent ship velocity. Browse the "Seesaw alternatives" section above for the current picks, or visit /alternatives/seesaw for the full list with editorial commentary on each.
Top Blockly alternatives in EdTech are ranked by recent ship velocity. Browse the "Blockly alternatives" section above for the current picks, or visit /alternatives/blockly for the full list with editorial commentary on each.