I tested a Chromebook and had hardly any issues other than slow loading (probably due to the wi-fi network). I tested multiple choice, true/false, multiple answer, free form, drop-down, and drag-and-drop and all worked. The main issues were design related (font appeared small and sound was too low without headphones). The Chromebook I tested did not load the flash file. In testing other HTML5 mobile devices (android tablets) there were numerous issues (poor text rendering; interactions don't always load); however the Chromebook worked well.
I was using Google Chrome. We were concerned with HTML5 performance since HTML5 is inconsistent across devices, so it's possible I had linked directly to the HTML5 load page rather than the story.html. According to this: https://support.google.com/chromebook/answer/108086?hl=en Chrome on Chromebook does support Flash.
According to the system requirements, Chrome OS is not a supported platform--Chromebooks do not use Windows or Mac OS X.
Additionally, I've seen where Google has said that Chromebooks support their default flash plugin, but do not support other plugins such as Java. They go on to say that Chrome OS devices can only support these additional plugins whenever additional virtualization and remote software is added.
For authoring Storyline content it looks like you won't be able to create it on a Chromebook if it doesn't meet our system requirements. As for viewing the published content in an LMS or web server, Storyline doesn't rely on Javascript unless you've included such as triggers - but many LMSs use Javascript. You should be able to access the published content through the installed Chrome browser though.
7 Replies
I tested a Chromebook and had hardly any issues other than slow loading (probably due to the wi-fi network). I tested multiple choice, true/false, multiple answer, free form, drop-down, and drag-and-drop and all worked. The main issues were design related (font appeared small and sound was too low without headphones). The Chromebook I tested did not load the flash file. In testing other HTML5 mobile devices (android tablets) there were numerous issues (poor text rendering; interactions don't always load); however the Chromebook worked well.
Did you use Google Chrome to test? Doesn't Google Chrome contain Flash on a ChromeBook?
I was using Google Chrome. We were concerned with HTML5 performance since HTML5 is inconsistent across devices, so it's possible I had linked directly to the HTML5 load page rather than the story.html. According to this: https://support.google.com/chromebook/answer/108086?hl=en Chrome on Chromebook does support Flash.
Hi, All! Curious if there's any more recent info on Chromebooks with Storyline output?
Hi Nick,
I haven't heard any more about Chromebooks in the forums - but as long as they meet with the system requirements here it should be safe to use.
This post was removed by the author
Hi Ashley,
According to the system requirements, Chrome OS is not a supported platform--Chromebooks do not use Windows or Mac OS X.
Additionally, I've seen where Google has said that Chromebooks support their default flash plugin, but do not support other plugins such as Java. They go on to say that Chrome OS devices can only support these additional plugins whenever additional virtualization and remote software is added.
https://support.google.com/chrome/a/answer/1290513?hl=en
Since Articulate products rely heavily on Javascript, I don't see how it can be natively supported on a Chromebook.
Can you verify whether or not the Chrome OS is supported, or that Storyline content will function without Java support?
Hi Michael,
For authoring Storyline content it looks like you won't be able to create it on a Chromebook if it doesn't meet our system requirements. As for viewing the published content in an LMS or web server, Storyline doesn't rely on Javascript unless you've included such as triggers - but many LMSs use Javascript. You should be able to access the published content through the installed Chrome browser though.
This discussion is closed. You can start a new discussion or contact Articulate Support.