1.
FirefoxOS:
The Web, Mobile
Daniel Appelquist (@torgo)
Open Web Advocate, Telefónica Digital

2.
What a difference 5 years
makes
-Me in 2008 (http://www.slideshare.net/dappelquist/web2-expo-sf2008-
appelquist/)

3.
The Web is Mobile
Image from Brad Frost (http://bradfrostweb.com)

4.
..but
• WebApps still second class citizens on smart
phones
• Great confusion about the difference betwen
Apps and Web
• Consumers being driven towards apps
• In the process, we are losing what the Web
has given us: interoperability, freedom,
openness, choice

5.
(Native) Apps vs. Web
Yawn

6.
(Native) Apps vs. Web
• Web has been a browser based experience
• Web has not had access to device APIs
• Web has not been very good with touch
• Techniques for responsive UX have not been
developed
• JavaScript frameworks have been oriented
towards desktop
...but now the Web is catching up

7.
Apps Remind me of
Something

8.
The Web has Staying
Power
• Built on (open, royalty-free) standards
• International community of implementers
• Open to all content providers, open to all
developers
• Don't like it? Fork it.
• People chose the Web because the Web
gave the people a choice

9.
Why FirefoxOS?
• A phone built by the people who brought you
the Web
• All apps are Web apps (including dialer,
etc...)
• All applications built on top of Firefox engine
(Boot to gecko)
• Everything open source
• Optimized for low-end smart phones
• Open OS

10.
Why Telefónica Digital?
• Easier app development across platforms =
better apps
• Lower cost handsets = more people using
them
• Google/Apple Appstore duopoly = bad for
developers, bad (in the long run) for
innovation
• Bringing a fresh approach = disruptive
• We benefit from openness

11.
Bridging the Gap
• New APIs allow access to accelerometer,
camera, address book, calendar, telephony
(making calls), etc...
• New security model for privileged webapps
• Hosted apps and packaged apps
• Both can be used off-line
• Icons represent webapps to the user
• Curated app store from Mozilla - or roll your
own

12.
Blurring the Lines
• Why should an app on your phone be
different from the Web?
• How can a WebApp dip into your personal
information and use your camera in a secure
way?
• Is a chromeless WebApp still "The Web"?
• Is a packaged WebApp still "The Web"?
• How can I, as a user, tell when I can expect
to use an app off-line?

13.
Everything.me Integration
• Unique search interface for
apps
• "Try before you buy"
approach to discovery
• Integrated into FirefoxOS

14.
Working with Standards
This is the Web. I know this.
W3C: HTML5, WebApps,
Geolocation, Sysapps
Privileged APIs, Packaging,
Improving Appcache,
Touch Events, Push

15.
Challenges
• Security - beyond the browser sandbox
• Protecting user privacy when apps can
access private data
• WebRTC - coming soon
• Platform optimization
• Appcache

16.
Geeksphone Keon
•CPU Qualcomm Snapdragon S1 7225AB 1Ghz.
•UMTS 2100/1900/900 (3G HSPA).
•GSM 850/900/1800/1900 (2G EDGE).
•Screen 3.5" HVGA Multitouch.
•Camera 3 MP.
•4 GB (ROM) and 512 MB (RAM).

17.
Some Resources
BuildingFirefoxOS.com
Building blocks to help you create apps
wiki.mozilla.org/B2G
Info from Mozilla on B2G project
OpenWebDevice.com
Info from Telefónica on the project
lungo.tapquo.com
Lungo JS framework - designed for mobile
FirefoxOS Hack coming up May 31 meetup