Are progressive enhancement and graceful degradation basically the same thing?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Not quite. They tackle similar problems, but from different angles.
“Graceful degradation” implies you have spiffy functionality, and can deal with it being less spiffy (but still need it to work somehow) in browsers that don’t support it. “alt” attributes on images, and the
<noscript>tag, are examples of this.“Progressive enhancement” implies you’re starting out with just basic content, and want to add spiff for browsers that support it without breaking the site for those that don’t. As an example of this, imagine you have a list of links that serves as your nav menu. It works fine, but if you add some javascript it can give you flyout menus, tooltips, and all that.
Basically, progressive enhancement says “start out with good content, and make it better when you can”, and graceful degradation says “i assume you can do this cool stuff…but if you can’t…well…here’s some other crap you can do.”
Guess which one’s better.