My team is currently working to put together a proposal to move from Captivate 6 (yes, 6) to Articulate Storyline 2. I know we need to substantiate the move from a financial perspective, which we will do. I was wondering if anyone might have anything compelling to share from a qualitative perspective. I'm looking for stellar articles, comparison pieces or, even better, examples from your accepted proposals would be phenomenal! If you were a previous Captivate user and have made the move, I'd love to hear what you appreciate about Storyline that Captivate wasn't doing for you. :-)
1 Reply
I'll answer with a rhetorical question. Would you be able to do this or this using Captivate 6?
If you're not using motion tweening excessively, Storyline 2 is the way to go.
Furthermore, Captivate 6 is a June 2012 release - three years is a long time for (what essentially is) a code generator to be sustainable on the web.
Hope this helps,
Alex
This discussion is closed. You can start a new discussion or contact Articulate Support.