r/lowcode • • Apr 18 '26

Learning design is getting vibe coding.

Not actually writing code. I mean talking about the goal, the learner's situation, the choices, the flow, the feedback, and then improving the experience instead of making each step by hand.

That sounds like a really interesting future for designing learning. A lot more interesting than just using AI to make more content faster.

It also fits with the idea of vibe coding for SCORM interactive courses, where structure and intent come first and output comes last.

I wonder if anyone else is thinking about it this way.

12 Upvotes

15 comments sorted by

1

u/Shot_Ideal1897 Apr 18 '26

yeah, exactly it feels like we’re finally treating courses more like games or apps: start from the player/learner journey, then worry about the wiring.
I really like your experience architect” framing too if tools keep improving, the valuable part won’t be cranking out slides, it’ll be deciding what the learner should feel and do at each step.
feels like a fun overlap between UX, narrative design and pedagogy rather than just AI makes more SCORM faster.

1

u/OkIndividual2831 Apr 18 '26

where this gets interesting is in tooling. traditional formats like SCORM were built for static packaging, not adaptive experiences. so if you apply this vibe approach on top of them, you’re almost working against the medium. that’s why newer workflows are starting to look more like systems. people use tools like ChatGPT or Claude to define learning flows, and then something like Runable to shape the interaction layer instead of hardcoding every step.

1

u/Dramatic_Object_8508 Apr 19 '26

Yeah, this makes sense and it’s already happening in a lot of places. Instead of focusing on writing every step manually, people are designing the flow, intent, and feedback loops, and letting tools handle the execution. It’s less about “coding screens” and more about shaping experiences.

The interesting part is that this shifts the skill from syntax to thinking clearly about user journeys and edge cases. If the structure is good, the output usually follows. But if the thinking is vague, no amount of AI or tooling fixes it.

For learning design, this could actually be a big upgrade because you can iterate faster on how people learn, not just what they see. It also makes personalization easier since the system can adapt based on the flow you define.

So yeah, you’re not alone in thinking this way, it’s kind of where things are heading. The real value is moving from building things to designing how things behave.

1

u/[deleted] Apr 22 '26

yeah this is a much more interesting direction, focusing on intent, flow, and feedback instead of just generating content feels way closer to actual learning design, ai should be shaping the experience, not just speeding up production, feels like this is where things are heading tbh

1

u/cookedfraud Apr 25 '26

This is genuinely interesting — designing the flow and feedback loops first, letting the AI generate the actual content and branching logic.

Most people are doing the reverse: generating content first and hoping the flow works out.

Your way means you're designing for how people actually learn (choices, feedback, consequences) instead of optimizing for content volume.

If you're building tools around this, the bottleneck isn't generation, it's designing those decision trees and feedback systems. That's where the real work is.