Now
The best block editor for courses
Interactions that follow one schema, share one question bank, and produce accessible markup that has been tested against hostile input.
What is built, what is being built, and what comes after. This page changes as the work does.
Now
Interactions that follow one schema, share one question bank, and produce accessible markup that has been tested against hostile input.
Next
A private library of the plugins your organization builds for itself, versioned and reviewable, not a public app store.
Then
Courses you can compare, review, search, and version like any other text, and that software can read as easily as people.
Shipped. In progress. Up next. Exploring.
More than 70 interactions, from drag-and-drop and flashcards to branching scenarios, all following one schema.
Every interaction keeps its settings inside the course, so it can be edited later, even on a machine that never had the plugin.
One question bank, objective bank, media library, rubric builder, completion rule, LMS profile, and course theme that every plugin reads from.
Finished example courses you can open from the start screen and build from.
Save a configured block under your own name to reuse it, or duplicate any block in one step.
Send a review copy that opens from disk with nothing installed. Comments come back against the interaction they are about.
When comments arrive on an older version, the Review panel shows what has changed since it was sent.
Before you insert an interaction, the Insert list says whether it is scored and whether it counts toward progress.
Plugin packages are signed, and a package altered after signing is refused at install.
One page, slides, or numbered pages: choose how a course feels to the learner.
Type, spacing, and a logo alongside color, with defaults chosen for readability.
Change a block's settings in place in the course, not only its name.
A learner who leaves a course comes back to where they were.
Plugins reach only the sites you approve. This opens the way to deploy targets, LMS connections, and AI features.
Importers and packagers can be written as plugins.
Named, user-approved connections to software on your computer, such as Office or a local AI model.
The same checks built-in plugins pass, available to anyone writing a plugin.
Build, check, and package a plugin without leaving IRLO Studio.
When a plugin is improved, find every block the earlier version made.
Two or more people working on the same course.
Act on many courses at once, not only the one that is open.
Bringing the content of existing Storyline projects into IRLO Studio.
Catch SCORM and LMS problems before a course leaves your hands.
Scenario graphs with path preview and a state budget that stays inside LMS limits.
Courses that adjust to what the learner already knows.
Tie each claim a course makes to the source document it came from.
Installable course apps, courses as PDF, facilitator guides, learning paths, and Open Badges.
Uninstall a plugin and every course it helped build keeps working. No plugin becomes something your course needs in order to play.
Improving a plugin changes the next block you insert, not a course a learner has already taken.
Structure, selection, and undo belong to the app. Everything else is a plugin.
Authoring state lives in the course file, not in a database, so the course outlives the tool.
A few hundred plugins that follow one schema and pass the same checks are worth more than tens of thousands nobody maintains.
Open plugin submissions wait until signing and review are in place.
Want to shape what comes next? Join the early access waitlist, try the release candidate when it opens, and tell us what you need.
Join the Waitlist