Archiv für das Tag "progressiveenhancement"

Jeremy Keith - Choice

We’ve made the mistake in the past of framing problems as “either/or”, when in fact, the correct solution was “both!”:

you can either have a desktop site or a mobile site,
you can either have rich interactivity or accessibility,
you can either have a single page app or progressive enhancement.

We don’t have to choose. It might take more work, but we can have our web cake and eat it.
adactio.com

Don’t tell me what my browser can’t do! – Christian Heilmann

This article by Christian Heilmann (of Mozilla and Microsoft fame) about the misconception that expecting certain features and capabilities in browsers and simply stating "please upgrade/turn on/go away" if these "requirements" are not met by the user's set up is web development is very much worth your time if you create things for the web.
And no, your shiny new client-side JavaScript framework is not the problem, but it isn't the answer, either.

Here’s a reality check — this is what our users should have to do to consume the things we build:

That’s right. Nothing. This is the web. Everybody is

...

Enhance progressively

progressive enhancement is not about offering all functionality; progressive enhancement is about making sure that your core functionality is available to everyone. Everything after that is, well, an enhancement (the clue is in the name).
Jeremy Keith

It is more often than not that I find myself in discussions about this exact point: I want our websites, their core tasks, to function, and if this is cared for, then we can talk about the fun stuff.
To many people this, in our new and modern browser times, seems to be a waste of time, why care for systems or users ...

The design, the code, 1909 texts, the illustrations, and some photos are made by me.

Motorisiert durch WordPress