IRLO Studio

The IRLO Studio roadmap

What is built, what is being built, and what comes after. This page changes as the work does.

Three horizons

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.

Next

A home for your team's own interactions

A private library of the plugins your organization builds for itself, versioned and reviewable, not a public app store.

Then

Courses as text

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.

Shipped

  • Interaction library

    More than 70 interactions, from drag-and-drop and flashcards to branching scenarios, all following one schema.

  • Blocks you can reopen

    Every interaction keeps its settings inside the course, so it can be edited later, even on a machine that never had the plugin.

  • Shared foundations

    One question bank, objective bank, media library, rubric builder, completion rule, LMS profile, and course theme that every plugin reads from.

  • Templates

    Finished example courses you can open from the start screen and build from.

  • Saved blocks

    Save a configured block under your own name to reuse it, or duplicate any block in one step.

  • Review copies

    Send a review copy that opens from disk with nothing installed. Comments come back against the interaction they are about.

  • Changes since review

    When comments arrive on an older version, the Review panel shows what has changed since it was sent.

  • Scoring at a glance

    Before you insert an interaction, the Insert list says whether it is scored and whether it counts toward progress.

  • Signed plugins

    Plugin packages are signed, and a package altered after signing is refused at install.

In progress

  • Delivery modes

    One page, slides, or numbered pages: choose how a course feels to the learner.

  • Course theme

    Type, spacing, and a logo alongside color, with defaults chosen for readability.

  • Edit blocks where they sit

    Change a block's settings in place in the course, not only its name.

Up next

  • Resume where the learner left off

    A learner who leaves a course comes back to where they were.

  • Network access, by allowlist

    Plugins reach only the sites you approve. This opens the way to deploy targets, LMS connections, and AI features.

  • File import and export for plugins

    Importers and packagers can be written as plugins.

  • Approved bridges to other apps

    Named, user-approved connections to software on your computer, such as Office or a local AI model.

  • Plugin checks in the SDK

    The same checks built-in plugins pass, available to anyone writing a plugin.

  • A plugin workbench in the app

    Build, check, and package a plugin without leaving IRLO Studio.

  • Know which plugin version made a block

    When a plugin is improved, find every block the earlier version made.

  • More than one author

    Two or more people working on the same course.

  • Work across a library

    Act on many courses at once, not only the one that is open.

Exploring

  • Getting content out of Storyline

    Bringing the content of existing Storyline projects into IRLO Studio.

  • Standards pre-flight check

    Catch SCORM and LMS problems before a course leaves your hands.

  • Branching scenarios

    Scenario graphs with path preview and a state budget that stays inside LMS limits.

  • Adaptive paths

    Courses that adjust to what the learner already knows.

  • Source tracking

    Tie each claim a course makes to the source document it came from.

  • Reaching learners away from the LMS

    Installable course apps, courses as PDF, facilitator guides, learning paths, and Open Badges.

Our commitments

Plugins build courses. They do not run them.

Uninstall a plugin and every course it helped build keeps working. No plugin becomes something your course needs in order to play.

Updates never rewrite a finished course

Improving a plugin changes the next block you insert, not a course a learner has already taken.

A small core

Structure, selection, and undo belong to the app. Everything else is a plugin.

The course carries its own state

Authoring state lives in the course file, not in a database, so the course outlives the tool.

Curated, not endless

A few hundred plugins that follow one schema and pass the same checks are worth more than tens of thousands nobody maintains.

Signed and reviewed first

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
v0.38.0