les slides sont disponibles ici : https://www.nicolas-hoffmann.net/PE-CES2017
Research and publish the best content.
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
Bonnes Pratiques Web & Cloud
58.9K views |
+0 today
 Your new post is loading...
Your new post is loading...
Scoop.it!
Au SXSW en 2003, Steve Champeon et Nick Finck ont présenté une conférence intitulée "Conception Web Inclusive pour le Futur". Ils ont alors dévoilé un modèle pour cette nouvelle méthode d'approche du développement web. Steve lui a aussi donné un nom : l'amélioration progressive.
Scoop.it!
Is there a JavaScript-Dependency Backlash? Craig discusses the benefits of Progressive Enhancement. Again. Is that JS Framework the best option for your app?
Scoop.it!
In State of the Mobile Web (March 2013), we take a look at 7 tips for mobile-proofing your website and key trends affecting the mobile web.
Scoop.it!
Like me, Mike was impressed by Bryan Rieger’s excellent presentation in which progressive enhancement plays a crucial role. However, it’s important to realise that Bryan’s presentation is the start of the dicsussion, and not the end. Lots of work remains to be done.
Mickael Ruau's insight:
The trick is that every browser uses exactly those layers it can handle and ignores the rest. The website is enhanced as much as the browser allows — for any value of “browser.”
Scoop.it!
by Steven Champeon and Nick Finck Introduction Web design must mature and accept the developments of the past several years, abandon the exclusionary attitudes formed in the rough and tumble dotcom era, realize the coming future of a wide variety...
Mickael Ruau's insight:
Progressive enhancement is a strategy that reaches back into the history of the semantic markup technologies that gave rise to HTML and inspired XML. By making use of new presentation technologies such as CSS, it allows the Web document designer, visual designer, and developer to play to their own strengths while enabling each to deliver the information and interactivity demanded by users, while embracing accessibility, future compatibility, and determining user experience based on the capabilities of new devices. Instead of placing responsibility on server to determine what to send back to the client, PE uses longstanding characteristics of markup, bugs in various browsers, and other tactics to place a renewed focus on information delivery. Rather than hoping for graceful degradation, PE builds documents for the least capable or differently capable devices first, then moves on to enhance those documents with separate logic for presentation, in ways that don't place an undue burden on baseline devices but which allow a richer experience for those users with modern graphical browser software.
Scoop.it!
Steven Champeon turned web development upside down, and created an instant best practice of standards-based design, when he introduced the notion of designing for content and experience instead of browsers.
Mickael Ruau's insight:
About a decade later, several smart folks began to question graceful degradation and found it lacking on many levels. Concerned with content availability, overall accessibility, and mobile browser capabilities, they sought a new way to approach web development—a way that focused on the content and did more than just pay lip service to older devices.
|
Scoop.it!
What is the difference between a web page and a web application? Though we tend to identify documents with reading and applications with interaction, most **web-based applications are of the blended variety**: Users can consume information and perform tasks in the same place. Regardless, the way we approach _building_ web applications usually dispenses with some of the simple virtues of the readable web.\n\nSingle-page applications tend to take the form of runtimes, JavaScript executables deployed like popup shops into vacant `` elements. They’re temporary, makeshift and [not cURL-able](https://indiewebcamp.com/curlable): Their content is not really _there_ without a script\_being executed. They’re also brittle and underperforming because, in service of architectural uniformity and convenience, they make all of their navigation, data handling and even the **basic display of content** the responsibility of one thing: client-side JavaScript.
Scoop.it!
As we discuss in our new book, Designing with Progressive Enhancement, and in previous articles and presentations, building with progressive enhancement is essential to ensuring a usable experience for all. But how do you determine which browsers should receive the enhanced experience and which should stick with the basic experience?
Introducing EnhanceJS, a JavaScript framework designed specifically to deliver a usable experience to the widest possible audience, by testing the browser to determine whether it is capable of correctly supporting a range of essential CSS and JavaScript properties, and delivering features only to those that pass the test.
We're releasing EnhanceJS as an open source (MIT license) project to allow everyone to start building sites with test-driven progressive enhancement. In this article, we’ll review how to use EnhanceJS in your own projects so you can take advantage of new CSS and JavaScript features while ensuring a usable experience to all.
Scoop.it!
Learn how to build pages that take advantage of browsers' capabilities rather than be limited by feature sets.
Scoop.it!
This is the last part of my reply. In parts one and two we talked about what web developers are doing wrong; now we’re going to talk about the errors of the mobile world.
Mickael Ruau's insight:
Just say no
I was one of the first web developers to speak out against this practice, and I will continue to do so now that I’ve moved to mobile. I aim to prove that it’s simply not necessary, besides being wrong on a fundamental level. Why is browser detection so wrong? It’s incomplete. There’s just no way we’re going to be able to incorporate all devices in this detect. And even if we miraculously did, the next week a new device would hit the market and we’d be incomplete again.It’s unreliable. You’re always going to miss something or make a mistake in your detection.It’s an arms race. If device detection really catches on, browsers will start to spoof their user agent strings to end up on the right side of the detects. Web developers will retaliate by even more finely-grained (and even less complete and reliable) detects, which will cause the browser vendors to improve their spoofing etc. This has happened on desktop (just ask Opera about it), and we should keep the mobile space free of this nonsense.It’s cheating. If you make any mistake at all (and that’s inevitable, really), you’re either denying advanced functionality to a browser tht can handle it, or sending advanced functionality to browsers that can’t handle it. In either case you cheat your end users.It’s inflexible. Sites that were created for any device will be much more flexible in all kinds of situations because the web developer planned for the unknown. Conversely, if you rigidly sort devices into groups and then code for those groups, this rigidity is going to make your site unable to react to the unforeseen.
Scoop.it!
Recently Mike Rowehl, a mobile developer with relatively little knowledge of the web world, confessed to being baffled by the attitude of web developers interested in mobile. He feels there’s a disconnect between what web developers do, what they’re supposed to be doing, and the tools mobile vendors make available to them.
Mickael Ruau's insight:
Progressive enhancement is the key to mobile web development. In the next installment I’ll talk about this concept a bit more.
Scoop.it!
Back in March of 2003, Nick Finck and I stunned the Web design world at the South by Southwest Interactive conference in Austin. How?
Mickael Ruau's insight:
We've talked about how style can be correlated to basic HTML frameworks, customized and targeted at certain browsers, and how to make sure others don't see it at all. We showed you how to achieve bandwidth savings and make your pages more accessible, through the use of sparse markup, caching of stylesheets and scripts, and structure geared towards the lowest common denominator.
Scoop.it!
A simple example of Unobtrusive Javascript and jQuery to give Progressive Enhancement
|
