Forget what you know about Graceful Degradation. Forget what you know about Developer Convenience. Forget what you know about Progressive Enhancement.
Instead of arguing over these terms, we should focus on how to change our culture. Create “fallforwards” not “fallbacks.”
In some ways this post is a semantic argument. Yet, it is an important one.
Lera Boroditsky, an assistant professor at Stanford, wrote an article on the effects of language on cognitive reasoning.
For those of us who studied philosophy and linguistics in college, this comes as no surprise. Yet, the depth of this influence bias is amazing.
This seems obvious in some cases. A language that often genders its vocabulary will have children that recognize their gender earlier (page 65 in the reference). In other cases it can be astounding. A 5-year-old girl living in an Australian Aboriginal community could discern cardinal directions. Intelligent adults in Western cultures struggle to gain a sense of direction.
The languages of these cultures actively shapes comprehension.
The girl from the example speaks a language with no relative spatial terms. Instead of an object being to the left of someone, it’s to the southwest.
The linguistic need turns into an intellectual need: keeping track of directions. The brain forges the neural pathways necessary to accomplish this need.
As it turns out, a semantic argument can be very important for creating culture shift.
In our world of web development, we talk a lot about fallbacks.
We use this word to mean “when this feature we’re using is not available to a user, how should our application behave?”
Why does it matter if we use this word?
Most definitions of “fallback” refer to “retreat” or “emergency” or other negative words. If our language is negative, we may end with a negative opinion of those we support.
Or at the very least, we may view them with less sympathy.
We shouldn’t retreat from these users. We should support them and then push forward into a new and awesome future.
Is this different than “Progressive Enhancement?” No, not really. This is more about ditching the negative connotations.
Let’s get started. As an example, let’s take a simple design form: an article list.
Our first step is simple, clean markup. This, out of the box, works on all browsers and devices. Each article has a headline, description and link.
Not exactly revolutionary.
Next, we add simple styling, clean the margins and make it look good on mobile.
These styles should be basic. Strive to add visual hierarchy and weight with spacing, colors and small images and clean the reading experience.
When we’ve got more screen real estate than mobile, we expand into layout. In our case, a two-by-two card view would be nice on tablet. As we approach bigger sizes, though, the width of these boxes is too wide for our content.
In this example, we use media queries to affect the flex-basis to adjust the size of these boxes.
If this sounds like “mobile-first design,” you’re right. Mobile is a very restrictive place for design. It’s also very restrictive for powerful hardware available cheap. This means we need to put a premium on the content, not the “design.”
Once we get our simple layout done, we can expand on the layout. In our example, we have a perfectly nice layout for articles. We have served our audience. Now, let’s have fun.
CSS Grid Layout is something I’ve written about recently. I’ve even begun using it to lay out pages on this site.
Let’s make an impactful layout for our articles using some fun new code.
In the code above, I’m using CSS Feature Queries to identify if a browser supports Grid before using it. By utilizing grid-auto-rows and not just display: grid, I can have Edge ignore it for now, but begin seeing it when it updates in 2017.
With an idea of fallbacks, a developer might try to have Grid be the main layout engine. They might then fallback to flexbox using an @supports not (display: grid) query.
The problem is Internet Explorer doesn’t understand Feature Queries. This means your handcrafted fallback will fail, as well.
This is not a new concept. Call it Progressive Enhancement. Call it Moral Development. Call it Defensive Coding. Just don’t call it a Fallback. Support your users and fall forward into new design and code.