article thumbnail

Video not play in iPad/iPhone on Captivate 2017

Adobe Captivate

Video dose not play in iPad/iPhone. I had faced these issues for Captivate 2017. The post Video not play in iPad/iPhone on Captivate 2017 appeared first on eLearning.

iPhone 40
article thumbnail

The Future of Enterprise Mobile Learning [INFOGRAPHIC]

LearnDash

billion enterprise smartphone users globally by 2017. Everywhere you look someone is toting around an iPhone, iPad, or iThing. Smartphones are the leading mobile technology, with an estimated 2.4 While these facts are interesting, I don’t think they are very surprising.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Under the hood with Captivate 2017: Creating a Custom Preview Mode for Responsive Projects

Adobe Captivate

If you’ve been on the eLearning forums after the launch of Captivate 2017, you’ve already seen that you can convert an existing ‘blank,’ or standard, Cp project to Responsive bu choosing ‘ Save as Responsive ‘ in the File menu. The default devices include: Desktop, iPhone 6, iPad, Galaxy S7, and Nexus 5x.

article thumbnail

Uploading videos and audio from other IOS devices

Adobe Captivate

Currently I am working on the trial version of Adobe Captivate (Having a lot of fun just its a serious learning curve) and currently having trouble transferring videos and audio recordings from my iPhone or iPad to the program. For context, I am working on a 2017 Macbook with 8gb of RAM.

Audio 40
article thumbnail

Retain Scalable HTML on Desktop version when creating responsive project

Adobe Captivate

Some information that could be helpful, happy to provide additional if needed: Using Captivate 2017 (but willing to upgrade to 2019 if it solves for this issue). Target devices for mobile are iPads & iPhones. Project size: 1280*720. Includes quiz & knowledge check questions. Thank you, Jody.

HTML 40
article thumbnail

Phasing out Flash

OpenSesame

The Adobe honeymoon period started to end in 2010 when Apple famously refused to allow Flash on iPhones and iPads— in part because it was originally designed for desktop browsing, not mobile, which led to performance problems and battery drain, and also due to its security flaws.

Flash 52
article thumbnail

Phasing out Flash: all your courses will be mobile ready by 2019

OpenSesame

The Adobe honeymoon period started to end in 2010 when Apple famously refused to allow Flash on iPhones and iPads— in part because it was originally designed for desktop browsing, not mobile, which led to performance problems and battery drain, and also due to its security flaws.

Flash 52