Yesterday i was reading the “Progressive Enhancement demystified” on the .Net site. It was one of those articles that was bookmarked to read later. The article was about the difference between Graceful Degradation and Progressive Enhancement. Since i started looking at HTML5 about 2 years ago i heard these words often without really understanding them. Graceful Degradation VS Progressive Enhancement Gracful Degradation: -> think browser Takes care of the presentation in this proces the site or app get build for the most advanced and fancy browsers. In this paradigm older browser get little attention. Only the big errors get fixed and only for a few previous version. In other words it gets to the other buzz word “Fallback”. You make sure that for the functionality you use other minor browse can use a alternative or a message of the short coming of there browser. Can’t use canvas then use flash for example. Progressive Enhancement: -> think content It is all about the content. St...

It’s been a while now but finally I had some time to set-up some started projects. A while back I was doing a lot of research into all the new methodologies and technology’s. After reading and testing a lot with Local storage, Responsive Web Design, Mobile First, Progressive Enhancement and Graceful Degradation. Progressive Enhancement approach I realized that having those new skills is great but how to use them? This made me think about my work flow and how to approach a new project. It has to be Mobile First, but Graceful Degraded or Progressive Enhanced? And what with Responsive Design how to tackle this? A while back I saw a presentation from Nicolas Zakas and when seeing this screenshot on the right I realized that we have to try to create our UI as simple as possible and then layering up. This results in a long journey of reading, watching video and hack some stuff together to test and get results. Where to begin? That was my first question, I based my quest on the s...