RWD BLOAT // Speaker Deck
Dave’s great slides from a presentation on performance and responsive design.
Dave’s great slides from a presentation on performance and responsive design.
A great primer on using
picture. I think I’ll be referring back to this a lot.
This was a fun podcast—myself and Cyd from Code For America talk to Karen and Ethan about how we worked together. Good times.
The audio is available for your huffduffing pleasure.
Patty’s excellent talk on responsive design and progressive enhancement. Stick around for question-and-answer session at the end, wherein I attempt to play hardball, but actually can’t conceal my admiration and the fact that I agree with every single word she said.
I share the concerns expressed here about the “sizes” attribute that’s part of the new turbo-powered img element (or “the picture element and its associates”, if you prefer). Putting style or layout information into HTML smells bad.
This is a concern that Matt Wilcox has raised:
Change the design and those breakpoints are likely to be wrong. So you’ll need to change all of the client-side mark-up that references images.
I can give you a current use-case: right here on adactio.com, you can change the stylesheet …so I can’t embed breakpoints or sizes into my img elements because—quite rightly—there’s a separation between the structural HTML layer and the presentational CSS layer.
Following on from that post of Jason’s I linked to, Chris also emphasises that, for most use cases, you probably only need to use srcset (and maybe sizes), but not the picture element with explicit sources.
It’s really, really great that people are writing about this, because it can be quite a confusing topic to wrap your head around at first.
Jason points out that the picture element might not be needed for most responsive image use cases; the srcset and sizes attributes will probably be enough—that’s what I’m doing for the photos on my site.
I remember reading Gia Milinovich’s reports from the set of the in-production Danny Boyle sci-fi film called Sunshine back in 2005. Then the film came out, exceeded my expectations, and became one of my all-time favourites.
Now the website—which was deleted by Fox—has been lovingly recreated by Gia. (And it’s responsive now.)
I had a good ol’ chat with Justin Avery from Responsive Web Design Weekly. We talk about performance, Responsive Day Out, and yes, progressive enhancement.
Those lovely people at Filament Group share some of their techniques for making data tables work across a range of screen sizes.
Dave wanted to figure out if having a responsive site necessarily meant taking a performance hit, so he ran the numbers on his own site. It turns out all of performance-related issues are not related to responsive design.
If you’re going to check out the New Yorker’s nice new responsive site, might I suggest you start here?
Here’s an intriguing approach to offering a navigation control that adapts as the user scrolls.
I’m not too keen on the way it duplicates the navigation in the markup though. I might have a play to see if I can find a way to progressively enhance up from a link-to-footer pattern to achieve this.
A peek behind the scenes of an interesting new navigation pattern on the Guardian’s still-in-beta responsive site.
You can try it out here
A concise case study from gov.uk:
Designing for the constraints of mobile is useful – if we get the fundamentals of the service working on small screens and slow network speeds, it can work on more capable devices.
Neil Berry writes down his thoughts prompted by Responsive Day Out 2.
A great blow-by-blow account of Responsive Day Out 2 from Simon R Jones.
Phil Baker writes up his thoughts on all the day’s talks.
What follows here is not a full account of each talk, you can listen to the audio recordings for that. This is more a collection of my main take-aways for the day, and what I found most interesting.
Marc Jenkins shares his thoughts on Responsive Day Out 2.
Another lovely write-up of Responsive Day Out 2.
Now this is what I call a conference write-up. Paul synthesises the talks from Responsive Day Out 2 into five principles for responsive design:
Sally and I will be speaking at this free evening in London on August 7th.
Here’s the Creative Commons licensed music that was playing during the breaks at Responsive Day Out 2.
Here’s Kirsty’s retrospective of Responsive Day Out 2, from the perspective of a speaker and an attendee.
Thanks to the tireless efforts of the magnificent Drew McLellan, the podcast of all the talks from Friday’s Responsive Day Out 2 are now available for your listening pleasure.
As well as delivering a terrific talk at Responsive Day Out 2, Ida has also written up her detailed notes of the day.
Adam Onishi’s write-up of Responsive Day Out 2, paying particular attention to the format and the curation of the day.
Jeremy puts together two fantastic conferences in Responsive Day Out and dConstruct, both of which I will have attended for the first time by the end of the year and I don’t think there’s a coincidence in that. Responsive Day Out was a truly fantastic conference, and it was all down to the curation of the conference, because quite literally there wasn’t anything else.
As always, Orde Saunders took copious notes at Responsive Day Out 2. The man’s a machine!
Sally’s talk at Responsive Day Out 2 was really, really great—it kinda blew my mind. I’m so, so happy she agreed to be a part of the event.
Here’s her description of the day and the other talks. Pay attention to the closing call:
I didn’t get to meet everyone I wanted to, but you should all come back for dConstruct in September as I’m sure that it’ll be even better than this weekend was.
Another great write-up of Responsive Day Out 2, this time from Hidde de Vries, who came over to Brighton from the Netherlands.
A terrific write-up of Responsive Day Out 2 by David Watson, tying together many of the day’s strands.
This is what Oliver was talking about Responsive Day Out 2 — a new approach to information architecture.
Cast off your sidebars! You have nothing to lose but your grids!
Photos from the rather wonderful second edition of the Responsive Day Out in Brighton.
A lovely little tale of empowerment through HTML and CSS.
If you’re coming to the Responsive Day Out next week, bring your dog. Laura is organising a special Web Talk Dog Walk for the next day.
A look at how the website for An Event Apart is using the picture and Picturefill …featuring Jessica as the cover girl.
This is an interesting observation about the design of cassette inlays. It reminds of Paul’s presentation at the Responsive Day Out when he looked at the “responsiveness” of television idents.
A handy little bookmarklet for quickly checking how a site might look at different screen sizes, and you can customise it to use whichever screen sizes you like.
A thoughtful in-depth piece that pulls together my hobby horses of independent publishing, responsive design, and digital preservation, all seen through the lens of music:
Music, Publishing, Art and Memory in the Age of the Internet
A nice summation by Dan of when it makes sense to use a graphic design tool like Photoshop and when it makes sense to use a web browser.
A reusable set of responsive patterns and templates for UK councils.
Yaili is documenting the process of retrofitting ubuntu.com to be responsive. I’ll be avidly reading each post in this series.
A terrific post from Trent, touching on all the important facets of building for the web: universality, progressive enhancement, performance …great stuff!
A handy way of automating the creation of old-IE stylesheets using Grunt. This follows on from Jake’s work in using preprocessors and conditional comments to send a different stylesheet to IE8 and below—one that doesn’t contain media queries. It’s a clever way of creating mobile-first responsive sites that still provide large-screen styles to older versions of IE.
Some good ideas on the idea of element-level media queries, a feature that developers are crying out for and browser makers are saying is too hard. This post has some thoughts on how to deal with the potential issues.
An interesting pattern for handling complex data tables in responsive designs. It’s a desktop-down approach, but pretty smart.
Great stuff from James Wragg and the gang at Madgex: a way of lazy-loading ads for responsive sites without messing with the ad code.
A great write-up of the design process behind The Guardian’s responsive site. It’s really gratifying to see UX designers talking about performance.
A nice look at responsive design, progressive enhancement, and the principle of One Web.
A great series of articles on the sci-fi films of the ’60s and ’70s:
The Laser Age examines a rich period in the history of science-fiction filmmaking that began in the late 1960s and faded away by the mid 1980s.
…all wrapped up in a nice responsive design too.
I think Chrome is doing the right thing by removing the 300 millisecond tap delay on sites that set width=device-width — it’s certainly better than only doing it on sites that set user-scalable=no, which felt like rewarding bad behaviour.
The transcript of Mark’s talk from last week’s Handheld conference in Cardiff.
There are mountains.
I like this CSS solution to sideways-scrolling tables for small viewports. It’s not going to be right for every situation but it’s a handy trick to keep up your sleeve.
This is the talk I gave at the border:none event in Nuremberg last month. I really enjoyed it. This was a chance to gather together some thoughts I’ve been mulling over for a while about how we approach front-end development today …and tomorrow.
Warning: it does get quite ranty towards the end.
Also: it is only now that the video is released that I see I spent the entire talk looking like a dork with a loop of wire sticking out of the back of my head.
The title is a bit sensationalist but I agree completely with what Karen is saying:
It’s time we acknowledged that every responsive web design project is also a content strategy project.
A wonderful piece by Ethan taking issue what the criticism that responsive design is over-reliant on screen size. Instead, he says, it begins with screen size, but there’s no limit to where we can go from there.
Responsive design might begin with the screen, but it doesn’t end there.
Dan Bricklin—co-creator of the original VisiCalc spreadsheet—turns his attention to responsive design, specifically for input-centric tasks.
Dan gives some insight into what it took to make his personal site responsive. Stay tuned: there’ll be more of this.
A great presentation from Brian Boyer on NPR’s mobile strategy. Spoiler: it’s responsive design.
Here’s the CSS and markup you need to make third-party iframes responsive. Handy!
Some good-lookin’ stats from a responsive redesign:
Total page views, a metric we were prepared to see go down with the redesign, are up by 27%. Unique visitors per week are up 14% on average and visits per week are up on average 23%.
Jason recants on his article from a few years back when he described responsive design as “fool’s gold.”
Responsive web design: it’s solid gold, baby.
On the one hand, this is yet another Snowfall clone. On the other hand, the fact that it’s responsive is impressive.
WebKit nightlies now have support for
srcset. I’m pleased to see that it’s currently constrained to just handling the case of high-density displays; it doesn’t duplicate the media query functionality of
I’ve always maintained that the best solution to responsive images will be some combination of
picture: they each have their strengths and weaknesses. The “art direction” use case is better handled by
picture, but the “retina” use case is better handled by
Looks like Google are offering responsive (or at least adaptive) ad sizes.
A call for developers to let standards bodies know what we want:
It is important that we as developers focus on the right things again. If you encounter a bug, you should not only fix it for your site; you should reach out to browser vendors and web standards people to fix this in a long-term solution. It might cost you a few minutes, but brings a lot of improvement to the whole developer community.
A page to demonstrate the conditional CSS technique I documented a while back.
A nice collection of navigation patterns for responsive designs. The demos aren’t using a mobile-first approach, and they’re reliant on jQuery, but they could be easily adapted.
A terrific case study in progressive enhancement: starting with a good ol’ form that works for everybody and then adding on features like Ajax, SVG, the History API …the sky’s the limit.
A comprehensive look at the current state of things in the world of responsive design, with a look to possible future APIs.
Here’s a nifty trick: using text-align: justify to get a nice responsive grid layout.
A lovely little highlight reel that Craig put together from the Responsive Day Out.
Some good thinking from Jason here. In a roundabout way, he’s saying that when it comes to responsive images—as with just about every other aspect of web development—the answer is …it depends.
Some thoughts (and code) on responsive images.
A handy plugin for Chrome that always you to inspect media query breakpoints and take screenshots at any of them.
A couple of years ago, the benefits of separate sites were more clear to me. Today, I can’t think of a good reason to maintain a separate mobile site.
Trent hammers home the point that the kind of compartmentalisation that’s traditionally been part and parcel of the web dev workflow just won’t cut it anymore.
Keep it under your hat, but Paul has soft-launch his Project Portillo. And very nice it is too.
Dave talks about the kind of deliverables that get handed over in a responsive project. Sounds a lot like what we do at Clearleft.
Responsive deliverables should look a lot like fully-functioning Twitter Bootstrap-style systems custom tailored for your clients’ needs.
A terrific, in-depth round-up and recollection of the Responsive Day Out by Laura that ties all of the strands together.
Good writing. Good design. Good food.
I agree with David: most pre-rolled grid “solutions” are way too complicated. And in any case, applying a pre-existing grid framework for a new project seems kind of like applying a pre-existing colour palette.
As David points out, it really needn’t be so complicated.
A report on the Responsive Day Out that focuses on three themes from the day: progressive enhancement, process, and design systems.
Benjamin’s notes from the Responsive Day Out.
A nice write-up of the Responsive Day Out from three different perspectives.
An excellent explanation from Tom Loosemore on why the Government Digital Service is putting its energy into open standards and the web, rather than proprietary native apps.
A write-up of the Responsive Day Out from the perspective of a designer whose background is off-web:
Unlike the experts, I haven’t had to make the transition from designing for desktop for years to suddenly becoming device agnostic, which is what I think the main issue seems to be.
This is the full text of Owen’s talk at the Responsive Day Out. It makes for a terrific read!
Here’s Keir’s roundup of the Responsive Day Out (which was preceded by a Shopify meetup the night before).
The “client hints” proposal looks really interesting: a way for user-agents to send data to the server without requiring the server to have a library of user-agent strings. But Scott has a few concerns about some of the details.
Another in-depth round-up of the Responsive Day Out, this time from Vasilis.
Yet another round-up of the Responsive Day Out. I’m pleasantly surprised by the number of people that have been blogging since the event.
An in-depth blow-by-blow account of the Responsive Day Out by my fellow Brightonian.
Another nice set of photos from the Responsive Day Out.
A write-up of the Responsive Day Out from one of the Belgian contingent. They’re a notoriously hard-to-please bunch but it sounds like a good time was had nonetheless.
Sadly, the ol’ “web app” get-out-of-jail-free card is whipped out once more. You know the one I mean.
The slides from Andy’s excellent pragmatic talk on performance and aggressive enhancement at the Responsive Day Out.