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 labled 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.
by Brian Fling
Have you ever considered that the way you design and build a site or app might be completely wrong? Have you ever actually had to support the top devices on the market, let alone make each of them amazing? Have you ever designed or built a mobile app for devices that don't even exist yet? Do you know how to do all of this and still come in under budget?
These are just some of the questions that are being answered deep within the mobile community. It is unlike the web. It is opaque. It is competitive. It is an entirely different medium. And it is really really hard. In fact, there is a good chance that everything you think you know about mobile is wrong.
In this session by Brian Fling—author of O'Reilly's Mobile Design & Development (http://mobiledesign.org) and Creative Director at pinch/zoom (http://pinchzoom.com) —he discusses his experiences of spending a decade between web and mobile and shares what what he thinks the web community can learn from mobile.
by James Pearce
Few have the chance to create web-based mobile services from scratch. After years of investment in existing platforms (such as content management systems), how can you re-use your content, your servers, and your knowledge and evolve them to meet the mobile challenge? In practical terms, we look at systems like WordPress and Drupal, and show how we can quickly start to reuse them to build consistent mobile services from existing resources.
No one who advocates for the mobile web wants to admit it, but it is true. Native is easier.
It's easier to sell to stakeholders. Easier to monetize. And most importantly, easier to implement.
Argue about programming languages, memory management and reach all you want. There is one undeniable disadvantage that the mobile web faces that native apps don't--over a decade of legacy code, cruft and entrenched organizational politics.
But the web is essential. Even companies whose businesses are centered on native apps need web pages to sell those apps. We can demonstrate time and again that a web-based approach is a smart investment.
So how do we sell mobile web projects? How do we work with the systems we currently have to build compelling mobile web experiences?
And most importantly, how should we be changing our web infrastructure, tools and workflow for the coming zombie apocalypse of devices.
11th–12th April 2011