The new version of Captivate can only create responsive projects. Personally I don’t believe that such a project is not appropriate for any content. I also know that responsive projects have more limitations than non-responsive projects, both technical and design-wise. To be able to give the new version a thorough test, I choose a topic which can be used on mobile device and developed a responsive project in version 11.8 with Fluid Boxes workflow. You can test this project here. I will try to recreate this project in version 12, try to report the progress which will be in baby-steps due to the drastic change in UI, tools and terminology.
For this project I used assets from the Quick Start project ‘Rhapsody’. It uses variable, shared and advanced actions. You’ll get some more information in the project:
Workflows rely heavily on multistate objects, which are especially useful in responsive projects with the Fluid Boxes workflow. The new version 12 has improved working with states, which is hopeful.
I would like to know if and when the new version of Captivate will include a non-responsive option. Currently, it is not possible to create high-quality eLearning content, and it’s too complicated to move or modify the layout. We created one eLearning in the new version, and after format changes, users have to scroll to read all the content on one page. I would prefer a clean, fixed-size format.
What is the reasoning behind only having responsive projects? Has anyone considered the feedback from end users? I’m starting to get frustrated because I am unable to deliver what is expected by the end customer. Could ADOBE please provide a timeline for when non-responsive projects will be available in the new version? I am willing to wait until this is addressed, but if it will never be implemented, I may have to consider exploring other applications.
You must be logged in to post a comment.
