I build scenario-based learning, and the part that always slowed me down wasn't the design-- it was everything after it. Branching logic, variable wrangling, and anything conversational meant either heavy Storyline plumbing or a developer.

With devlin.ai I built an adoption simulation where the learner talks to an AI coach character that actually responds to what they say, not to a preset menu of three options. That used to be a custom-dev conversation. Here it was part of the build.

The other thing I didn't expect to care about as much as I do: publishing and hosting are in the same loop. My portfolio piece went from build to live URL without a handoff, and revisions land in the same session instead of the next sprint. When you're shipping work to be seen, that compression is the whole game. Review collected by and hosted on G2.com.

Neither is a dealbreaker -- Two small edges, both in the deploy path rather than the building:

The uploader rejects the entire bundle if a stray file type it doesn't expect is in the zip -- a leftover .md in my case -- but the error tells you which file caused it. I didnt lost much time hunting for that.

Deployed URLs carry version fragments that look like you can reach an earlier build, but they return the current one. So keep your own snapshot before you deploy; don't assume you can roll back from the live URL. Review collected by and hosted on G2.com.