CTO of Articulate explains why Storyline is better than Adobe!

[doma2001]

Nice read about responsive eLearning authoring:

http://articulate-downloads.s3.amazonaws.com/Delivering%20E-Learning%20in%20a%20Mobile%20World.pdf

[Lilybiri]

Bit outdated, since it ignores the Fluid Boxes workflow in Captivate 2017. Sorry for the disagreement.

[RodWard]

Actually, if you read carefully you will detect that what Articulate are admitting here is that Storyline does NOT do true responsive design output in the same way that Captivate can.  Articulate has decided NOT to compete head to head with Captivate in this area and has claimed that the real reason is they have found a better way.

But what Articulate are mistakenly calling 'responsive' output is really just scaling the output to the available width of the viewport.  Captivate has had this ability for several versions.

If you go to the Articulate user forum where this 'creative naming' was discussed you will find that some Storyline users are not impressed with what they interpret to be a somewhat deceptive marketing approach by Articulate.

Responsive design in Storyline 360 - Articulate Storyline Discussions - E-Learning Heroes

[doma2001]

It is outdated, yes.

I agree, sorry, I should have made it clear, I was in no way agreeing with the article.

I had some recent contact with a marketing company trying to sell me Storyline which is why I saw the article. My team already use it, along with other tools such as Captivate. They sent me the link after I queried the claim Storyline was able to create responsive output.

I thought it would make amusing reading for those of us that know what both Storyline and Captivate can do respectively.

[Lilybiri]

It was the main subject when I met StoryLine users at Learning Technology (London) one month ago. StoryLine has not real responsive projects at all. Their marketing claims so, but I call that lying but of course I don't have a marketing mind.

In this comparison I also explain my viewpoint on Fluid Boxes workflow, as well. Only Breakpoint views workflow can result in a full responsive project as I understand that word:

Fluid Boxes Or Breakpoint Views? - Captivate blog

BTW I changed the status of this thread from Question to Discussioin. Hope you don't mind?

[David Burnham HBA]

Articulate Storyline and other Articulate tools (Presenter, Engage, Quizmaker) outputs the content to work in their "responsive player", i.e. content scales to fit the device and the player (skin) changes the sidebar menu into a hamburger menu when presented on a tablet and phone.

 "Rise" part of Articulate 360 is a "Responsive"  development tool. It uses prebuilt lessons and blocks to build the course in html5 format. I just worked with a large organization and they were truly impressed with this tool.

[Lilybiri]

StoryLine wrapper  = rescalable projects, not responsive.

Rise = fluid projects, not fully responsive projects. Fluid Boxes in Captivate and Rise can rearrange containers to adapt to other browser resolutions, but you'll have to sacrifice control. A fully responsive project can have a totally different layout for small screens, that will load faster and gives all freedom to the creative developer.

Maybe some are impressed with Rise, but I heard lot of complaints in London from SL users, going from 'childish' to 'insulting for an experienced designer'. Not my words....

[David Burnham HBA]

So I think the way I am reading your response is that you are not thrilled with "Fluid boxes either in Captivate or Storyline Rise"  but prefer the Captivate (Version 8 - 10  "Breakpoints") to have more control.

[Lilybiri]

You should read my blog post to see my view on both workflows. It largely depends on the project, and on the developing time you want to spend. I just tried to explain the differences between rescalable, fluid (which is sort of hybrid between rescalable and responsive) and responsive. Terminology is important, and there is too much confusion by inaccurate use of words which seems to be the prvilege of all marketing people. I use the 3 workflows depending on the type of projecT.

[David Burnham HBA]

I agree that "responsive terminology" is part of the problem for both Adobe and Articulate. I also agree with you that the point is use the tools that meet the project requirement. Having taught Captivate since version 2 and Storyline since its inception to hundreds of students, I encourage my students/clients to use the tools that meets the project requirements. As I have also found, not all students/clients want to spend the extended time learning Captivate/Storyline to the level of a seasoned developer, but do like rapid development tools like "Rise" and on the Adobe side "Muse" to create"responsive" content although it not an "eLearning tool."