With so many different types of devices out there a strategy that allows an optimal presentation for each device makes a lot of sense. The concept of Progressive Enhancement has been around for a while but has new relevance in the mobile age.

2. People are a little scared of using Flash and looking towards HTML5.

3. Almost all the ambitious/impressive HTML5 samples are built for only one browser.

4. Do we have to choose one or the other? Introduction

6. Even on mobile devices that run Flash consideration must be made to usability.

8. Users expect a more rich and compelling experience

10. Ignore lesser devices and focus only on the best possible experience

11. Make multiple versions of your site, at least one “standard” and one optimized for mobile

12. Or...

14. Focuses on handling different browsers with varying capabilities.

15. Was a departure from Graceful Degradation, which was the leading philosophy on the issue.

16. Has caught on in theory but in practice older or less capable browsers are an afterthought, with one notable exception.

18. Add styling as supported

19. Add features as supported

21. Fix broken styling

22. Fix broken features

23. Built expecting certain technology.

25. Swfobject can be a progressive enhancement but is usually not

27. CSS that styles the HTML without requiring special HTML or Javascript.

28. Javascript that improves the experience and visual presentation if available.

30. Prioritize what is important (already doing this)

31. Accept that the site may not look exactly the same in all browsers (important!)

32. Designers are already thinking about content in a way that can be translated to basic browsers

33. Developers have to understand the experience and make smart recommendations

35. Blends together video and interactivity

36. Multiple animation techniques (frame-based, tweenlite, tweenmax, gtween, etc...)

37. Powerful 3D framework in Papervision

38. Existing HTML content can act as content XML

40. May not achieve as specialized an experience as having a custom site for each “category” of devices/browsers.

41. You may end up writing functionality that you hope to never use.

43. Allows the site to be experienced with all browsers/devices without building multiple versions.

44. Too many browsers/devices to target.

45. In many ways the experience will be more consistent across browsers/devices since it's essentially the same site.

47. Rather than going “lowest common denominator” or “all or nothing”, Progressive Enhancements allows your work to grow with the browser/device capabilities.

48. Q&A

50. Credits: http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2/

51. http://blog.deconcept.com/2006/02/27/using-alternate-content-flash/