The Best of the Internets
ESPN launched its responsive site. I still need to tuck into it, but here’s a little background as to why:
In January, 61 percent of ESPN’s roughly 94 million users in the United States were viewing content exclusively on mobile devices, with a good chunk of that viewing content on its mobile web version. For a massive company like Disney trying to make a shift to mobile like any other content-driven company, a test of a new mobile web strategy for a large property like ESPN is critical.
Testing “new” tech isn’t really a new thing for ESPN. Those of you who have been on the web a while might remember it being one of the first really big sites to embrace CSS and web standards, back in 2003.
Coding HTML emails is one of those necessary evils, but Ted Goas offers some helpful advice and links in this post.
This is an open letter to designers and developers who’d rather not work on email.
And then it was revealed:
Windows["Microsoft Edge"] = new Browser();
I gotta believe the origins of the name go back to IE8’s “version targeting” scheme. Remember this?
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Yes. Yes it does. Some great stats in here including this gem:
O’Neill Clothing saw perhaps the most impressive increases after their conversion to mobile-ready. Transactions went up 112.50% on iPhones and 333.33% on Android. Conversions rang in at 65.71% on the iPhone and 407.32% on Android. Total revenue cleared 101.25% on iPhone and 591.42% on Android.
Bruce Lawson is dead-on with his critique of Apple’s feedback on Web Components:
Implementation is hard. Too hard for the developers at Apple, it appears. So Web developers must faff around adding ARIA and tab index and keyboard listeners (so most won’t) and the inevitable consequence of making accessibility hard is that assistive technology users will suffer.
We (browser makers and web developers) need to be willing to put in the effort to make things better for everyone else. Sadly, few seem interested.
Thanks for calling this out Bruce!
This is a brilliant post from Scott Jehl about optimizing page render by getting particular about how (and when) certain assets load. He uses the real-world site Wired as a test bed for putting the ideas into practice, cutting perceived load time by a full 8.5 seconds!
Abstraction can be helpful, but it also complicates things and leads to slower performance. Andrea Giammarchi provides lots of details here in examining a complex app scenario with the good old fashioned DOM vs. a handful of frameworks. Bonus points for the fact that most of the video evidence tests are being run on non-iOS devices!
No, the DOM is not your problem, the fact you brought an over-engineered abstraction on top of a deadly simple task, like a table that needs some quick update, is the real problem you don’t want to see.
If you dig Andrea’s post, you should also check out this post from the Filament Group.