HTML5 Apps: What, Why, and How. If you want to build web apps, you might want to think about using HTML5. HTML5 is the new hotness when it comes to app development, and it has the potential to change the way software is made and sold.
It also activates the millions of people out there who know how to make web pages, and never thought their skill set could be used for something else. But before jumping into development, there are some things you should know about HTML5. In this tutorial, I'll teach you the basics! What is HTML5? HTML5 is a W3.
C spec in the making. It started at WHATWG, and is the future gold standard for HTML. If you have been around for awhile, you many know that XHTML 2 was the next major version, but that fell apart. The reasons are varied, but one main point of contention was that few websites use perfect syntax, and XHTML 2 was going to enforce perfect syntax. It has also always been extremely hard to say exactly what perfect syntax is. When the browser vendors realized how hard it was going to be to make the switch to XHTML 2, things just broke down.
At that point a bunch of people broke away from the W3. C and started the WHATWG. These guys wanted to rethink not just HTML, but the whole standards making process. They started work on a new HTML5 standard. They operated from the principal that there is no perfect, and it. Instead they focused on looking at what was happening in the real world of HTML. They also took the time to codify some conventions that sprung up in the community.
That is where a lot of the new elements in the HTML5 spec (like the progress bar, video, and audio tags) came from. People have been making due, and they just wanted to make specific pieces of markup to help people do what they have already been doing. Besides just markup, the WHATWG started creating some new Java. Script APIs. This is where HTML5 started to look . They also started new working groups around widgets and device access (for using devices like cameras and accelerometers).
An interesting side note to the whole standards process is this: for awhile the differences in rendering engines were so great that one approach to be cross- browser compliant was to sniff which browser the user was on and deliver a different experience based on that. The WHATWG and others always thought that browser sniffing wasn. What is commonly recommend now is progressive enhancement. In a nutshell, progressive enhancement is this. Instead of just deciding that one browser would get experience Y and another would get experience Z, why not detect advanced feature support and build up to a great experience? If, at any point, the browser doesn.
The Last Numbered Spec This leads to another point about the HTML5 spec: it will probably be the last numbered spec. In the future, instead of revving HTML versions, like HTML6, the W3. C will just maintain the latest version of HTML, and there will be a gold standards spec. Web developers can use progressive enhancement to handle the fragmentation, while waiting for browser vendors to catch- up to the spec.
So What are HTML5 Apps? With HTML5 defined, what is an HTML5 app?
Essentially, a HTML5 app uses all the shiny, new pieces of the HTML5 draft to create an app- like experience. This means storing data offline, being functional, and acting like a real app instead of just being content for perusal. You probably use web apps now, like Gmail. Gmail actually has an HTML5 version; if you visit Gmail on an i.
Phone or i. Pad, you can check it out. Why Should I Use HTML5? Why would I want to use HTML5 instead of Objective- C, Flash, Silverlight, or some other kind of device- specific environment? If I was making the latest, greatest 3. D shoot- em- up, I would not use HTML5. If you need to use the camera on devices, or local files system, HTML5 would not be the best choice. There are workarounds, using a native wrapper, which I will discuss shortly, and there are also some standards coming that will help with that.
While there are specific cases for not using HTML5, many apps that get produced today for i. OS and Android could work just as easily in HTML5. Besides just technically being able to do it, there are other good reasons to use HTML5. You Already Know How to Use It Right now, if you are a web developer, you have all the tools you need to get into this. HTML5 app development is only little more then changing how you think about webpages. In some instances you can just add a few lines to your HTML, and add some stuff on your server and you will have a full, working, offline HTML5 app. The more we work with standards, the more useful they become.
Besides, web developers already understand cross- browser problems. While there will be more cross- browser issues than ever, web developers have a distinct advantage over other kinds of developers, because they already have this in their pocket. The other part of cross- browser development is standards. The more we work with standards, the more useful they become.