For years, most Web teams have designed for the desktop. Mobile, if it even happened, was a port off the desktop version, designed and built before anyone even considered the mobile experience. This made perfect sense for a while. Browsing the Web on mobile phones was painful; carriers controlled access to the Web on their devices; and mobile network speeds made everything often grind to a halt.
But things have changed so dramatically over the past few years that starting with the desktop may be an increasingly backwards way of thinking about a Web product. Designing for mobile first can not only open up new opportunities for growth, it can lead to a better overall user experience for a Web site or application.
In this session, Luke Wroblewski will dig into the three key reasons to consider mobile first: mobile is seeing explosive growth; mobile forces you to focus; and mobile extends your capabilities.
Currently there's a discussion raging about the advantages of the mobile web over native apps, and vice versa. Although native apps will not disappear, they'll gradually grow less important relative to the web.
In this session we'll take a look at the future of the mobile web, which will involve new ways to pay for content, new ways to distribute web apps, and further integration of web technologies with mobile technologies such as SMS.
Context is often cited as the single most important factor in design for the mobile medium. Mobile devices are of course 'mobile', but they are also small, always on, always with us, and can instantly connect us to the people we love. Mobile services must therefore be simple, social, and well-focussed--enabling us to quickly get things done on even the smallest screens.
This is all well and good, but mobile devices have changed. They may be mobile, but many have already stopped being 'phones'—nor do they resemble what we traditionally think of as computers. This presentation will explore how our use, and perception of mobile devices is changing, and how these changes may impact how we should design for them going forward.
by Brian Leroux
The world is enthralled with this next ambitious iteration of the web labeled HTML5. An amazing array of new features including: offline access, client storage, media, webfonts, new form elements, canvas, svg, css and more. While the spec is still being worked on most of these things are here today in most modern browsers. So what will be next? There are more web enabled handsets than television sets. But this isn't the whole story. Mobiles bring a whole new level of intelligence to computing by way of enhanced sensors and contextual data. This next revolution, Device APIs, is being prototyped in the PhoneGap project. Join Brian for a rowdy look at the not so distant future of the web.
We're reaching a point in time where the device is now enabling interactions and behaviours in the physical world. We live in a task-oriented world and with technology becoming less visible (due to good design), we are well on our way to creating experiences that the mass audience can consume. How do we make technology less visible? What kind of design results in new physical behaviours? Why is this important for the future? These are some of the questions I'm going to have a go at tackling.
12th–13th May 2011