Has anyone implemented Integrating Progressive Enhancement to Web Design ?

4 replies
  • WEB DESIGN
  • |
I heard Progressive Enhancement comes with many benefits, so staying away from incorporating the same in your web design is certainly not a god idea. Has anyone tried this out and got benefits from it?
#design #enhancement #implemented #integrating #progressive #web
  • Profile picture of the author Michael71
    51: Graceful degradation versus progressive enhancement - Dev.Opera

    This article should give you some insight.

    And here the definition:

    http://en.wikipedia.org/wiki/Progressive_enhancement

    +1 for progressive enhancement
    Signature

    HTML/CSS/jQuery/ZURB Foundation/Twitter Bootstrap/Wordpress/Frontend Performance Optimizing
    ---
    Need HTML/CSS help? Skype: microcosmic - Test Your Responsive Design - InternetCookies.eu

    {{ DiscussionBoard.errors[7741415].message }}
  • Profile picture of the author David V
    This is an interesting subject, because many of the ways it is used really should be called "Progressive Degradation Funnel".
    There's nothing wrong with it, the concept is simple.
    Hey "this is the best way, but oh, you don't have that, so let me serve you the "next best thing".
    "Oh, you don't have that either?, let me serve you this then".... and so on.

    Basically trying to cover every base, every circumstance to ensure everyone gets your message or product.

    This is cool, why not....

    But when you start at the top with the "ideal way" or the "way you want to serve it", then everything you do below that is a step down not up. Enhancement means "better" or "improved", but what we really have is a inverted pyramid or funnel.

    Certainly there are "things" that are lateral and not a step down, but if your site's intention is to serve javascript, ajax, etc for a better user experience and your user has these disabled (which I do at times), then giving them a non-javascript version is a step down, not an "enhancement".
    Don't get me wrong, I like the idea, I just don't care for the misleading label and naming of the practice.

    Of course you can avoid having to "cover every base" by understanding your visitors, doing extensive research and tracking.
    IE6 is a good example. It's pretty common for developers to say "kiss you know what" to catering to IE6 users. They are far and few between, IE6 is practically dead, so unless your research and tracking shows that a lot of your visitors use IE6 then don't spend an ounce of effort catering to it. It's a lot of work, and a deadbeat browser.
    {{ DiscussionBoard.errors[7741649].message }}
  • Profile picture of the author Michael71
    Graceful degradation can be a pain in the a**... I remember I had to code a job portal where the client wanted to have IE6 covered, too.

    At the end we decided to drop IE6, thank god.

    "Progressive Degradation Funnel"...

    Yeah David, that is how it work... at the end.

    You code for/with modern browsers and everything else is just as you said:

    PDF - "Progressive Degradation Funnel"

    Thank god there are frameworks that cover most of the graceful degradation.
    Signature

    HTML/CSS/jQuery/ZURB Foundation/Twitter Bootstrap/Wordpress/Frontend Performance Optimizing
    ---
    Need HTML/CSS help? Skype: microcosmic - Test Your Responsive Design - InternetCookies.eu

    {{ DiscussionBoard.errors[7742221].message }}
  • Profile picture of the author zubizubi
    [DELETED]
    {{ DiscussionBoard.errors[7743927].message }}
    • Profile picture of the author Istvan Horvath
      Originally Posted by zubizubi View Post

      Not at all. To be frank I have not heard about Integrating Progressive Enhancement till today.
      That's not a good enough for reason to post...
      Signature

      {{ DiscussionBoard.errors[7743948].message }}

Trending Topics