Progressive Enhancement
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
First build core functionality for the lowest-end devices/browsers (baseline), then add richer interactions for devices that support advanced features (enhancement). This is the opposite of "graceful degradation" (build the perfect version first, then patch up the broken parts).
SCAFFOLDING EFFECT
Reduce cognitive load
Inclusive design. When creating products or policies, first ensure that the most vulnerable groups (elderly, low-bandwidth users) can use it, then add enhancements for high-end users. This ensures maximum coverage and resilience of the system.
Anchor fast decisions
Progressive Enhancement: First ensure that basic content/functionality is available in any environment (semantic HTML), then layer styles, scripts, and advanced interactions on top according to browser capabilities; this is the opposite direction of "graceful degradation", emphasizing robustness and accessibility.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Progressive_enhancementverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS