Code.org
Code.org is repainting the whole platform while quietly hardening student account handling
A side-by-side editorial comparison of OpenBoard and Blockly — release velocity, themes, recent moves, and the top alternatives to consider.
An interactive whiteboard whose releases are Qt upgrades and PDF rendering fidelity.
OpenBoard publishes roughly once a year, and the entries are dominated by rendering correctness and toolkit maintenance. The most recent build moves to Qt 6.9 on macOS, Debian and Windows and fixes PDF glitches under DPI scaling and non-integer device pixel ratios. The build before it reworked thumbnails to be shared between board and document mode, added snapping for rotated items, and sped up the background loader.
Blockly makes keyboard and screenreader access the default, not a plugin
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
OpenBoard publishes roughly once a year, and the entries are dominated by rendering correctness and toolkit maintenance. The most recent build moves to Qt 6.9 on macOS, Debian and Windows and fixes PDF glitches under DPI scaling and non-integer device pixel ratios. The build before it reworked thumbnails to be shared between board and document mode, added snapping for rotated items, and sped up the background loader.
Nearly every named change traces to the same problem class: documents and drawings rendering wrongly on the hardware classrooms actually use — scaled displays, tablet erasers, Windows document switching. Alongside it the project has been widening how it can be built and extended, with CMake support for community Linux builds and a separate Latex2SVG converter whose output drags onto the board. Contributions cluster heavily around one or two individuals.
Expect the Qt 6 migration to keep generating platform-specific rendering fixes across the next builds, with new capability continuing to arrive as small companion tools rather than changes to the board itself.
This Blockly line shipped a major version in June that made the editor keyboard-navigable and screenreader-accessible by default, folding what had been the separate keyboard-navigation plugin into core and requiring custom blocks and fields to update their ARIA roles and labels. Everything since builds on that: a FOCUSABLE capability for components, paste placement near the focused block, added navigation shortcuts, an ARIA type-name method for fields, and translated field labels. The most recent releases are corrective, covering memory leaks, right-to-left rendering, and flyout behavior.
Accessibility has moved from an add-on to an architectural property of the editor, and the follow-on releases show what that costs: focus management, insertion markers, and field labeling all had to be reworked around it. The insertion marker rewrite is a good marker of the pattern, framed as a performance change but motivated by memory leaks in the focus-aware rendering path. Translation of field labels extends the same reasoning from assistive technology to language.
Expect continued hardening of the focus and navigation paths rather than new editor capability, since that is where every release since 13.0.0 has concentrated. The RTL and memory-leak fixes suggest the accessible rendering path is still settling.
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 OpenBoard or Blockly.
Code.org is repainting the whole platform while quietly hardening student account handling
ProProfs Training publishes buyer-intent listicles on a weekly clock; the product never appears.
TopClass's feed is association marketing essays, with one release post buried among them.
Classroom's release notes are now a Gemini rollout, and the student age gate just came down.
Moodle is modernising its frontend stack while hardening the base institutions audit.
Kajabi is building retention machinery around the community and the checkout.
See all OpenBoard 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. Blockly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Blockly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top OpenBoard alternatives in EdTech are ranked by recent ship velocity. Browse the "OpenBoard alternatives" section above for the current picks, or visit /alternatives/openboard 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.