There is some confusion among users regarding the new HTML5 keygen element. The keygen element generates a public/private key pair and then creates a certificate request. Many users want to know the exact use of the element when SSL is available. This is my take on the subject. Correct me if I’m wrong.
Mobilize.js allows web developers create mobile sites out of existing websites with little effort. It supports the following features:
Automatically detect mobile browsers.
Easy to integrate – no server side changes needed.
Open source – no expensive software or licenses needed.
Supports iPhone, Android, Blackberry, Opera Mini and other browsers and devices.
If you have a WordPress site, plugins are available for the same. To see exactly how mobile.js works, check this section of the documentation.
Search-engines have reached a impasse with respect to understanding of HTML data. Although most sites, especially databases centric sites use structured data in the backend, once the data is rendered as HTML the data looses all its structure and makes it difficult for search engines to understand them correctly. Until now most search engines have relied on extracting keyword text from the web pages and ranking the pages accordingly, taking the context around the keyword into consideration. This obviously has its limitations and it can only take you so far.
One of the interesting and useful addition to the HTML5 specification is the Geolocation API. The Geolocation API allows users to share their location with web applications so that they can enjoy the benefits of various location-aware services.
Geolocation enables you as a developer or website owner to figure out where a particular user is located on the planet. This can be helpful in various web applications; for example in social networking, where you can find out where your various friends are currently located or in advertising where you can display targeted ads based on the users location.
If you’re designing a web application, you may think that developing it in English will be quite enough. Remember, though, that only 22% of internet users speak English as their native language, and 85% of ecommerce consumers won’t buy a product if they can’t read about it in their native language, which leaves only one question to be asked: are you prepared to miss on those millions of potential customers?
Software developers worldwide know that a web application will only work the way it’s supposed to for its target market. Even if two countries speak the same language, there are plenty of other things to consider when it comes to localising an app. Take, for example, the UK and the United States. The date format in the UK is day/month/year, while the US uses month/day/year, which could be cause for problems if an app is not localised for its specific market.