This document contains a presentation about developing multiplatform mobile applications. It discusses the benefits of using HTML5 for cross-platform development, including code sharing across platforms. However, it also notes some disadvantages of HTML5 like underestimating challenges, varying performance across browsers and devices, and lack of native UI capabilities. The presentation explores options for developing native apps, web apps, and hybrid apps that combine web technologies with native platforms. It emphasizes the importance of considering multiple factors like distribution channels, development approaches, and each platform's varying support for HTML5 features when choosing a development strategy.
1. Nov, 7th, 2012
San Francisco, USA Max Firtman @firt
MULTIPLATFORM,
PROMISES AND
HTML5
Wednesday, November 7, 12
2. Watch the video with slide
synchronization on InfoQ.com!
http://www.infoq.com/presentations
/Mobile-Multiplatform-HTML5
InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
3. Presented at QCon San Francisco
www.qconsf.com
Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
17. Cross Platform mobile
10.30 Maximiliano Firtman
Multiplatform, promises and HTML5
11.40 James Pearce
Building social apps for all mobile platforms
13.30 Pete LePage
The Mobile Web Developer’s Tool belt
14.40 Christophe Coenraets
Cross-Platform Mobile Apps with PhoneGap
16.00 Robert Shilston
Developing the FT web app
Wednesday, November 7, 12
106. second class developers
‣ vague, non-existent or outdated info
‣ new features discovered by third-parties
Wednesday, November 7, 12
107. second class developers
‣ vague, non-existent or outdated info
‣ new features discovered by third-parties
‣ lack of samples
Wednesday, November 7, 12
108. second class developers
‣ vague, non-existent or outdated info
‣ new features discovered by third-parties
‣ lack of samples
‣ no developer tools on some platforms
Wednesday, November 7, 12
109. mobile
html5
is slow
Picture from Simon Howden freedigitalphotos.net!
Wednesday, November 7, 12
111. performance
‣ do we need jQuery?
Wednesday, November 7, 12
112. performance
‣ do we need jQuery?
‣ performance best practices
Wednesday, November 7, 12
113. performance
‣ do we need jQuery?
‣ performance best practices
‣ JIT compilers
Wednesday, November 7, 12
114. performance
‣ do we need jQuery?
‣ performance best practices
‣ JIT compilers
‣ hardware acceleration
Wednesday, November 7, 12
115. battery consumption
WW 2012 – Session: Mobile Web Performance April 16–20, 2012, Lyon, Fra
50
45
40
Energy (Joules)
35
30
25
20
15
10
5
0
live.com
microsoft
weather
picasa
baidu
facebook
imdb
youtube
go.com
wall st. journal
blogger
3G setup
nytimes
tumblr
wikipedia
apple
ebay
amazon
gmail
yahoo
cnn
bbc
engadget
natgeo
wordpress
aol
Figure 6: Energy consumption of top websites
Web site Comment % Battery Traffic (bytes)
life Upload Download
The resulting numbers are shown in Figure 6. Note that the e
m.gmail.com inbox 0.41 9050 12048 bars are so small that they are barely visible.
m.picasa.com
m.aol.com Who Killed My Battery ~ mobilexweb.com/go/battery
user albums
portal home
0.43
0.59
8223
11927
15475
37085
The left most column in Figure 6 shows the energy neede
set up a 3G connection and download a few bytes without any
m.amazon.com product page 0.48 9523 26838
ditional processing. Since all navigation requests must setup a
mobile.nytimes.com US home page 0.53 15386 66336
touch.facebook.com facebook wall 0.65 30214 81040 connection we treat this measurement as a baseline where th
mw.weather.com Stanford weather 0.62 38253 134531 teresting differences between web sites are above this line.
apple.com home page
Wednesday, November 7, 12 1.41 86888 716835 Figure 6 is generated from the mobile versions of the
116. battery consumption
Apple has no mobile website
Amazon consumes 17% energy
in a non used JS
jQuery.js ~ 4 joules (0,02%)
~5000 jQuery parsings per charge
Who Killed My Battery ~ mobilexweb.com/go/battery
Wednesday, November 7, 12
135. conclusions
‣ Multiplatform is a key for success
Wednesday, November 7, 12
136. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
Wednesday, November 7, 12
137. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
Wednesday, November 7, 12
138. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
‣ write once, deploy anywhere is... a promise
Wednesday, November 7, 12
139. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
‣ write once, deploy anywhere is... a promise
‣ However, it’s better than 10 SDKs or than create only
elite users
Wednesday, November 7, 12
140. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
‣ write once, deploy anywhere is... a promise
‣ However, it’s better than 10 SDKs or than create only
elite users
‣ On some situations you will need native SDKs
Wednesday, November 7, 12
141. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
‣ write once, deploy anywhere is... a promise
‣ However, it’s better than 10 SDKs or than create only
elite users
‣ On some situations you will need native SDKs
‣ Some problems will be gone in the future
Wednesday, November 7, 12
142. conclusions
‣ Multiplatform is a key for success
‣ HTML5 is good for cross platform on some situations
‣ HTML5 is not a heaven
‣ write once, deploy anywhere is... a promise
‣ However, it’s better than 10 SDKs or than create only
elite users
‣ On some situations you will need native SDKs
‣ Some problems will be gone in the future
‣ Use the best technology for every situation
Wednesday, November 7, 12
150. you can reach a good
thanks!
experience
firt.mobi
firtman@gmail.com
twitter: @firt
www.mobilexweb.com
Pictures)from)freedigitalphotos.net)
Wednesday, November 7, 12