The panel ended with a collection of things that make libraries desirable. Amongst those were:
- small size
- the ability to choose your own components
- good documentation
- a strong community
…things that would most probably also be applicable for any library for mobile browsers - especially in this order.
Dan Cederholm - Bulletproof Webdesign
Many of the workarounds presented by Dan were simple techniques, such as applying a background color to an area with a background image in order to make the font on this area still readable if images in the browser are turned off. But still these things have to be kept in mind, especially in the mobile area, where you will find a lot of different environments - a lot more than in the area of desktop PCs.
Cameron Moll - Mobile Web Design
This talk was entirely focussed on mobile devices, it was also Cameron’s first time he did a talk (on his own) in Europe - and he did a very good job! These were the key facts presented by him:
- mobile devices are widely spread:
- almost everybody in the audience did browse the web with a mobile device (only 4 people of those were delighted by the experience though)
- by 2009 3 billion people will own a mobile phone, thats almost half of the entire (expected) world population by then
- there are more mobile phones than there are PCs, even more than landline phones
- the mobile web is diverse and different:
- a small poll asking 400 people revealed: 159 unique handsets, 19 handsets, 44 countries, 12 carriers
- mobile phones supported WML, XHTML(-MP/-BASIC), inconsistent standards, plethora of agents, XHTML/CSS support is highly iconsistent
- the question must not be “how do i do a website similarly on a mobile phone?”, but it should be asked without the “similarly”
- “mobile” means “mobility”, so the whole experience changes
- mobile web development fundamentals:
- most devices are WAP 2.0 (= XHTML-MP, not WML) but are backwards compatible
- testing to some extend can be done in a desktop browser
- test need to be done on target devices, not in emulators
- Cameron put up some mobile test pages on his site
- mobile web development methodologies:
- there are several ways:
- do nothing (such as craigslist - no images anyways) or strip images and styling
- use handheld stylesheets (the poster child of the mobile web)
- create a mobile specific page (double the work)
- decide between mobilizing or miniaturizing
- miniaturizing means to keep the content and miniaturize the look and feel
- mobilizing also involves the creation of a mobile-specific version
- the creation of a mobile-specific version was promoted as being the better way in many cases, because most webservices (Cameron used craigslist.com as an example) just have different use cases on a mobile phone than on the desktop (other functions will be needed there)
- guidelines for mobile web development:
- the W3C mobile web best practices contain things such as considering access keys, short URIs, text equivalents for images and 120px as the baseline width
Cameron closed his presentation by speaking about mobile web ideology and pointed out that the mobile web needs to be desirable, dependable and disciplined. We need an array of thought leaders and there is a stong need for user agent consistency. He also expressed his wish for a mobile device wiki, where developers can collectively collect their findings and experiences on different mobile devices.
After his talk I approached him and explained my idea of a collectively-created mobile browser support chart - he liked it :) Too bad I missed him later that day at the social event.
@media 2006 was a big success in general and an inspiring event for me. As usual on events like this, I met many interesting people and I am looking forward to next year. The next event of this kind for me will be d.construct 2006 in Brighton, England.