Adobe captivate vs articulate
![adobe captivate vs articulate adobe captivate vs articulate](https://miro.medium.com/max/722/1*Vos9C_oHVwrjDsy2ldl-gg.jpeg)
The experiences between a desktop computer with a mouse and a touch-enabled devices are simply too different. One Size does Not Fit AllĪnd then there’s the fact that I don’t believe we should literally convert the same exact desktop eLearning to HTML for mobile devices, including the iPad.
#Adobe captivate vs articulate android
In fact, according to this “ Bring Your Own Device” (BYOD) research, entitled Dispelling Six Myths of Consumerization of IT, which took place in January, 2012, one of the key findings is that personal devices coming into the workplace are broad and diverse and in fact, the most popular consumer device that employees are bringing into the enterprise is not an Apple product, it turns out the single most popular device is the Android phone. What about other screens, like the iPhone, Android smartphones and tablets, and other devices like the Kindle Fire for example? In other words, I don’t believe that you can call having an iPad-only solution a real mLearning strategy. First off I think this question is fairly shortsighted because I believe real multi-screen design and deployment of “ learning” should go beyond just publishing for iPad consumption. This is an interesting question to answer for so many reasons. One of the questions I get asked frequently is whether I’d recommend Storyline or Captivate 6 to a company who needs to publish their desktop eLearning specifically for learners to consume it on the iPad.