You can put html5 and css3 to use *today*. Using some clever code and trusted techniques of progressive enhancement, you'll be creating cutting edge sites that handle older browsers appropriately.
1 of 38
Downloaded 66 times
More Related Content
Progressive Advancement in Web8
1. Progressive Advancement
in Web8
(btw- web8 == html5 + css3)
Paul Irish
Isobar
JSConf 10
Friday, April 23, 2010
3. Native is better
html5 form controls vs UI libraries
html5 drag n drop vs draggable()
css transitions vs animate()
border-radius, border-image, background-size
vs using large sprites
localStorage vs cookies
Friday, April 23, 2010
19. Native No Native
Implementation Implementation
. box { .no-borderradius .box {
// use border-radius // maybe less padding?
} }
if (Modernizr.borderradius == false){
// call up DD_roundies, etc.
}
Friday, April 23, 2010
20. Native No Native
Implementation Implementation
.boxshadow div { .no-boxshadow div {
box-shadow: 1px 1px 1px #666; border-bottom: 1px solid #666;
} border-right: 1px solid #777;
}
Friday, April 23, 2010
21. // geo-location bridge
function getLocation(callback){
if (getLocation.cache) return callback(getLocation.cache);
if (Modernizr.geolocation) {
navigator.geolocation.getCurrentPosition(function(position) {
callback(getLocation.cache = {
"lat": position.coords.latitude,
"lon": position.coords.longitude,
"obj": position
})
});
} else {
$.getScript('//www.google.com/jsapi',function(){
callback(getLocation.cache = {
"lat": google.loader.ClientLocation.latitude,
"lon": google.loader.ClientLocation.longitude,
"obj": google.loader.ClientLocation
})
});
}
}
// usage
getLocation(function(pos){
console.log("I'm located at ",pos.lat,' and ',pos.lon);
});
Friday, April 23, 2010
31. UP !
HU T wrong.
S y ou re
ishtml5readyyet.com
Friday, April 23, 2010
32. Your mother does
NOT 鍖nd a website
she likes the look of,
and then opens it
another browser.
~Andy Clarke (@malarkey)
Friday, April 23, 2010
33. A Performance Policy
2 truths
1. Both you and the client want the most
responsive experience possible.
2. Everything added to the page slows it
down.
Friday, April 23, 2010
34. A Performance Policy
During IA, IxD and visual design
communicate impact of design decisions
Tell the client all browsers will not have the same
experience
Its not worthwhile to have feature parity
Stop in the name of love
Drop in the name of performance
Friday, April 23, 2010
35. What would you prefer me to do?
Spend my time hacking around issues in
older technologies like Internet Explorer 6
or
would you like that time spent making the
site look the best that it can on better
desktop browsers, as well as on the
iPhone, iPod Touch, iPad, Blackberry and a
whole host of other mobile devices?
~Andy Clarke (@malarkey)
Friday, April 23, 2010
36. When performance is poor
There are three options:
1. Redevelop the code
2. Drop the feature
3. Redesign approach of the UI
Friday, April 23, 2010