Please note that all these articles are just linked from other websites. I don't own or write any of them. Moreover, this blog is being under construction, so some functions might not work properly. Be patient!!! :)

Showing posts with label HTML5. Show all posts
Showing posts with label HTML5. Show all posts

Wednesday, October 20, 2010

Top 5 Developer Questions About HTML5 Answered


HTML Questions ImagePaul Gubbay is vice president of engineering for design and web at Adobe. He has spent the past 25 years working in the software industry with a specialized focus on creative and web professional tooling and solutions.
There’s been a lot of talk lately about HTML5 and confusion about what it is, what can be done with it today, the best way to learn it, etc.
With so much hype in the marketplace, I wanted to tackle the questions we hear most from creative professionals who want to take advantage of HTML5 but are unsure about how to get started.

1. What is HTML5?


In its simplest form, HTML5 is the evolution of HTML. Interestingly, it has become a “catch all” term for many technologies that can move the web forward, including CSS3, SVG and Canvas. What it offers most web professionals is a new set of functionality for creating richer interactivity for websites and applications across multiple screens. Due to the adoption of WebKit on mobile devices, HTML5 is gaining a lot of traction around smartphone and tablet development. In its early days, HTML5 will feel incremental in terms of how users can take advantage of it. But as the ecosystem evolves, frameworks and tooling will enable web professionals to create a new world of interesting experiences including applications that are accessible on a variety of devices.

2. Can I Use HTML5 Even if Users Have Outdated Browsers?


Although HTML5 is still in its infancy, there are several ways users can employ new language elements while ensuring that content degrades gracefully on unsupported browsers. There are plenty of articles on the web that discuss these techniques. For example:
  • Developers can work conceptually with new structural elements such as Header or Footer by creating classes with the same name and attaching them to divs within a user’s page.
  • You can take it a step further by using the new HTML5 elements today with a combination of JavaScript and some CSS to ensure compatibility with older browsers.
  • Developers can leverage JavaScript libraries such as Modernizr that take advantage of emerging technologies (HTML5, CSS3) while providing control over older browsers that may not support this functionality.
  • Developers can use HTML5 forms with new Input elements and types to provide richer functionality on modern browsers that support them with no penalty on older browsers where they will degrade gracefully to text inputs.
Of course if you are just targeting mobile browsers, you can take advantage of many more HTML5/CSS3 features. The mobile browsers that are primarily based on WebKit provide a lot more support, although there are still some inconsistencies across different implementations.

3. What Should Designers and Developers Learn First?


Developers should start incrementally by expanding their skills with technologies they already understand. Leveraging new functionality in CSS3 is a great place to begin. I also recommend following blogs to stay on top of what’s going on and keeping an eye on the different JavaScript frameworks that are springing up. There is a lot of innovation happening around mobile frameworks and runtimes right now. Some good resources to watch include:
Developers should also make sure they keep in mind the platforms they are building for, because the gating factor right now is browser support.

4. Am I Behind the Times?


9 Elements HTML5 Canvas
Hype about a particular technology can often lead to designers and developers feeling like they’re behind the curve, but that just isn’t true with HTML5. While there are some really cool examples out there today, in reality it is a much smaller subset of web developers that can create them, and the content works on an even smaller subset of devices.
There are significant hurdles to face when developing for devices, in addition to the typical cross-browser desktop compatibility issues everybody experiences. How do you take advantage of hardware acceleration? How do you take advantage of device APIs (e.g. touch, geolocation, offline cache, etc.)? What do you do when device APIs are not consistently accessible through the browser implementations?
Look for JavaScript frameworks and tools that can abstract across these differences and provide a set of building blocks that work consistently across the devices you are targeting. While there are many exciting capabilities being made available, most users will need to be pragmatic in their approach.

5. Why the Wait?


The gating factors right now for the widespread adoption of HTML5 are the browser vendors and the HTML5/CSS3 specification. Similar to the browser wars in the early days of the web, there is a significant amount of innovation happening within the browsers themselves. WebKit is becoming the predominant browser for mobile devices, but there are multiple implementations. Firefox and Chrome continue to push the boundaries on the desktop, with IE9 now joining the race with deeper support for HTML5/CSS3. While fast innovation is good news for web pros, it also creates inconsistency. This is where the Spec comes into play. The Spec drives the standard that all browsers need to adhere to. However, the Spec will not be ratified for many years.
Most web pros will be well served by standardizing on frameworks and tooling that can help them take advantage of the new functionality while degrading gracefully on the browsers that are still behind. Sites such as HTML5 Readiness can give users insight into what is and isn’t supported across Browsers.

What Is Adobe’s Stance on HTML5?


This is a question we get a lot at Adobe. As the current landscape continues to evolve rapidly, we believe people will benefit from implementing a hybrid strategy where Flash and HTML5 technologies are both utilized depending on the business need. For instance, if you are building an enterprise RIA with a multi-function team that needs a strong development framework, ubiquity across devices, and one vendor behind the technology, then Flash makes a lot of sense. If you are building a dynamic website that targets desktop, tablet and mobile, then HTML5/CSS3 is likely the right technology. In short, there will be places where HTML5 makes the most sense and provides basic interactivity, but there will always be a place for richer interaction and guaranteed consistency, and that’s where Adobe feels that Flash technology excels.

Conclusion


There’s no question that designers and developers should familiarize themselves with HTML5, learn what capabilities are currently supported, and, most importantly, where those capabilities are available based on the audiences they’re trying to target. Users shouldn’t make the mistake of falling in love with a particular site element and charging ahead only to find out that it doesn’t work at all in a browser that matters to their customer.
These are exciting times for designers and developers. We have some great challenges and opportunities in front of us that will have a huge impact on the future of the web. I can’t wait.

[via mashable]

Thursday, October 7, 2010

W3C Says HTML5 Isn’t Ready for the Web

While companies from Google to Apple to Microsoft voice their ardent support for HTML5 and developers rush to show off the fun tricks it can do, those who actually oversee HTML5 are telling the world to cool their britches.

An today, “There is already a lot of excitement for HTML5, but it’s a little too early to deploy it because we’re running into interoperability issues.” Particularly when it comes to video content, different devices and different browsers aren’t handling HTML5 consistently.

“I don’t think it’s ready for production yet,” the official continued.

“The real problem is can we make it work across browsers, and at the moment, that is not the case.”

HTML5, which was hatched by the non-W3C Web Hypertext Application Technology Working Group in 2004, should be fully approved within two or three years; until then, officials say Flash and Silverlight are still going to remain approved and viable web technologies.

Regardless of these issues, however, HTML5 already has an incredible amount of momentum behind it. Not only has the spec received the aforementioned endorsements from big tech companies; its praises are being sung by developers who have used it to create beautiful and innovative web projects, as well.

We’re fairly uncertain that any developers will stop deploying HTML5 websites simply because W3C officials say the specification and APIs are still undergoing changes, and we’re equally certain that the same developers who are using HTML5 now will not be likely to want to develop with Flash/Silverlight or for older browsers such as IE6.

What do you make of this proclamation from the W3C? Let us know in the comments.


[via mashable]

Saturday, September 25, 2010

5 Ways HTML5 Is Changing Mobile Advertising


Xavier Facon is CTO at Crisp Wireless, a rich media advertising technology company based in New York City. He blogs regularly about ad technology and mobile best practices.
Close to five years have passed since the early mobile ad networks emerged with basic banners on mobile screens. Despite numerous attempts at innovation, there are still very few mobile ad unit technologies being used by major networks or agencies. Many have just relied on the same basic banner ads that were used five years ago.
When Apple’s iAds [mashable link] came on the scene several months ago, it was considered a game-changer. While Apple believed it was setting a new standard for the quality of ads on the mobile device with its use of animation, sound and video, the company has since drawn criticism for production delays of initial iAd campaigns. Apple has managed to introduce a few campaigns from top brands including Nissan and Unilever in the past few months, but its early challenges underscore the struggles with innovation that have plagued the industry over the years. The question is, why?

The Introduction of HTML5


A large part of the issue is that many rich media ad technologies are proprietary and closed platforms. None of the mobile ad integration kits for apps are interoperable with each other. The technical barrier for running a mobile rich media ad campaign is very high.
With iAds demonstrating thatis a viable option for mobile ad development today, the industry will see more progress. HTML5 and compatible HTML5-based ad formats will have a major impact on the future of the mobile ad industry. Here are the five reasons why HTML5, an open standard, will change mobile advertising the way Flash changed it for the desktop.

1. Open Systems Support Speed And Scale


When ads are programmed using HTML, agencies can give the work to their own designers and developers. It saves time and money to put the creative control back in their hands instead of having to go back and forth with third-party vendors or ad networks.
Some rich media ad technologies may be based on open standards, but they are generally all closed systems where it often takes one or two months to get the ad unit developed and tested. After all, earlier HTML versions resolved the content creation bottleneck in the early days of the world wide web as well.

2. HTML Can Run Anywhere




HTML can be downloaded from an ad server and displayed on the web and in apps. The ability of apps to render HTML is a huge boost. Android and iOS support HTML5, and soon all major smartphone platforms will follow suit. The same can’t be said for Flash and other Flash lookalikes. One of the key issues in extending desktop campaigns to mobile is dealing with the fragmentation of that audience by diverging technologies.
Let’s take the recent extension of the Nissan Leaf campaign to mobile platforms. One vendor could have developed a Flash creative for the desktop web. Another vendor could have converted it to run in Android apps. Yet another vendor might support it to run on mobile web browsers. Apple could also use iAd to run the campaign on iPhone apps. Imagine the headache a media agency would have customizing that ad to run across all of these different platforms. HTML5 can be leveraged to solve that.

3. Tracker Compatibility


What’s the point of extending a campaign to mobile devices if you can’t get the delivery and brand interaction metrics right? This is another point easily solved by the unifying nature of HTML/JavaScript-based ad units. Agency ad servers can track banner impressions and clicks across many devices and technologies and produce a single report.
This is a more reliable approach than collecting various reports out of different mobile platforms, which are all calibrated according to different methodologies. For example, most in-app mobile ad servers count an impression every time an ad is requested from the server, while web servers track an impression only after the ad is displayed.

4. Lightweight Ad Display Engine


You may well be aware of the ongoing HTML5 vs. Flash debates happening across the industry and the web. One of the arguments in that debate is the potential quality and performance problems that plug-in technologies can suffer. With rich media advertising for mobile, much of the same concept stands.
When a mobile application developer integrates a rich media ad kit, it adds weight and can cause application performance issues. On the other hand, the code involved in leveraging the browser as the ad rendering engine is comparatively lighter and simpler, thus more suitable for resource-constrained mobile devices.

5. Design Flexibility




Last but not least, HTML5, CSS3 and JavaScript offer remarkable design flexibility and capability, which is unlikely to be trumped by a single technology compatible with so many mobile devices. It doesn’t require downloading of potentially insecure pre-compiled binaries and it doesn’t necessitate any heavy UI framework to be bundled with the app. For instance, the iPad apps for The Wall Street Journal and Popular Mechanics use HTML5 exclusively for their advertisers.
Based on a dozen or so major app publishers I’ve spoken to, the majority are either already serving HTML5-based display ads in their mobile tablet or smart phone apps, or they are considering it in the near future. There are even app developers who are collaborating on open source software development kits to create a rich media mobile advertising standard based on HTML5 with some extra native application hooks.
While display advertising on mobile devices may not reach full maturity for a while, the need to de-fragment the platforms on a technical level is key right now. Bridging the gap between the mobile web and apps has pushed the technology to evolve towards a cross-platform [mashable link] architecture. It is an exciting time for interactive developers and designers.

[via  mashable]