4 comments

  1. Hi Craig,

    Some great points. The problem as we head to HTML5 and want to store our content in a truly cloud structure is that generating XML streams which is what SCORM calls for just doesn’t work. As a vendor, if you truly want to deliver content around the world using a content delivery network such as Amazon S3/ cloudfront, you cannot have it as a SCORM course. The way SCORM works you need to have a server actively parsing XML back and forth. Again, doesn’t work in a cloud environment. HTML5 also eliminates the hassles of authoring since video tags, interaction can be easily edited. Tracking or replicating what SCORM does is trivial. We are reaching a perfect storm of HTML5 and Cloud. SCORM will not survive.

    Like

  2. Craig,

    I enjoyed your article and shared it. We definitely need more HTML5 authoring tools. I find the PowerPoint-to-Flash authoring tools to be quite cumbersome and difficult to maintain. I’m looking forward to Apple’s announcement later today and hope we’ll soon have some easier authoring tools that will support mobile solutions.

    Like

  3. Scott,

    You probably want to check out Craig’s top ten list – there are a few tools there that probably meet your needs today.

    Like

  4. Thanks Craig. Good post. You ask why is Flash still hot. On the desktop browser, it is still the only viable solution for cross browser compatibility. Our mLearning Studio, HTML5 solution is targeted at mobile devices, but we still publish to Flash on desktop because HTML5-compatible browsers still only make up a fraction of the market share. Moreover, Flash is much more secure on desktop browsers. HTML5 is wide open (a good and bad thing). Thanks for staying on top of the RCAT market. Good stuff.

    Like

Comments are closed.