4. The Buzz

This statement has to be qualified. Although the browsers all support the standards, their support varies. Interpretations of the standard can differ. No browser supports every feature defined in every applicable standard. To keep the user experience acceptable on all browsers, developers have to restrict themselves to the features shared by their target browsers and use conditional code that executes differently to suit each browser. This annoyance is unfortunate but a fact. Developers have become adept at working around it.

SaaS has its own challenges. Applications were traditionally designed for a single installation supporting a single enterprise. SaaS can be architected that way, but that architecture is hard to scale and maintain. From the consumer’s viewpoint, on-premises architectures are under the governance of the consumer. They can be secured and customized easily. The consumer decides when and how to patch, not the provider. The challenges can and are being addressed.

Android code is released under the Apache license.

IBM’s Worklight is an example of a hybrid IDE that plugs into Eclipse. See an overview here: www.sitepoint.com/build-a-mobile-hybrid-app-using-ibm-worklight-part-1/ .

For a comparison of browser HTML5 support, see https://​html5test.​com/​results/​tablet.​html. Accessed August 2015.

TLS replaced SSL fifteen years ago. SSL is no longer considered secure. There have been several revisions of TLS, each closing security holes in the previous version. SSL is still the more common term, but it nearly always refers to TLS.