I got a question for ya'll: Is the eLearning authoring tool as we know it dead? It's a question I’ve been thinking about a lot lately. So, let's discuss! Ya know, a few months back, I invited Jeff Batt into my community to talk about vibe coding...and one of the things he showed was how he was using tools like Lovable to essentially vibe code his own eLearning authoring tool. And I gotta say...it was pretty damn impressive. Since then, I’ve seen more and more people using vibe coding to build custom interactions and other learning elements, and then embedding those into the tools they already use. And this is what got me thinking... If we can vibe code the interaction, at what point can we vibe code the whole learning experience? And if we can do that, then what exactly is the authoring tool for? Is it just a familiar interface? A publishing wrapper? A SCORM machine? A place to organize content? Maybe. But AI can increasingly do those things too. So, at what point does the AI tool stop being the assistant… nd start becoming the authoring environment itself? Well, that’s exactly what I talked about with Melissa Milloway in my new video. 🔗 Watch the full video here: https://lnkd.in/g4xf3rMi Otherwise, I'm curious where you land on this: Do you think traditional authoring tools still have a clear long-term role, or are we watching that category start to break apart? Let me know down in the comments! See ya around! —Tim #eLearning #InstructionalDesign #LearningAndDevelopment #VibeCoding #AI
As customizability expands, I think reliability will become a priority. When you have a compliance-driven organization and the record of training is more important than the delivery mechanism, it's important that certain processes are reliable. The current authoring tools are tested in that they will consistently work on the back-end with the LMS software that meets the record-keeping requirement. If the vibe-coded eLearning produces an error on completion one out of every 200 times it is completed, you may not notice it when you're testing. However, when you launch it to an audience of 50,000, you'll flood the IT help desk with tickets. "I did this training; why isn't it appearing in my transcript?" This may be the same same help desk that provides T1 support to the patient health records system, which could cause a compromise in patient care. That's one scenario; there are hundreds more. I could see a scenario where a much more simplified (possibly open source) wrapper for SCORM compliance replaces the authoring tool. Then vibe code all you want for the non-infrastructure portions of your content.
You know how I feel about AI in general lol. But staying focused just on capabilities alone, I am extremely surprised we haven’t seen a competitor to Articulate crop up already because of vibe coding, and even made a comment on one of Heidi Kirby, PhD ‘s posts about this. AI is in a hype stage where everyone and their mother is eager to try it out, and a lot of the output is just slop (images, designs, apps, it’s content agnostic.) But this is not because AI is inherently trash, it’s because of the mindset of most people using it. Most people are not using it to solve real problems, they are using it to build “cool” things they didn’t know how to build before. No disrespect to them either, most of them are just getting their feet wet and giving it a try. Once AI is more firmly in the hands of real teams full of SEs Designers and PMs that could ‘build the thing’ even without AI’s help, the faster they will be able to ‘build the thing’ as solutions to real problems they have already researched and understand well.
I’ve been wondering the same thing. I’ve been building custom learning for years. When standard tools didn’t do what I wanted them to do. Way before AI. I’ve then SCORM wrapped it for it to work in an LMS. So it’s for sure possible to not use an authoring tool, but AI makes it easier to do more now, so it’s for sure a valid question. It does take IMO still some technical strategy, especially to make it reusable, but it’s for sure within reach and doable. While I still think authoring tools have their place, I think they need to evolve to more prompt-based authoring like Lovable to stay relevant. So instead of us designing slides and adding triggers, we describe what we want and have it create the interaction for us. But I wonder if LMSs will even last because I’ve been working on my own platform like Circle, and I’m able to track video progress, do user management, create reports, and everything all from a Vibe Coded Lovable app. It does take more back and forth, but it’s for sure doable. I know Mel is doing some awesome work with vibe coding custom experiences, so it should be an awesome conversation you will have with her.
Tim, this is a great provocation! From my perspective, the “death of the authoring tool” conversation might be framing the shift a bit narrowly. In complex training environments, the real challenge has never been the mechanics of building interactions it’s the architecture of the learning experience and the ecosystem it lives in. AI and vibe coding will absolutely accelerate how we generate interactions or simulations. But tools like Articulate Storyline 360 still serve a larger function around governance, interoperability, accessibility, and scalable deployment especially in regulated or enterprise contexts. So I’m less convinced we’re watching the category die and more convinced we’re watching it redefine itself. The real shift may be that designers move further upstream, spending less time assembling screens and more time shaping the learning architecture, performance context, and evaluation strategy. If anything, AI raises the bar for what good instructional design actually looks like.
Some authoring tools may become SCORM machines. Because content produced with vibe coding may or may not work with certain LMS systems. I think vibe coding will be another tool that complements apps like Articulate 360.
It's an interesting idea, but how would that work with teams when more than one person is contributing to authoring? And what about maintenance? What happens when someone needs to update a course down the road, like if you've passed it off to your consultancy clients to maintain and make updates as needed after your work for them has concluded 🤔 I think at this stage there are still plenty of reasons for continued use of existing authoring tools
I think the role of an authoring tool might be shifting, and the go-to standard tools might fall off. AI can handle more and more of the actual build, but what it can't do is know why a specific interaction earns its place in a course or help you make that case to a stakeholder.
I think we are getting closer to where e-learning tools will need to catch up quickly or learning teams will continue to upskill in this direction. Imagine a team using MindSmith.ai with Lovable and deploying solutions. In my mind, Articulate needs to move towards a MindSmith model soon to stay relevant overtime.
Hey All! The full video is live here: https://youtu.be/5fr1csKM5L8?si=q7S5sDs_4PRBpqJi