
Tough crowd too - one of my first posts on their forums resulted in a hearty browbeating from a fellow forum member. Their so-called forums are weak - nothing like what Articulate has. Don't count on them responding to a question or comment via Twitter. The Captivate folks just don't seem to care and aren't up on the latest ways to communicate and interact with customers. Articulate takes this aspect of their business very seriously. :(Ģ) The Articulate community is second-to-none.
ADOBE CAPTIVATE 9 VS ARTICULATE STORYLINE 2 MAC
Create a simple rectangle and drag across the slide: S.L.O.W!!! This is on an i7 Mac with 24 gigs of RAM. Dialog boxes look like something from Unix circa 1995. Was this written in some sort of weird emulation/cross-platform language? It doesn't look, act or perform like a native Mac app. Sure, Captivate Draft seems a bit gimmicky at this point, but hey, it's something.Ħ) Adobe is more aggressive about HTML5 support.ġ) Performance and look/feel of Captivate on Mac is **very** disappointing. Storyline is double that.Ĥ) The Articulate character packs just look weird (to me).ĥ) Adobe is embracing the use of iOS as an extension platform. Captivate is currently on an annual version release schedule. $30/month is less painful than $1,400 up front.ģ) More rapid version releases. I'm a long-time Articulate user currently migrating to Captivate. In case you are interested, I attempted to round up the pros and cons of all three here. But than again, tastes and budgets differ.

The thing with Lectora is, it may appear prohibitively expensive to individual educators. I like its revamped responsive design approach, and animations are way better than in Captivate. To be honest, Lectora has quite an edge over both in some aspects. It's worth mentioning, Articulate Storyline lacks the video publishing option, whereas Captivate allows you to publish projects as MP4. Conversion quality is disputable, but that's a common problem. It's something that Articulate has been really good at for quite a long time. As far as I'm concerned, Captivate 8 didn't have any decent 'import from PowerPoint' feature, for one. For instance, Captivate 9 is a totally different story than ver. On the other hand, Storyline outruns Adobe in quizzing functionality, it offers more questions types and options.īesides, it's important to understand which version we are talking about. Looks like it's just a copy of the PowerPoint effects.

Captivate’s got some great animations and effects, Articulate is pretty basic from this perspective. Captivate requires a certain learning curve, even specified training might be an option here. Storyline is surprisingly easy to use, I mean my three-year-old grandson could probably use it. That's why many of us choose to keep both for various tasks. Let's face it: Articulate Storyline and Adobe Captivate are just conceptually different. I'd like to look at this issue from another angle, though. I agree being simple and 'just like Microsoft PowerPoint' is a flimsy argument. I am using Captivate 9 as a subscription, and seem to be using it much more than Storyline, although the more Advanced use of custom actions can be somewhat daunting at first.
ADOBE CAPTIVATE 9 VS ARTICULATE STORYLINE 2 PDF
PDF is a native file format in the Windows 10 browser and I would anticipate other browsers will also make this a native file format, doing away with the Acrobat reader entirely, just as the Flash Player will no longer be supported - ActiveX and plugins are just too much of a security risk, and the sooner we make the jump to xAPI and let go of SCORM the better, but Captivate's SCORM support is equal to Storyline for I believe they both use the Rustici SCORM Engine.

Yes, the learning curve for Captivate is longer, and there are some features within Storyline 2 that I really like, people fail to see the advantages of interactive PDF, particularly in its ability to use 3D objects in authoring tools such as Sim Labs Composer and output to PDF. Adobe has seen the proverbial "writing on the wall" in terms of HTML5 and the eventual demise of Flash, this is why Adobe has created so many complimentary HTML5-based products while still maintaining Air and Flash CC Pro. While I have both, I have to agree with Mark on all counts.
