This document discusses the need for websites and applications to be designed in a "future-friendly" way to accommodate unpredictable technological changes and new devices. It notes that the distinction between mobile and desktop is blurring as screens and usages vary widely. Responsive design is presented as an approach that can build sites optimized for all screen sizes through fluid layouts and flexible images. The document emphasizes making content worthwhile and relevant for users across contexts and devices.
LDD Southern Summit 2013 - Adido - The theatre of the future-friendly website
1. The Theatre of the
Future-Friendly Website
Chris Cherrett
Senior UX Developer
Adido
@chrischerrett
#letsdodigital
2. “The future of web and mobile design
is that there is no distinction between the two.”
- Tarun Mitra, 2013
source: https://medium.com/i-m-h-o/587b66677bf3
11. “The things that we create today will exist
beyond what we originally intended them for”
- Brad Frost, 2011
source: http://vimeo.com/29961436
12.
13. You have to reach your target user, wherever they are,
whatever device they use.
14. Today's smartphones are sculpting the landscape of the web
• Mobile web users are estimated to have reached one billion
• Mobile internet adoption has outpaced desktop internet adoption by 8x
• Smartphone sales surpassed worldwide PC sales in 2011
26. Responsive Web Design allows us to build websites
that are optimised for screens of all sizes; small mobile
devices, tablets and large desktop monitors.
RWD will drive the decline of standalone mobile
optimised sites and native apps.
In fact, it is already the trend and the right path to follow.
28. Large-screen and Small-screen user
interactions are polar opposites
(or are they?)
Factors such as Click versus Touch, Screen-size,
Pixel-resolution, optimized markup and many
more have become crucial.
30. Craft an optimal experience — easy reading and
navigation with a minimum of resizing, panning, and
scrolling — across a wide range of devices from
mobile phones to large monitors
• Fluid
• Media queries
• Rules based on device
characteristics
• Proportion-based grids
• Percentages — rather than
absolutes
• Flexible images
• Progressive enhancement
• Context
• Quantitative & Qualitative
33. Fixed
Fluid
vs.
•
•
•
•
A wrapper with a fixed width
Percentage or fixed width
columns
Same width seen by all visitors
A 960-pixel width has become
the “standard”. Most website
users are assumed to browse in
1024×768-pixels or higher.
•
•
Percentage widths
Adjusts to screen resolution
37. isruption will only accelerate. The quantity and diversity of connected devices
— many of which we haven't imagined yet — will explode, as will the quantity and
diversity of the people around the world who use them.
Our existing standards, workflows, and infrastructure won't hold up.
Today's onslaught of devices is already pushing them to the breaking point. They can't
withstand what's ahead. Proprietary solutions will dominate at first. Innovation
necessarily precedes standardisation.
38. Technologists will scramble to these solutions before realizing (yet again) that a
standardised platform is needed to maintain sanity. The standards process will be
painfully slow. We will struggle with (and eventually agree upon) appropriate
standards.
But there’s hope…
39. While we can't know exactly what the future will bring, we can:
1. Acknowledge and embrace unpredictability
2. Think and behave in a future-friendly way
3. Help others do the same
The future is ours to make - friendly
42. Resources
Brad Frost – http://bradfrostweb.com
Future Friendly - http://futurefriend.ly
Medium - http://medium.com
Compete - http://compete.com
“If I have seen further it is by standing on the shoulders of giants.”
- Isaac Newton
Hinweis der Redaktion
Thisused to be the web.
Great to see everyone here today with their iPads, iPhones.It’s not a bad thing (I’m not angry with you)
TheiPad wasn’t around a couple of years agoEaraof Ubiquity
Nobody is a mind readyNobody knows that’s around the corner
(8x – This is been propped up by desktop’s internet adoption itself)
The highlighted area is the only reason anyone would go to this page
Don’t use a lack of real-estate to slash-back functionality
Users want to do the samething on their mobile as theirdesktop