iSpring
iSpring has moved AI from generating whole courses to sitting inside every text field.
A side-by-side editorial comparison of Blockly and Code.org — release velocity, themes, recent moves, and the top alternatives to consider.
Post-v13 cleanup: three beta tags in one evening, two of them carrying nothing at all.
Blockly is servicing the v13 line it opened in June with keyboard navigation and screenreader support on by default. The 13.2.2 beta train tagged three times in under three hours, but only beta.0 carries changes — an undo-stack corruption fix, a nested-tree traversal speedup, and focus restoration on toast dismissal. beta.1 and beta.2 record an empty commit range.
Challenge evaluation is quietly becoming a real feature inside the daily deploy train.
Code.org ships a dated deploy train most weekdays, each release a flat list of merged PRs with no grouping. The current train is carrying three threads at once: challenge evaluation, which has grown from model foundations to a frontend and now class-gallery listing endpoints; the Lab2 migration, which keeps absorbing Sprite Lab and Python Lab behaviors; and the codeai rebrand, which is now mostly cleaning up regressions rather than repainting surfaces.
Blockly is servicing the v13 line it opened in June with keyboard navigation and screenreader support on by default. The 13.2.2 beta train tagged three times in under three hours, but only beta.0 carries changes — an undo-stack corruption fix, a nested-tree traversal speedup, and focus restoration on toast dismissal. beta.1 and beta.2 record an empty commit range.
The work since v13.0.0 is consolidation around focus, rendering, and performance rather than new surface area — insertion markers rewritten for memory, connection-database updates sped up, field labels made translatable. Accessibility remains the organizing concern, now expressed as correctness fixes in the machinery that shipped rather than new capability. The rapid empty beta tags suggest release automation firing on non-code commits.
Expect a 13.2.2 final shortly, continuing the pattern of small fix batches on the v13 line. Nothing in these entries points to a v14 or a new feature theme.
Code.org ships a dated deploy train most weekdays, each release a flat list of merged PRs with no grouping. The current train is carrying three threads at once: challenge evaluation, which has grown from model foundations to a frontend and now class-gallery listing endpoints; the Lab2 migration, which keeps absorbing Sprite Lab and Python Lab behaviors; and the codeai rebrand, which is now mostly cleaning up regressions rather than repainting surfaces.
Challenge evaluation is the thread worth watching. It arrived as a data model in early August, gained an evaluation job and frontend a day later, and now has listing endpoints for class-wide galleries plus a rubric simplified to a flat list of integer levels — the shape of a teacher-facing grading surface rather than an internal experiment. Moderation, meanwhile, has finished its sweep: after Java Lab, Web Lab, and the Asset Manager, this train only adds error handling around lab sandboxes.
The class gallery and simplified rubrics point at challenge evaluation surfacing to teachers as a reviewable set of student responses. What the entries do not show is whether evaluation is automated or human — the rubric-as-integer-levels change reads either way.
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 Blockly or Code.org.
iSpring has moved AI from generating whole courses to sitting inside every text field.
Pear Deck's feed is mostly pointer entries; the AI assessment workflows are the one real thread.
Three straight digests point one way: OpenLearning is building for outcomes-based assessment.
IXL keeps enhancing its diagnostic, analytics, and curriculum breadth on a steady monthly cadence.
A listicle engine that opens on the reader's audit anxiety and never mentions a release.
Whatfix has spent two months naming a problem category it does not yet sell a product for.
See all Blockly alternatives → · See all Code.org alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Code.org is currently shipping more aggressively (velocity 6.3 vs 5.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. Code.org is currently shipping more aggressively (velocity 6.3 vs 5.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 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.
Top Code.org alternatives in EdTech are ranked by recent ship velocity. Browse the "Code.org alternatives" section above for the current picks, or visit /alternatives/code-org for the full list with editorial commentary on each.