Captivate 3

*Currently playing in iTunes: Howl (Extended Version) by Black Rebel Motorcycle Club, Southland Tales soundtrack*

I upgraded to Captivate 3 *personally* today to gear up to take on some contract work, and I’m exploring a couple of things. Months ago, when Captivate 3 was released, I downloaded the demo and thought it was overall a little cleaner and snappier, but I didn’t notice a whole lot that really made me pluck down the $300 for the upgrade.

Snapz Pro XScreenSnapz001.jpg However, looking around now, even the interface improvements by themselves in the Branching section make it a viable way to work in the tool. More than just a pretty layout of how the branching should work in your content, now you can actually edit button and navigation actions from this interface, which is much better than having to constantly find where you’re supposed to be in the regular **Edit** area. This alone helps me in wanting to work with Captivate more now, because in version 2 (and in regular ol’ RoboDemo), this was damn near impossible to work with to do anything but a linear piece of content.

Another feature that’s been introduced in Captivate 3 is the ability to develop question pooling. Now Quizmaker offers this already in their assessments so that learners don’t necessarily have the same assessment as the person next to them. Captivate 3 takes this a step further by allowing you to have Question Slides interjected at different places in your content and the questions presented to the learner can pull from a common pool — this means that if you want a small interaction slide for the learner every three pages or so, you can put in such a slide and the experience will be a little different each time a learner encounters the same spot in the content, because the questions will be pooled (randomized) instead of being a fixed question. Don’t exactly know how instructionally useful this will be, but I like it from a development perspective.

I haven’t had to do a lot with porting out our content in Captivate to other languages, but now that the textual content in Captivate 3 is in XML, this will make internationalization of this content a possibility we can use when we need to. I’ve done this a bit with Articulate and it was easy as pie to translate, plug and play. Now that I can do the same thing with simulation content may/may not be very useful.

Since I have some contracting work coming up that calls for Captivate 3, I’ll be sure to share any learnings and frustrations along the way.

4 replies on “Captivate 3”