- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
What is the difference between "Graceful Degradation" and "Progressive Enhancement"?
They both describe patterns for how to implement experiences, but the difference lies in the perspective on achieving compatibility.
- 🔼 Progressive Enhancement (Old to New): Starting from an older experience and moving forward to adopt new experiences
- 🔽 Graceful Degradation (New to Old): Starting from a newer experience and moving backward to maintain compatibility with older experiences
If there were no constraints, adopting the latest environment would be ideal, but the reality is that we often need to support legacy users to some extent, which is why different approaches are necessary to achieve a consistent experience. Looking around, we can see these patterns applied in various fields on the web; for example, consider:
- 👉🏻 Is the early trend of skeuomorphism a form of design progressive enhancement?
- 👉🏻 Is loading high-resolution images on high-speed networks while loading low-resolution images on low-speed networks a form of graceful degradation?
The web is changing rapidly, but necessary compatibility based on user needs still needs to be addressed, and these two patterns can be relied upon to make decisions based on the situation.
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1