Graceful Degradation vs Progressive Enhancement
You'll learn the difference between two opposite approaches to building web experiences: starting fancy and removing features, or starting simple and adding enhancements.
Two Opposite Strategies
Both Graceful Degradation and Progressive Enhancement aim to make websites work for everyone, but they approach the problem from opposite directions.
Graceful Degradation: Top-Down
Graceful Degradation means building the full, feature-rich experience first (for modern browsers), then adding fallbacks so older browsers don't completely break.
Analogy: Imagine designing a luxury car with all the bells and whistles, then stripping features out to create a budget model. You start with heated seats, GPS, and autopilot, then remove them for older vehicles — but the car still drives.
The risk: If you forget to test in older environments, users might get a broken experience.
Progressive Enhancement: Bottom-Up
Progressive Enhancement (which you learned about in the previous lesson) starts with core functionality that works everywhere, then layers on enhancements for browsers that support them.
Analogy: You build a reliable bicycle first (works for everyone), then add an electric motor for those who have the infrastructure to charge it. Everyone can ride; some just get extra features.
Why Progressive Enhancement Wins
While both philosophies acknowledge that not all users have the same capabilities, Progressive Enhancement guarantees that everyone gets a working baseline. Graceful Degradation can accidentally leave people behind if you miss a fallback.
Modern web development strongly favors Progressive Enhancement because it puts accessibility and core functionality first.
Key Takeaway: Graceful Degradation builds rich experiences and strips them down; Progressive Enhancement builds core functionality first and layers enhancements on top — ensuring no one is left with a broken site.