The honest answer first
No. Storyline is not dead. If you build real interactions with variables and triggers, the kind that turn a wall of Moodle text into something a human will actually finish, you are getting genuine leverage out of it, and a dropdown plus a PDF is not going to replace that. Anyone telling you it is already dead is usually selling their own AI tool.
But "is it dead" is the wrong question, and I think you half know that, because you did not ask whether Storyline is still good. You asked whether your company can stop paying for it. Those are different questions. Storyline is not dead. It is getting much harder to justify on cost, and that is a fair thing for your leadership to be poking at.
The bind you are actually in
Leadership wants more interactivity and also wants to cut the one tool you build interactivity with. That is not a strategy, it is a contradiction, and you are the person standing in the middle of it. You have done the right thing by spelling out that the activities live inside Storyline and do not survive its removal. Most cuts like this happen because nobody upstream realised what was attached to the thing they were cancelling.
What has actually changed
For about twenty years, if you wanted custom interactivity and you could not write web code, you bought an authoring tool. That was the deal. Writing the underlying HTML, CSS and JavaScript by hand was a specialist job, so Storyline, Captivate and the rest sold you a way around it.
That is the thing that has changed. AI can now build genuinely interactive HTML from a plain-English brief: variables, branching, drag activities, scored questions, the lot. Not a slideshow with a next button, real web interactions. So the monopoly that authoring tools held, being the only way a non-coder could make interactive things, has cracked. Storyline did not get worse. The road around it opened.
So should you drop it
Keep it if you lean on mature interaction types, you ship a lot quickly, and your team only knows Storyline, because retraining can cost more than the licence. Reconsider it if you are paying around 1,449 pounds a year per seat for a fraction of what it can do, or if you have ever resented handing a client a .story file they cannot even open without buying the same tool you did.
The thing nobody mentions: what the client ends up with
With an authoring tool you rent the software, and the client receives a source file they can only edit if they also buy that software. With HTML, you or the AI build it, you own the files, and the client gets an open deliverable that any future developer, or any AI, can edit with no licence at all. If you freelance, that is not a small thing. "You own this and it is not locked to my tool" is a genuinely strong line to a client.
About that PDF equivalent
This is the bit I would gently push on. A PDF sitting next to an inaccessible interaction is a fallback, not accessibility. It is the separate-but-equal of e-learning, and it does not actually satisfy WCAG, which is about the content itself being usable, not about there being a second version for people who cannot use the first. Built properly in HTML, the interaction is accessible in the first place: keyboard operable, screen-reader friendly, captioned, no parallel PDF required. Getting an authoring tool's published output fully accessible is famously fiddly. This is quietly one of HTML's biggest advantages, and it is the one procurement will care about most in the next couple of years.
Will it work in Moodle
Yes. Wrap your HTML as a SCORM 1.2 package and Moodle runs it like anything else: launches it, tracks completion and a score. SCORM 1.2 is the universal format and Moodle has spoken it for years. So "Moodle-friendly" is not the constraint it feels like. The HTML you build does not have to live outside your LMS, it goes in exactly where your Storyline output goes now.
What we are building, since it is relevant
In the interest of being straight with you, this is our blog, so here is the disclosure. We build the AI Learning Packager, which wraps HTML you or an AI made into a SCORM 1.2 package for any LMS, with an accessibility check built in and xAPI support for richer tracking (cmi5 coming soon). We are also building a course that teaches instructional designers to do exactly this. We are not doing it because Storyline is dead. We are doing it because there is now a credible road that does not involve renting a tool or locking your client in, and somebody should make that road easy to walk. We treat Storyline's strengths as the benchmark to beat, not the enemy.
The actual answer for you
For you specifically, fifteen years in and leaning hard on variables and triggers, the licence probably still earns its place today, and I would not drop it on the strength of a forum thread. But I would learn the other road this year, because the gap is closing quickly. The next time leadership asks you to cut the tool, "here is how I build the same activities without the subscription, and the client owns the result" is a far stronger hand than "I cannot work without it."
Not dead. No longer the only option. The real question is whether the subscription earns its place for the work you actually do. Answer that honestly and you will know what to tell your leadership.
Written by Michael at Digital Technology Training. The AI Learning Packager is in private beta. If you want to wrap HTML content as SCORM 1.2 without touching an authoring tool, request access below.