1. Rethinking the Mobile Web
a pragmatic look at creating an accessible and inclusive mobile experience
http://www.flickr.com/photos/fpat/3692425154
2. we
a lovely, location-b
ased,
social, photo thing
y...
this presentation
is
not about these.
http://www.flickr.com/photos/scobleizer/3985020876
apps, and...
3. Dinosaurs!
we think the iPad is pretty awesome, but...
http://www.flickr.com/photos/goincase/4647893507
5. billion
1.8
the number of internet
connections in the world today...
26% of the world’s population at the beginning of 2010 – http://www.internetworldstats.com
6. billion
6.8
the number of people
in the world today...
*2009 estimates put the population around 6.79 billion inhabitants...
7. billion
3.4
the number of people
with mobile devices today...
or roughly 1/2 the population of the planet, which is...
17. about 6% US market share...
enormous
impact
US Population: 307 million
Smartphone penetration: 31% of pop.
iPhone market share: 21% of smp.
Total iPhones in US: 19 million (~6%)
low overall
penetration
The iPhone Reality in Europe: Low Overall Penetration, Enormous Impact
http://moconews.net/article/419-deep-discounts-on-smartphones-drive-u.s.-adoption-rates-to-nearly-a-thi/ and http://www.npd.com/press/releases/press_100510.html
19. only 4% EU5* market share...
enormous
impact
EU5* = France, Germany, Italy, Spain and United Kingdom
low overall
penetration
The iPhone Reality in Europe: Low Overall Penetration, Enormous Impact
http://www.comscore.com/layout/set/popup/layout/set/popup/Press_Events/Press_Releases/2010/6/The_iPhone_Reality_in_Europe_Low_Overall_Penetration_Enormous_Impact
20. <4% global market share*
enormous
impact
low overall
penetration
*I suspect it’s actually much less, but finding accurate global figures is a tad difficult...
21. ie: BMW
The ”most popular” devices don’t necessarily
translate to the most used devices.
ie: Ford
24. the first smartphone in 2003...
considered
portable in 1984
fits in your pocket
still widely used...
Released: 1984
CPU: 8 MHz
RAM: 128k (512k max)
Storage: 400k (3.5” floppy)
Display: 22.9 cm Monochrome
Dimensions: 34.5 x 24.4 x 27.7 cm
Weight: 7.5 kgs
Released: 2003
CPU: 104 MHz
RAM: 6 MB
Storage: 32 MB MMC Card
Display: 5.3 cm Thousands of colours
Dimensions: 10.9 x 5.8 x 2.4 cm
Weight: 122 g
25. the music phone in 2008...
again, it was ‘portable’...?
...this runs Flash
not a feature phone,
nor a smartphone...
Released: 1998
CPU: 233 MHz
RAM: 32 MB (512 MB max)
Storage: 4 GB (+ optical drive)
Display: 38.1 cm Millions of colours
Dimensions: 40.1 x 38.6 x 44.7 cm
Weight: 17.3 kgs
Released: 2008
CPU: 434 MHz
RAM: 128 MB
Storage: 8 GB (16 GB max)
Display: 8.1 cm Millions of colours
Dimensions: 11.1 x 5.2 x 1.5 cm
Weight: 109 g
26. the feature phone in 2009...
smartphone from 2005
extremely
popular today...
still widely
used today...
Released: 2005
CPU: 220 MHz
RAM: 22 MB
Storage: 64 MB
Display: 5.3 cm Thousands of colours
Dimensions: 10.8 x 5.3 x 2.2 cm
Weight: 126 g
Released: 2009
CPU: 369 MHz
RAM: 30 MB
Storage: 1 GB (16 GB max)
Display: 5.1 cm Thousands of colours
Dimensions: 10.6 x 4.7 x 1.5 cm
Weight: 88 g
27. the smartphone in 2010...
...playing “catch-up”
Released: 2010
CPU: 680 MHz
RAM: 256 MB
Storage: 16 GB (32 GB max)
Display: 8.9 cm Millions of colours
Dimensions: 11.4 x 5.9 x 1.3 cm
Weight: 135 g
raising the “bar”...
Released: 2010
CPU: 1 GHz A4 Processor
RAM: 512 MB
Storage: 16 GB (32 GB max)
Display: 8.9 cm Millions of colours
Dimensions: 11.5 x 5.9 x 0.9 cm
Weight: 137 g
28. ”
...but folks with those other phones
simply don’t use the Internet.
http://www.flickr.com/photos/carbonnyc/3369424492
29. ”
yeah, and grandma
doesn’t do Facebook...
Grandma*
Facebook
http://www.flickr.com/photos/amagill/304701054
*not my Grandma
30. billion
1.3
the number of mobile internet
users today...
...includes WAP and ‘real web’ via Tomi Ahonen Consulting
31. 1/3
number of global internet
users who access the internet
only via mobile...
...includes WAP and ‘real web’ via Tomi Ahonen Consulting
34. mobile browser market share
via http://gs.statcounter.com - 02/2010
other?
things have changed
skeptical
UC ate Nokia’s share...
other?
other?
note OperaMini...
quality + sample size?
Data Source: http://gs.statcounter.com
Published Under a Creative Commons Attribution 3.0 Unported License
You are free to copy, distribute and transmit the work and to adapt the work providing it is attributed to www.icrossing.co.uk
http://www.flickr.com/photos/icrossing_uk/4342659861
Blackberry!
35. something happened in February...
UC browser...
Nokia browser...
Top 9 Mobile Browsers in China from Sep 09 to Aug 10 | StatCounter Global Stats
http://gs.statcounter.com/#mobile_browser-CN-monthly-200909-201008
36. moving forward...
used in iOS, Android, Palm WebOS, Nokia Qt,
Bada, Symbian and new Blackberry...
primarily used on feature
phones supporting Java ME...
+
WebKit
OperaMini
watch these...
Windows Mobile
proxy browser...
lots of new browsers, variation and of course – legacy browsers
Obigo
“Fennec”
Internet Explorer
Browser
UC
proxy browsers
MicroB
SkyFire
Internet Browser
37. the importance of WebKit...
open source
licensed under the GNU Library General Public License
excellent standards support
including HTML, CSS3, SVG, etc.
innovations often contributed back
example: HTML5, CSS animations, SquirrelFish, etc.
adopted by many leading companies
WebKit
including Apple, Nokia, Samsung, Google, Palm, etc.
used in many mobile operating systems
including iOS, Android, webOS, Bada, Symbian, etc.
btw - “There is no WebKit on Mobile” by @ppk
http://www.quirksmode.org/blog/archives/2009/10/there_is_no_web.html
38. the importance of OperaMini...
free
costs consumers absolutely nothing
a full-web experience
supports Ajax, zooming, tabbed browsing, etc
excellent standards support
based on the same code-base as the Opera browser
available just about anywhere
on JavaME, iPhone, Android, Windows Mobile + more
an extremely efficient browser
a proxy server filters, compresses & pre-renders content
usable on older devices
breathe new life into those antique devices...
very important
OperaMini
39. proxy browser
rendered + optimised
on proxy server...
and proxy browsers...
free + unlimited
bandwidth
OBML*
limited + costly
bandwidth
HTML
proxy server
bbc.co.uk
*OBML (Opera Binary Markup Language) is highly optimised for mobile networks + devices.
40. on private networks...
caller
a
d
limited + costly
bandwidth
switching
centre
c
receiver
b
base-station
to the Internet...
transcoding, bandwidth limitations, service blocking and no packet neutrality
41. also availabl
e for Android
...
OperaMini is great for browsing
the web on iPhone when your
connection stinks. Which is
unfortunately is fairly often in my
case. – @jonathanstark
http://www.flickr.com/photos/johanl/4424185115
”
63. these are also mobile...
WebKit
approximations based on actual device testing - font rendering will vary...
http://colly.com/
WebKit
64. as are these...
the iPhone is #1 device for OperaMini
*OperaMini is often preferred by many users as it optimises content prior to download, which reduces data costs.
http://colly.com/
70. once again
why are we writing for only one browser...
2000
2010
...is WebKit the new Internet Explorer?
71. ”
“This site works best in Safari 4”
is ok where “This site works best in
IE4” wasn’t?!? Open standards or
double standards? – @csssquirrel
via @brucel
http://www.flickr.com/photos/pjanvandaele/3990379048
72. ”
If you want to use the web on a
mobile device, is the purchase of
an iPhone the cost of entry?
or Android device
this design can work on
*many* more devices...
let alone only one device?
73. as per my highly sophisticated
mobile web triage process... ;)
Good
Could be improved
Needs to be improved
let’s make it more accessible...
http://colly.com/
74. 3 one style sheet w/@media queries
4
jQuery used only for animation...
5 same images used for
all screen devices...
only a few issues...
2
4
well structured,
meaningful markup
Javascript animations tend to work
poorly on the majority of mobile devices...
Good
Could be improved
Needs to be improved
76. 2. use well structured, meaningful markup
for those still paying attention, yes there is a #1 and we will get to it shortly...
77. 2
well structured, meaningful markup...
mmm... meaning!
structure
there’s lots more, but who
wants to stare at code...
http://colly.com/
view source
78. 2
well structured, meaningful markup...
use <header>, <h1>, <p> and other semantically meaningful tags to provide basic structure
*Note: this is not from hp://colly.com
recreating
existing <tags>
is not cool
<div class="body">
<div class="header">
<div class= "h1">
<span>Hello World!</span>
</div>
<div> soup...
</div>
<div class="body">HTML
<span class="emphasis">can actually be</span>meaningful.
</div>
</div>
soup is best served in a bowl...
without a basic, meaningful structure you will need to re-create many existing properties
79. 2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
80. 3
all-in-one stylesheet with @media queries...
a single css file is network efficient, but often includes
unnecessary style data for mobile devices...
<link href="screen.css" type="text/css" rel="stylesheet" media="screen" />
....towards the end of ‘screen.css’ we find the @media queries
mobile specific tweaks are added at the very
end, and only through @media queries...
@media (max-device-width:480px) and (orientation:portrait) { ...
85. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
aha, I told you we’d eventually get to #1!
101. and not a new idea at all...
progressive enhancement
= full desktop site
Jeremy Keith
+ media queries
a mobile site
http://www.flickr.com/photos/clagnut/315554083
104. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
105. 3
all-in-one stylesheet with @media queries...
a single css file is network efficient, but often includes
unnecessary style data for mobile devices...
<link href="screen.css" type="text/css" rel="stylesheet" media="screen" />
....towards the end of ‘screen.css’ we find the @media queries
mobile specific tweaks are added at the very
end, and only through @media queries...
@media (max-device-width:480px) and (orientation:portrait) { ...
106. 3
default stylesheet plus @media queries...
place mobile related styles into a default stylesheet...
<link href="default.css" type="text/css" rel="stylesheet" media="screen" />
<link href="desktop.css" type="text/css" rel="stylesheet" media="screen
and (min-device-width:1024px) and (max-width:989px)" />
link additional style sheets using @media queries
to progressively enhance the content for more
capable browsers
some mobile browsers look for it...
*you may want to use both the ‘screen’ and ‘handheld’ media types for your default stylesheet
107. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
4. progressively enhance using JavaScript
and @media queries
108. 4
jQuery/JavaScript used only for animation...
jQuery is still a rather hefty library
for use on mobile devices...
<script type="text/javascript" src=".../jquery.min.js"><script>
<script type="text/javascript" src=".../scrollto.js"><script>
animation in JavaScript can be
very taxing on mobile devices...
109. mobile browsers aren’t as
capable as desktop browsers...
again, are we expecting too much...?
http://www.flickr.com/photos/mjryall/3638778588
110. 4
use CSS instead of JavaScript for animations...
are jQuery (and JavaScript) necessary to
provide an experience on mobile devices...?
<script type="text/javascript" src=".../jquery.min.js"><script>
<script type="text/javascript" src=".../scrollto.js"><script>
consider using basic DOM manipulation, or a mobile optimised Javascript library
<script type="text/javascript" src=".../xui.min.js"><script>
the “jQuery Mobile” long before jQuery Mobile...
http://xuijs.com
http://jquerymobile.com
use CSS for animations if available instead of Javascript
.scrollto {
-webkit-transform: translate(540px, -200px);
-moz-transform: translate(540px, -200px);
-o-transform: translate(540px, -200px);
}
...use CSS animations
(where possible) instead
ignored on browsers that don’t support it
111. look ma, no jQuery?
from a time before jQuery...
Twier?
http://www.flickr.com/photos/wordridden/2474879344
112. then again, do you really need javascript?
*none of these services relied on Javascript when they first started...
113. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
4. progressively enhance using JavaScript
and @media queries
5. adapt content (especially images)
appropriately for each device
114. 5
same images used for all devices...
one size rarely fits all...
ul li#biography a span.label {
background: url("../pig.png") repeat-x center bottom;
}
16 Kb
also adapt content used in <img /> tags
we should also adapt images found within the markup...
<img src="butterfly.png"
width="200" height="160" alt="butterfly" />
16 Kb
http://colly.com/
115. 5
images adapted appropriately for each device...
ul li#biography a span.label {
background: url("../pig-small.png") repeat-x center bottom;
}
provide appropriate sized images for various devices
also adapt content used in <img /> tags
6 Kb
many CMS’s such as WordPress provide a means of
filtering HTML before it’s sent to the client
<img src="butterfly-small.png"
width="100" height="80" alt="butterfly" />
be sure to update the width and height aributes accordingly
services such as http://tinysrc.net can automatically resize + compress your images
http://colly.com/
6 Kb
116. we could also rethink the <img />* tag...
one image can have multiple source
files, each for an appropriate context
<img alt="butterfly">
<source src="butterfly-small.png" width="100" height="80" />
<source src="butterfly.png" width="200" height="160" />
<source src="butterfly-large.svg" width="400" height="400"
media="min-device-width:320px" /> image formats, and aspect ratios
could be modified as required
</img>
and possibly even include media queries...
*I’m just dreaming here, this doesn’t currently exist...
124. 6 fonts often not supported on mobile
sprite image not used 6
on mobile devices...
6 images not used on
mobile devices...
only one real issue...
3
2
a single (and compressed!) style sheet
well structured, meaningful
and compressed markup
Good
simple DOM scripting without
4 large Javascript libraries
Could be improved
Needs to be improved
125. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for media queries
is in fact the first @media query...
4. progressively enhance using JavaScript
and @media queries
5. adapt content (especially images)
appropriately for each device
6. compress content where possible,
and avoid sending unnecessary data
126. 6
display:none still loads resources...
don’t expect mobile
bandwidth to be free...
@media (max-device-width:767px), all and (max-width:449px) { ...
.speaker-carousel {
display: none;
}
all of the speaker-carousel images are actually loaded,
even though they are never displayed on mobile devices...
127. images not used on
mobile devices...
367.35 KB
http://2010.dconstruct.org/
@font-face not supported
on most mobile devices...
93.63 KB
128. 6
...avoid sending unnecessary data
@media (max-device-width:767px), all and (max-width:449px) { ...
.speaker-carousel {
display: none;
}
find another way to remove the
unused resources on mobile devices...
132. 1. mobile first
2. use well structured, meaningful markup
3. the absence of support for @media queries
is in fact the first @media query...
4. progressively enhance using JavaScript
and @media queries
5. adapt content (especially images)
appropriately for each device
6. compress content where possible,
and don’t include unnecessary data
