I know. I know! It’s been far too long since episode 117. But fret no more, Unfinished Business fans, we’re back and back for good, every two weeks with some brilliant guests and some good old fashioned conversations. This week, I’m joined by Sean Johnson and Drew McLellan to talk fat and fitness, cruises and coach trips.
Tagged with “development” (262)
Everything about web page layout is changing. New CSS specifications will make it possible to do designs we’ve never seen before. Rachel Andrew joins Jen Simmons to talk about what’s happening.
The network is intrinsically unreliable. More so, the network is out of your control as a developer. Therefore, we must design systems which embrace the unpredictability of the network and defend against it all costs. How can you prioritise the delivery of your core content? What best-practices can you use to optimise your assets? How are APIs such as ServiceWorker changing the way we think about the network? Patrick is a front-end engineer at the Financial Times in London where – amongst other things – he is helping to build the next generation of their web platform. Prior to the FT he spent the last 3 years developing theguardian.com. When not speaking or ranting about performance he enjoys spending his spare time discovering new food and craft beer.
Progressive enhancement sounds practical, but not for your current project, right? Good news: you’re wrong!
In this session, Aaron will debunk the myths that often preclude individuals and organizations from embracing progressive enhancement and demonstrate solid techniques for applying progressive enhancement in your work.
By the end of this session, you’ll walk away with
a better sense of the devices people are using to access the Web,
a framework for envisioning experience as a continuum, and
a solid understanding of how to improve the accessibility and reach of your Web projects.
Come find out why progressive enhancement isn’t just for “content” sites (whatever those are).
Performance is not a technical problem.
Over the 8 years of its life, Dropbox’s CSS codebase has grown to a considerable scale. Dan talks about how their CSS has grown, the pains of inheriting a large CSS codebase, and some of the approaches for refactoring and scaling CSS at scale.
Paul and Jake talk about how to Promisify Node, the sins of CSS, and how hard it can be to find a door handle.
Measuring 3,000 private school websites in our report, Private School Digital Insights (August 2014), uncovered lots of interesting statistics about website navigation and design.
But one stat, in particular, answered some questions that I think many of us were curious about:
With the rise of mobile devices, how are private school websites adapting? More specifically, are they utilizing responsive web design (RWD)?
Our research revealed that 22% of private schools sites (August 2014) utilized responsive web design — meaning their designs responded to whatever device was accessing it — mobile, tablet or desktop.
We took another look at this group in early 2015 and saw a 9% jump to 31%. Here we are a year later, and I think it’s fair to assume another significant leap in RWD adoption.
Here’s the takeaway — schools understand that they need to display their content in the best possible way across all devices, both in front of and behind the password.
Just imagine a parent visiting the admission section of a non-RWD site via their phone? What kind of an impression does that leave?
But have you ever wondered about the origins of responsive design and how it became a standard in such a short time? Who had the foresight to see the need for a better, more flexible way to display web content across the ever increasing range of devices?
Joining me to talk about the birth and rise of responsive design is the man who founded the concept, Ethan Marcotte. Ethan is a designer, developer, author, and podcast host in Boston, MA, who unveiled the idea of responsive web design in a blog post on a list apart in May 2010.
From that simple article, a more flexible approach to design has been adopted by a huge range of sites including the Boston Globe, Time Magazine, CNN, Starbucks, and of course 31% of all private school sites! His approach has redefined the way we all interact with websites today.
So let’s get into a time machine and head back to 2010. Ethan talks about the days, weeks, months leading up to his blog post for a list apart. What was going through his head at that time? How & why did his thinking about web design land on the concept of responsive?
Ethan introduced the approach, but lots of concepts get introduced every day. Hear how RWD emerged from an idea to design standard.
Learn how has responsive web design matured from 2010-2016.
“What does it feel like to know that you’ve changed the way people all over the world access websites?” A big question, hear his answer.
Let’s get tactical, according to Pew, 64% of Americans own a smartphone, plus the usage stats are interesting. Knowing this, there’s a growing movement to design mobile first. Ethan shares his take.
In his new book (http://abookapart.com/products/responsive-design-patterns-principles), Ethan talk about the future of RWD — hear his take on what the future holds for RWD.
Let’s get prescriptive. For someone about to jump into the process of creating a new site design to replace a non-RWD site, Ethan offers advice.
Talking about the Internet of Things is all the rage these days. What is it about, and why is there so much hype? Will an ecosystem of internet-connected “devices” take over our lives? What role does the web play in all this? Stephanie Rieger joins Jen Simmons to discuss. Then Jonas Sicking joins Jen for a second interview, to talk more about what how the web might be involved.
In today’s episode, I interview Una Kravets, developer at IBM and prolific open source advocate.
Page 1 of 27Older