FirefoxOS is an open source mobile operating system built on web technologies. It allows all apps to be built as web apps using HTML, CSS, and JavaScript, and have access to device APIs. This bridges the gap between web apps and native apps. FirefoxOS aims to disrupt the current app store duopolies by bringing a fresh approach based on open web standards. All development is done through open source communities to further the capabilities of the open web. Telefonica Digital is working with Mozilla to develop and promote FirefoxOS to allow easier cross-platform app development and access to lower cost handsets.
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
● Web apps are still second class citizens on
smart phones
● Great confusion about the difference
between apps and Web
● Consumers being driven towards apps
● In the process, we are losing what the Web
has given us: interoperability, freedom,
openness, choice
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
8. App Fatigue is Setting In
● How many apps do you use regularly?
Where is your apps graveyard?
● Do apps really make sense for news?
Really?
● Social content consumption and sharing
zings you between apps and Web
● Door-slams
● What value is an app store bringing between
users and services?
● App stores remind me of pre-Web thinking
9. ...but the Web has something
to learn from Apps
● People like apps
● Emotive feeling of ownership
● Having an install step conveys meaning:
additional privileges, expectations of use
● Offline operation
● Access to more APIs = richer experience
● Touch UI is different from mouse-driven UI
10. 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 choose the Web because the Web
gives people a choice
● Solid architectural foundation
13. What could a Web Future
Look Like?
● Web apps can be used in the browser or installed
● Visit a Web page, it might ask you "do you want me to
install as an app?"
● Installed Web apps can pop up in a chromeless view
and can access privileged APIs
● Plethora of (Web-based) app stores available, or buy
apps direct from publisher
● Web apps that invoke telephony functions
● Privacy-enabled
● Apps built with responsive design across device types
and form factors
14. Firefox OS
● A phone built by the people who
brought you the Web
● All apps are Web apps (including
dialer, camera, etc...)
● All applications built on top of Firefox
engine (Boot to gecko)
● Everything open source - open for
tinkering
● Yes, a Marketplace (for "privileged"
apps)
● Optimized for low-end smart phones
● Geeksphone keon / peak developer
preview phones
● ZTE, Alcatel phones released
15.
16. 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
17. 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 tell when I can expect to use an
app off-line?
19. Some Challenges Still...
● Security - beyond the browser sandbox
● Protecting user privacy when apps can
access private data - what is the right
balance?
● WebRTC - in Beta
● Platform optimization
● Appcache / offline operation
20. 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
● "Open Innovation"
21. Working with Standards
This is the Web. I know this.
W3C: HTML5, WebApps,
Geolocation, Sysapps, WebRTC,
Community Groups
Privileged APIs (e.g. Telephony),
Packaging, Improving Appcache,
Touch Events, Push
22. W3C Responsive Images
Community Group
A group working on a solution for images in
responsive design
http://www.w3.org/community/respimg/
<picture alt="Description of image subject.">
<source srcset="small.jpg 1x, small-highres.jpg 2x">
<source media="(min-width: 18em)" srcset="med.jpg 1x, med-highres.jpg 2x"> <source
media="(min-width: 45em)" srcset="large.jpg 1x, large-highres.jpg 2x"> <img src="
small.jpg" alt="Description of image subject."> </picture>
A proposed syntax and a polyfill ("picturefill") on
GitHub
23. W3C Extensible Web Effort
● New idea for extending the capabilities of the
Web
● Community Group here:
○ http://www.w3.org/community/nextweb/
● Manifesto here:
○ http://extensiblewebmanifesto.org