by Horace Dediu
An analysis of the mobile computing market through a disruptive lens. Asymmetric competition, jobs to be done, value chain evolution, competition with non-consumption. How did a few entrants capture the industry profits from entrenched incumbents and what will happen next?
OK, so in mobile there are about 25 browsers, 20 operators, 15 device vendors (excluding the tiny ones), and 10 operating systems. Do you know your way around all of them?
Especially for people who come from the quiet, reclusive zone that is the desktop web, with only 5 browsers and 3 platforms, the mobile world can be a daunting place where everything happens at once, relations are much more complicated than you expect, and the sheer amount of actors is confusing.
In this session PPK will attempt to bring some order in the chaos by discussing about seven of the most important actors, their relations, and their long-term plans. After this talk you can amaze your friends by explaining why Windows Phone will never amount to much, why Android fragmentation will become only worse, in which way Apple has stolen a march on its competitors, and what Nokia is doing.
by James Pearce
The web deserves to be the third mobile runtime, but it isn't. What is holding it back? It faces challenges from industry, the standards process, browser implementations, and probably our own short-sightedness.
The web's unnerving ability to disrupt shouldn't be taken for granted. It wants to evolve, but we must encourage that process in order for it to become competitive again.
On a journey from device APIs to standards groups, from test suites to provocative demos, let's figure out how to move the web forward towards a brave mobile future.
by Eugene Goldin and Greg Schechter
This is the story of the glory and struggle of bringing a high quality YouTube experience to the mobile web. Once upon a time there was a web developer who wanted to play videos on the web. So he filmed a cat and wrote a Flash and a HTML5 player. He spent many hours making it work on his favorite desktop browsers and even the one his grandfather still used. People could watch his cat video, he smiled, and the world was good. Then one day someone put a browser in a phone and soon there were many phones with many different browsers. This new set of environments were even harder to develop for and had a slew of new terrifying bugs. The web developer was miserable knowing people couldn’t watch his cat video. With much time and effort he figured out many of the secrets needed to combat the evils of the different mobile platforms. Once again people could watch his cat vid eo, he smiled, and the world was good. The end.
Most mobile Web developers come from a traditional desktop development background. As such, many are not aware of key differences between desktop browsers and mobile browsers once they are trying to build an app vs a traditional web site, even if adapted for mobile. In this introductory session aimed at desktop developers interested in making the jump to mobile, we will present the technical tricks that are needed to circumvent a mobile browser's own interface (touch and gesture management, viewport and other aspects) to deliver a web app that looks and feels like a native app. We will discuss among other things how to virtualize the browser's own event loop, block swipe and pinch/zoom gestures, pin down the viewport, and a simple trick to build a mobile touch-based app that also works on a desktop browser with mouse events.
The "web versus native" debate is raging among mobile developers. Build native? You're locking yourself into a (usually closed and proprietary) platform and duplicating effort. Build for the web? You're sacrificing performance and features that benefit users. Like most divisive debates, there's a lot of truth on both sides.
The Web is powered by countless content management, eCommerce and marketing systems. Client-side adaptation - complemented by responsive, mobile and iPad design - is a powerful technique for launching mobile and iPad web experiences for virtually any website. Using Bonobos, a leading men's retailer, Igor will discuss some of the challenges internet businesses face today and the huge growth opportunity behind extending their web capability to mobile and tablet devices.
Device diversity is about to get an order of magnitude worse. SmartTVs are hitting the market in mass this year. Sony, LG, Vizio, and Samsung are all shipping televisions with Google TV built in.
And if the rumors that Apple will release a TV this year are true, 2012 will turn out to be the year web developers start to tackle the glass screen hanging on our walls.
Why should web developers focused on mobile learn about the web on TVs? Because TVs represent the next challenge in device proliferation. They share common characteristics with their smaller brethren. They create new challenges and opportunities we haven't encountered yet. And most importantly, learning how to build for TVs helps inform our practices of building for mobile devices.
Modern web technologies and responsive design aim at platform independent code while promising first-class experience on any mobile device. Even though purely web-based approaches can achieve stunning results, they (still) cannot compete with their native counterpart regarding platform features and integration.
During this panel representatives of Google, Nokia, Opera, and RIM will discuss problems and solutions in the mobile browser world. The exact topics of the conversation will be decided during the conference itself.
The mobile browser panel will once more be moderated by Jeremy Keith.
by Scott Jenson
Today's mobile phone is a combination of two aging paradigms: native applications and web browsing. Each is fine on their own but the mixture is actually taking the worst of both. The mobile web has the potential to be a transformative technology, doing so much more than just downloading a web page on a small screen. Native applications, for their part, are a siloed holdover from main frames, forcing the user to manage the discovery, installation, and removal of all functionality.
This is tolerable today because there is relatively little need to manage functionality on your phone. Installing a few apps really isn't that burdensome. However, the plummeting cost of processing and connectivity will change that creating an explosion of smart posters, devices, televisions, and more, all of which will likely require their own 'app'. It just isn't possible to install an app for every store I visit, every product I own, and and every smart thingy I pass in the street. This talk will explore a new approach, combining the best of native and mobile web to create a 'just-in-time' model of functionality.
by Stephen Hay
In our industry, everything changes quickly, usually for the better. We have more and better tools for creating websites and applications that work across multiple platforms. Oddly enough, design workflow hasn't changed much, and what has changed is often for worse. Through the years, increasing focus on bloated client deliverables has hurt both content and design, often reducing these disciplines to fill-in-the-blank and color-by-numbers exercises, respectively. Old-school workflow is simply not effective on our multiplatform Web.
In this session, Stephen explores at a content-based approach to design workflow which is grounded in our multiplatform reality, not fixed-width Photoshop comps and overproduced wireframes. You'll learn how to avoid being surprised by the realities of multiplatform websites. You'll learn how to better manage client expectations and development requirements. You've probably heard of designing in the browser; in this session you'll learn a practical approach for actually doing it.
by Remy Sharp
Mobile debugging is a bitch. Let's talk about that, and then fix it.
In this fun and down to earth session, Seb will demo his new project "PixelPhones", which turns all the phones into individual pixels on a large audience sized display. We'll also be looking at how we can use this network of phones to bring an audience together, experimenting with multi-player games and toys.
The project runs in a mobile phone browser on Android and iOS, and Seb will be talking through the development process, and exactly how he solved the two main challenges with this project - finding the phones and synchronising them together.
He's been working to improve this project, and we're hoping to run it on a scale that's never been attempted before! There'll be prizes for the games, so make sure your phone is fully charged before you arrive if you want a chance to win.
This panel discusses how web developers will get access to phone functionality such as the address book and the camera, as well as access to payment systems that tie in with the mobile operator. These APIs are fairly new, and they represent a new kind of functionality that simply wasn't there before, so we're expecting a lively discussion. This panel will be moderated by Jeremy Keith.
The Application Cache is one of the cool bits of HTML5, allowing sites to work without a network connection brings us much closer to native app-like behaviour. However, from HTML5 roundup articles and talks you may be left with the impression that it's a magic-bullet fix, unfortunately it isn't, the Application Cache is a douchebag.
I don't mean 'incompetent' or 'difficult', definitely 'douchebag'. The Application Cache has skills we need, but if you asked him to paint your bathroom he'd somehow manage to flood your kitchen and break your TV in the process, and he wouldn't care.
We'll look at how to use the features of Application Cache without the horrible side effects, comparing techniques you'd use for a simple clientside app and a large content-driven site. We'll explore the many gotchas left out of most AppCache articles and how you can build your site to survive them.
by Brad Frost
As the digital landscape continues to become more complex, it's essential for us to start thinking beyond the desktop and embrace the unpredictability of the future. Mobile is forcing us to rethink the content we create and the context in which people interact with our products and services. This session will cover how to change our thinking and start acting differently in order to create more future-friendly experiences.
You've likely heard about content a lot lately—content is king, content should flow like water, "Content First!". But what IS content in its basest form? Is it HTML? XML? JSON? Is it human-readable plaintext? And once we have our content, how do we transform it to look wonderful on mobile devices, televisions, regular old computers, refrigerators? Where does content end and platform-specific representation begin? The mobile revolution has shown us that our content management and web publishing technologies are entangled and flawed. The web will continue to be consumed by more and more clients, many of which haven't even occurred to us yet. But by thinking deeply and re-examining the essence of our content, we can help to architect a flexible future for the web.
by Brian Fling
For over 10 years Brian Fling has been designing for mobile apps and devices. In that time he has discovered a variety of techniques and methods not to just create a beautiful visual language, but to create meaningful products that have the power to change people's lives.
In this session, Brian uses the design principles of Dieter Rams, Mies van der Rohe, and Steve Jobs -- as well as his own insights and experience -- to create a simple framework you can use for creating amazing mobile designs.
10th–11th May 2012