iSpring
iSpring has moved AI from generating whole courses to sitting inside every text field.
A side-by-side editorial comparison of Blockly and LifterLMS — 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.
A WordPress LMS that just made its whole REST surface discoverable to AI clients.
LifterLMS spent June on a run of security-only patches — checkout order creation, quiz start, REST authentication, import user creation, each crediting an outside reporter — before shipping 10.1.0, which registers its REST endpoints for courses, sections, lessons, memberships, access plans, students, enrollments and progress as WordPress Abilities API abilities. That release also added wp llms CLI commands for course enrollments and course structure, and shipped a docs/ai-agents.md guide naming Claude Code, Cursor and Codex as intended clients. The 10.1.1 follow-up is bug fixes plus more entropy in generated order keys.
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.
LifterLMS spent June on a run of security-only patches — checkout order creation, quiz start, REST authentication, import user creation, each crediting an outside reporter — before shipping 10.1.0, which registers its REST endpoints for courses, sections, lessons, memberships, access plans, students, enrollments and progress as WordPress Abilities API abilities. That release also added wp llms CLI commands for course enrollments and course structure, and shipped a docs/ai-agents.md guide naming Claude Code, Cursor and Codex as intended clients. The 10.1.1 follow-up is bug fixes plus more entropy in generated order keys.
The direction is clear from what got built around the Abilities API integration: not just the registration, but CLI commands that return a whole course structure in one call and a written guide for driving the plugin from an agent. That is a plugin being deliberately shaped for machine operation rather than exposing an API and hoping. Running underneath it is a sustained security pass — the June patches plus the order-key entropy fix — which is the necessary counterpart to opening the surface up.
Expect the AI-agent documentation and CLI commands to expand faster than the web UI, since the recent releases put more new capability behind wp llms and the abilities registry than in the admin.
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 LifterLMS.
iSpring has moved AI from generating whole courses to sitting inside every text field.
Challenge evaluation is quietly becoming a real feature inside the daily deploy train.
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.
See all Blockly alternatives → · See all LifterLMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LifterLMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. LifterLMS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 LifterLMS alternatives in EdTech are ranked by recent ship velocity. Browse the "LifterLMS alternatives" section above for the current picks, or visit /alternatives/lifterlms for the full list with editorial commentary on each.