I used captivate until version 5-6, I do review each release of Captivate but find it painful and I can develop faster in Storyline. I know of developers who use both tools, I prefer to know Storyline as well as I can and supplement it with Tumult Hype and other software if required.
My response is very similar to Phil's. I've used Captivate since before it was Captivate (RoboDemo anyone??). I still have version 7 installed and have reviewed version 8. I use Captivate when I have to make edits to an older Captivate course.
Also like Phil I've always found Captivate a bit painful to use, even after Macromedia bought it. I was never a big fan of the authoring interface and have grown even less fond of it since the Adobe acquisition.
It's much faster and easier for me to build the same interactions in Storyline, and I feel that the end product is smoother and has more polish than anything I was able to build in the same amount of time with Captivate.
I too prefer to develop in Storyline for all of the reasons Brian and Phil stated. I have developed in Captivate 9 and find the responsiveness, although quirky and difficult to develop, can be awesome when it works.
That's interesting, I'm part of a captivate group on lInkedIn so might as the same question there and compare the results.
Phil I checked out Tumult, looks good, but its Mac, do you run Storyline on a simulator e.g. parallels?
I have found with the theme and images available online for storyline you can make a very smooth and modern look. But with captivate it looks a bit clinical and a decade old. Maybe I need to either try to recreate something from storyline in captivate are look for inspiration online.
Failing that I could just bite the built and move to storyline.
Besides authoring, being a LMS administrator I've found Storyline's output to be much more reliable as well.
Literally 99% of the time we had a problem with an online course in our LMS it was Captivate-built content. Captivate content does not play well when you combine SCORM with some of the browsers that are out there (just try googling Captivate, SCORM and Firefox for example...).
Articulate's SCORM content works extremely well across multiple browsers and operating systems. In the rare occasion where we would have a problem with Articulate content in our LMS it always turned out to be an issue where a new developer had published something with the wrong publish settings. Easy to fix...
Hi, Marcus -- Thanks so much for reaching out with your question! I see that you are getting some excellent responses from other members of the community, but I thought I might stop in to share a few other threads on a similar topic that may be of interest:
What struggles do you run into with software simulations? This discussion is a bit older, but I'd love to help figure out what you're running into and how we can help! First, can you tell me what version of Storyline you're using?
I am using Storyline 2 (and I have tried 3). I am used to being able to use an Object Style manager to quickly control all elements or even import from other projects. Also, setting universal project recording preferences for the various elements and timing (captions, highlights, mouse, audio, start, finish, etc.). The ability to right click and copy background and paste background onto any slide. There are too many features to mention really.
12 Replies
I expect there will be bias :-)
I used captivate until version 5-6, I do review each release of Captivate but find it painful and I can develop faster in Storyline. I know of developers who use both tools, I prefer to know Storyline as well as I can and supplement it with Tumult Hype and other software if required.
My response is very similar to Phil's. I've used Captivate since before it was Captivate (RoboDemo anyone??). I still have version 7 installed and have reviewed version 8. I use Captivate when I have to make edits to an older Captivate course.
Also like Phil I've always found Captivate a bit painful to use, even after Macromedia bought it. I was never a big fan of the authoring interface and have grown even less fond of it since the Adobe acquisition.
It's much faster and easier for me to build the same interactions in Storyline, and I feel that the end product is smoother and has more polish than anything I was able to build in the same amount of time with Captivate.
Good luck!
I too prefer to develop in Storyline for all of the reasons Brian and Phil stated. I have developed in Captivate 9 and find the responsiveness, although quirky and difficult to develop, can be awesome when it works.
Cheers, Julie
Storyline 2 is much better as per it is just my view. Except kerning issue in it.
Oh I forgot to add. The Captivate forums are brutal. Zip on your thick skin if you use their discussion board. It's nothing like this forum :)
That's interesting, I'm part of a captivate group on lInkedIn so might as the same question there and compare the results.
Phil I checked out Tumult, looks good, but its Mac, do you run Storyline on a simulator e.g. parallels?
I have found with the theme and images available online for storyline you can make a very smooth and modern look. But with captivate it looks a bit clinical and a decade old. Maybe I need to either try to recreate something from storyline in captivate are look for inspiration online.
Failing that I could just bite the built and move to storyline.
Besides authoring, being a LMS administrator I've found Storyline's output to be much more reliable as well.
Literally 99% of the time we had a problem with an online course in our LMS it was Captivate-built content. Captivate content does not play well when you combine SCORM with some of the browsers that are out there (just try googling Captivate, SCORM and Firefox for example...).
Articulate's SCORM content works extremely well across multiple browsers and operating systems. In the rare occasion where we would have a problem with Articulate content in our LMS it always turned out to be an issue where a new developer had published something with the wrong publish settings. Easy to fix...
Hi, Marcus -- Thanks so much for reaching out with your question! I see that you are getting some excellent responses from other members of the community, but I thought I might stop in to share a few other threads on a similar topic that may be of interest:
Storyline 2 vs. Captivate 9
Captivate vs. Articulate
Articulate (Storyline) Vs Adobe (Captivate)
Hope that helps! :)
Thanks Christie I'll take a look.
I find Storyline very painful to use for Software Simulations and may end up just giving up on it and embedding Captivate recordings into Storyline.
Hi Stephanie,
What struggles do you run into with software simulations? This discussion is a bit older, but I'd love to help figure out what you're running into and how we can help! First, can you tell me what version of Storyline you're using?
I am using Storyline 2 (and I have tried 3). I am used to being able to use an Object Style manager to quickly control all elements or even import from other projects. Also, setting universal project recording preferences for the various elements and timing (captions, highlights, mouse, audio, start, finish, etc.). The ability to right click and copy background and paste background onto any slide. There are too many features to mention really.
This discussion is closed. You can start a new discussion or contact Articulate Support.