PUBLIC MARKS from oseres with tags html5 & mobile

Whether you need to quickly get up to speed with HTML5 or are in search of easy-to-digest resources that you can use to educate your clients about this web technology that’s creating a huge paradigm shift in the web and mobile development ecosystem, this collection of infographics that visualize HTML5 facts and figures will help. If you’d like to go to the source of an infographic so that you can find a larger version and learn more about the infographic, click on the respective title or preview image.

Kaazing products power the Living Web – the dynamic, real-time, interactive, collaborative online world that has organically evolved into the norm. Building on the HTML5 WebSocket standard and extending WebSocket functionality to any browser or protocol, Kaazing products enable instantaneous, full-duplex delivery of content back and forth between any browser or mobile device and any backend service. The Kaazing product family is built on the Kaazing Platform, which provides a unified architecture for write once, use everywhere application development that can save vast amounts of both time and money in developing and deploying Rich Internet Applications. Whether exchanging content with mobile devices, browsers or other servers, the Kaazing Platform delivers the highest scalability, security and performance available in the market today.

The first open source multi-device framework. Develop only one application. Reach the web, mobile devices, tablets and smart TVs, as well as connected objects.

The desire to “consumerize” mobile apps for their own sake is stoking today’s outsized enthusiasm with device-specific enterprise mobile apps at a time when HTML5 is right there staring us all in the face.

reating a mobile-friendly html5rocks.com As an exercise I thought it would be interesting to take html5rocks (an existing HTML5 site) and augment it with a mobile-friendly version. I was mainly concerned with the minimum amount of work required to target smart phones. The goal of my exercise was not to create an entirely new mobile site and maintain two codebases. That would have taken forever and have been a huge waste of time. We had already defined the site's structure (markup). We had a look and feel (CSS). The core functionality (JS) was there. Point is, many sites are in this same boat.