forked from codepo8/mozilla-and-the-new-web-challenge
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
executable file
·621 lines (527 loc) · 20.9 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
<!DOCTYPE HTML>
<html lang="en-US">
<!-- <html lang="en-US" class="nonumbers"> -->
<!-- ^ if you want no numbers on the slides add a "nonumbers" class to the HTML element -->
<head>
<title>Mozilla and the new web challenge</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=1274, user-scalable=no">
<link rel="stylesheet" href="themes/mozilla/styles/style.css">
</head>
<body class="list">
<header class="caption">
<h1>Mozilla and the new web challenge</h1>
<p class="footer">{Your name}, {your <a href="http://twitter.com/">@twitter</a> or <a href="mailto:[email protected]">[email protected]</a>}</p>
</header>
<!--
Simply copy the whole block for each slide you want.
Special slides get extra classes. Each slide needs an ID
to allow for bookmarking and target jumping.
Images, videos and SVG objects are automatically centred
when you add a class of "middle"
If you add a "cover" class images are taking over the whole
screen resized to height. Add a "w" class to resize to width.
-->
<div id="cover" class="slide"><div>
<section>
<header>
<h2>Mozilla and the new web challenge</h2>
</header>
<img src="pictures/introicons.png" class="middle" alt="Icons of B2G, Firefox OS and Mozilla Apps">
<footer class="byline">{Firstname}, {Lastname}, {Conference}, {Location}, {date}</footer>
</section>
</div></div>
<div id="intro" class="slide"><div>
<section>
<header>
<h2>Who am I?</h2>
</header>
<!--
<img src="pictures/welcome.jpg" class="right" alt="Welcome mat">
^ add your photo if wanted - 400px wide works best
-->
<ul>
<li>{name}</li>
<li>{title}</li>
<li>{<a href="http://twitter.com/">@twitter</a>}</li>
</ul>
<footer class="notes">
Introduce yourself, who you are and why you are the person to give that talk
</footer>
</section>
</div></div>
<div id="agenda" class="slide"><div>
<section>
<header>
<h2>Introduction</h2>
</header>
<img src="pictures/welcome.jpg" class="right" alt="Welcome mat">
<ul>
<li>What has Mozilla done?</li>
<li>What do we do now?</li>
<li>A new challenge</li>
<li>Firefox for developers</li>
<li>Firefox OS / Apps for the web</li>
</ul>
<small class="credits">
<a href="http://www.flickr.com/photos/mjparnell/435465575/">Photo by the McClouds</a>
</small>
<footer class="notes">
Setting the stage - explain what you are going to cover. This was mainly added for
audiences who don't speak English as their first language.
</footer>
</section>
</div></div>
<div id="whatmozilladid" class="slide"><div>
<section>
<header>
<h2>What Mozilla did…</h2>
</header>
<img src="pictures/ie6.png" class="middle" alt="About Internet Explorer 6 info">
<footer class="notes">
Explain that without Mozilla, Internet Explorer would be the dominant browser,
that we are a not-for-profit organisation to keep the web open and that without
us the web would be a corporate-only environment.
</footer>
</section>
</div></div>
<div id="whatmozilladid2" class="slide"><div>
<section>
<header>
<h2>What Mozilla did…</h2>
</header>
<img src="pictures/browserlympics.png" class="middle" alt="Browser Logos">
<footer class="notes">
Firefox (and Opera) also paved the way for other browsers both to be released
open source and support web standards. Even IE now does a lot to support and
also promote web standards.
</footer>
</section>
</div></div>
<div id="morethanfirefox" class="slide"><div>
<section>
<header>
<h2>Ongoing work…</h2>
</header>
<img src="pictures/mozillamore.png" class="middle" alt="Mozilla is more than Firefox">
<footer class="notes">
Mozilla is much more than Firefox though. We are a not-for-profit organisation to
promote the open web. This means we educate people on how to publish content and
we protect people's privacy and identity and choice on the web.
</footer>
</section>
</div></div>
<div id="webmaker" class="slide"><div>
<section>
<header>
<h2>A generation of webmakers</h2>
</header>
<img src="pictures/webmaker.jpg" class="middle" alt="Mozilla Webmaker">
<p class="demourl">
<a href="https://webmaker.org">https://webmaker.org</a>
</p>
<footer class="notes">
Mozilla Webmaker is an ongoing project to turn pure consumers of the web
into makers. We teach basic web editing skills, how to publish and mix
video with online content and basic ways to keep safe and have a good
time on the web.
</footer>
</section>
</div></div>
<div id="thimble" class="slide"><div>
<section>
<header>
<h2>Learning by doing!</h2>
</header>
<img src="pictures/thimble.jpg" class="middle" alt="Mozilla Thimble">
<p class="demourl">
<a href="https://thimble.webmaker.org/en-US/projects/map/edit">https://thimble.webmaker.org/en-US/projects/map/edit</a>
</p>
<footer class="notes">
Mozilla Thimble is a very simple and interactive way to learn basic HTML. An editor on the
right hand side of the screen lets you write things and the results are shown immediately on
the left. You can also choose from already existing projects and write in them. The editor
shows you when you make an error and links it to the documentation on the developer network.
You can choose from various challenges to become better and better in editing HTML.
</footer>
</section>
</div></div>
<div id="popcorn" class="slide"><div>
<section>
<header>
<h2>Lights, Camera, interaction!</h2>
</header>
<img src="pictures/popcorn.jpg" class="middle" alt="Mozilla popcorn">
<p class="demourl">
<a href="https://mozillapopcorn.org">http://mozillapopcorn.org</a>
</p>
<footer class="notes">
Mozilla Popcorn is a simple way to create interactive web experiences from video and
audio materials. You have an editor to overlay web content over videos and interact
with parts of the page.
</footer>
</section>
</div></div>
<div id="persona" class="slide"><div>
<section>
<header>
<h2>Persona - own your identity!</h2>
</header>
<img src="pictures/persona.jpg" height="350" class="middle" alt="Mozilla Thimble">
<p class="demourl">
<a href="http://www.mozilla.org/en-US/persona/">http://www.mozilla.org/en-US/persona/</a>
</p>
<footer class="notes">
Mozilla Persona is a simple way to log into web apps and sites. Instead of having
to create a username and password for each product you log in to Persona allows you
to identify yourself with one of your verified e-mails. That way you don't have to
have thousands of profiles online and you only give sites the information you want
instead of all your data.
</footer>
</section>
</div></div>
<div id="a-new-challenge" class="slide cover w"><div>
<section>
<header>
<h2>A new challenge</h2>
</header>
<img src="pictures/responsive.jpg" class="middle" alt="Responsive Design">
<small class="credits"><a href="http://www.flickr.com/photos/indyplanets/5693612984/">Photo by Jason Weaver</a></small>
<footer class="notes">
One very obvious change in the last years was that the web became much more mobile.
Instead of desktop machines we use laptops, smart phones and tablets and all of
these devices get more powerful by the month. They all come with different resolutions
and connectivity issues, though and Mozilla is happy to take on the challenge of
moving the open web from immobile machines to on-the-go computing.
</footer>
</section>
</div></div>
<div id="brokenpromise" class="slide"><div>
<section>
<header>
<h2>Broken promises</h2>
</header>
<img src="pictures/html5promise.png" class="middle" alt="Smartphone equals HTML5">
<footer class="notes">
When a certain company very loudly proclaimed that the desktop is dead
and smartphones are the future and that HTML5 is the new standard to
power smartphones we were very happy and interested indeed. Finally
web standards got a platform that is on the bleeding edge and very
beautiful and we all were ready to chip in to make this an open
experience that empowers everyone to build for these new devices.
</footer>
</section>
</div></div>
<div id="business-realities" class="slide cover w"><div>
<section>
<header>
<h2>Business realities</h2>
</header>
<img src="pictures/apps.jpg" class="middle" alt="Apps">
<small class="credits">
<a href="http://www.flickr.com/photos/msvg/5385759365/">Photo by Michael Gil</a>
</small>
<footer class="notes">
However, when native apps took off a lot of companies realised that there
is money to be made by not keeping things open. Apps can do more than
HTML5 can because the OS and hardware providers grant them more access and
control the experience. If you control the software and the hardware, you
can build great, but very bespoke products. If you allow for open technologies
to be used, you lose control and you make less money as a hardware provider.
As a developer, you shouldn't have to go that route.
</footer>
</section>
</div></div>
<div id="firefoxandroid" class="slide"><div>
<section>
<header>
<h2>Firefox to the rescue?</h2>
</header>
<img src="pictures/firefoxandroid.jpg" class="middle" alt="Firefox for Android">
<footer class="notes">
Firefox is now available on Android and does quite a few things
more than the Android stock browser (not Chrome) does. You can
get it on the Android market and we welcome any feedback you
can give us to make it the best experience possible.
</footer>
</section>
</div></div>
<div id="firefox-for-developers" class="slide cover w"><div>
<section>
<header>
<h2>Firefox for developers</h2>
</header>
<img src="pictures/hackday.jpg" class="middle" alt="Developers at a hack day">
<small class="credits">
<a href="http://www.flickr.com/photos/osde-info/563699963/">Photo by Clive Darra</a>
</small>
<footer class="notes">
Firefox lately has gotten a lot of new features for developers far beyond
what the Firebug extension gave you. Some of them are very handy to have
when building for mobile devices.
</footer>
</section>
</div></div>
<div id="responsiveview" class="slide"><div>
<section>
<header>
<h2>Responsive view</h2>
</header>
<img src="pictures/responsivemenu.png" class="middle" alt="Responsive view in Firefox">
<p class="demourl">
<a href="http://paulrouget.com/e/devtoolsupdate/">Demo</a> |
<a href="http://www.youtube.com/watch?v=t07cLJhJkjQ">Screencast</a>
</p>
<footer class="notes">
A new feature in Firefox is the responsive view which makes it easy to
simulate different mobile device resolutions. This makes it much easier
to test your designs.
</footer>
</section>
</div></div>
<div id="responsivedemo" class="slide"><div>
<section>
<header>
<h2>Responsive view</h2>
</header>
<img src="pictures/responsive-demo.png" class="middle" alt="Two views of the same page">
<footer class="notes">
The responsive view in Firefox makes it easy to test what your app looks like
in different resolutions and when you switch from landscape to portrait mode.
Instead of resizing the window you resize the document in the browser. It comes
with lots of presets of the sizes of common phones and tablets and you still
have access to all the buttons and tabs of your browser.
</footer>
</section>
</div></div>
<div id="remotedebugging" class="slide"><div>
<section>
<header>
<h2>Remote debugging</h2>
</header>
<img src="pictures/remotedebug.jpg" class="middle" alt="Remote debugging">
<p class="demourl">
<a href="https://hacks.mozilla.org/2012/08/remote-debugging-on-firefox-for-android/">https://hacks.mozilla.org/2012/08/remote-debugging-on-firefox-for-android/</a>
</p>
<footer class="notes">
The latest Firefox now allows for remote debugging, which means you
can develop on your desktop and see the results on your phone instead
of having to send code, restart the phone or reload the page and all
that pain. With remote debugging you can see what is going on in the
code of your HTML5 app on your desktop while testing it in the real
environment.
</footer>
</section>
</div></div>
<div id="hardware-lockout" class="slide cover w"><div>
<section>
<header>
<h2>Hardware lockout</h2>
</header>
<img src="pictures/lockout.jpg" class="middle" alt="Very obvious road block">
<small class="credits">
<a href="http://www.flickr.com/photos/old_sarge/100926333/">Photo by Doug Geisler</a>
</small>
<footer class="notes">
The most frustrating part about this is that phone and operating
system providers lock out browsers and JavaScript. The fun parts
to use in a smartphone are the camera, the sensors and to use it
to send messages to your friends and call people. To do this,
however you'll need to write native code. Browsers, in general
are locked out. This is not fair when you claim at the same
time that HTML5 is the platform to bring a great future.
</footer>
</section>
</div></div>
<div id="webapis" class="slide"><div>
<section>
<header>
<h2>Web API work</h2>
</header>
<img src="pictures/hardware-blowup.png" class="middle" alt="All the hardware in a mobile with info to the corresponding Web API spec and implementation status">
<p class="demourl">
<a href="http://arewemobileyet.com">http://arewemobileyet.com</a>
</p>
<footer class="notes">
At arewemobileyet.com we have a live view of how far down the line
we are in defining and implementing open APIs that will give web
developers access to this hardware. These are standards that can
be used by other browser vendors and are implemented in Firefox.
As you can see we are very far down the line, the only thing
missing still is USB and NFC connectivity, other than that all
that is in your phone can be accessed by JavaScript.
</footer>
</section>
</div></div>
<div id="openwebdevice" class="slide"><div>
<section>
<header>
<h2>Open Web Device</h2>
</header>
<img src="pictures/openwebdevice.jpg" class="middle" alt="Openwebdevice web site">
<p class="demourl">
<a href="http://openwebdevice.com">http://openwebdevice.com</a>
</p>
<footer class="notes">
The open web device is an initiative by Telefonica to bring the
web to people who can not afford a high-market smartphone and
still should get the chance to be online on the go. These
devices will go on sale in Brazil as the first market in
early 2013.
</footer>
</section>
</div></div>
<div id="firefoxos" class="slide cover w"><div>
<section>
<header>
<h2>Powered by Firefox OS</h2>
</header>
<img src="pictures/otoro.jpg" class="middle" alt="Firefox OS running on a phone">
<footer class="notes">
The open web device is powered by Firefox OS a new operating
system for mobiles developed by Mozilla.
</footer>
</section>
</div></div>
<div class="slide cover w" id="firefox-os-components-detail"><div>
<section>
<img src="pictures/componentsflame.jpg" class="middle" alt="Gonk, Gecko and Gaia">
<small class="credits">
<a href="http://www.flickr.com/photos/alesadam/3869366195/">Photo by Alesa Dam</a>
</small>
<footer class="notes">
Firefox OS is build with three components:
Gonk is the Linux layer talking to the hardware (the same Android uses)
Gecko is the rendering and JavaScript engine (same as Firefox) and
Gaia is the interface - everything you see - written in HTML5
</footer>
</section>
</div></div>
<div id="gaia-concepts" class="slide cover w"><div>
<section>
<header>
<h2>Interface flexibility</h2>
</header>
<img src="pictures/uxconcept.jpg" class="middle" alt="Gaia concepts">
<footer class="notes">
The whole interface of Firefox OS is written in web technologies. This
means phone or phone service providers can complete change the look,
feel and functionality of the phone interface itself. This is something
completely new and can lead to a lot of great phone innovation for
special needs. Consider a kid's phone with three simple buttons or
company phones that only have the apps you need for your job and nothing
else.
</footer>
</section>
</div></div>
<div id="how-to-play-with-firefox-os" class="slide"><div>
<section>
<header>
<h2>How to play with Firefox OS…</h2>
</header>
<ul>
<li>Run GAIA in Firefox Nightly (simplest way)</li>
<li>Use a desktop simulator (OSX / Linux)</li>
<li>Build your own device (very hard indeed)</li>
</ul>
<p class="demourl">
<a href="https://wiki.mozilla.org/Gaia/Hacking">https://wiki.mozilla.org/Gaia/Hacking</a>
</p>
<footer class="notes">
You can run Firefox OS on your own computer inside Firefox Nightly
or with Desktop simulators.
The easiest is to run it in the browser and build your apps for it
with the environment you are familiar with.
You can put it on your own phones but the process is not easy (yet)
The idea of Firefox OS is to bring new, affordable web-enabled phones
to people and not to replace Android/iOS.
</footer>
</section>
</div></div>
<div id="more-info" class="slide"><div>
<section>
<header>
<h2>Where to find more info…</h2>
</header>
<ul class="longlist">
<li><strong>Follow</strong> <a href="http://twitter.com/Boot2Gecko">@Boot2Gecko</a> and <a href="http://twitter.com/mozhacks">@mozhacks</a> on Twitter</li>
<li><strong>Join platform mailing list</strong>: <a href="http://groups.google.com/group/mozilla.dev.platform">http://groups.google.com/group/mozilla.dev.platform</a></li>
<li><strong>Join in on IRC</strong>: irc.mozilla.org channel #B2G</li>
<li><strong>B2G Repo</strong>: <a href="https://github.com/mozilla-b2g/B2G">https://github.com/mozilla-b2g/B2G</a></li>
<li><strong>B2G Architecture</strong>: <a href="https://wiki.mozilla.org/B2G/Architecture">https://wiki.mozilla.org/B2G/Architecture</a></li>
<li><strong>Gaia Repo</strong>: <a href="https://github.com/mozilla-b2g/gaia">https://github.com/mozilla-b2g/gaia</a></li>
<li><strong>Developer Docs</strong>: <a href="https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko">https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko</a></li>
<li><strong>Web API Docs</strong>: <a href="https://wiki.mozilla.org/WebAPI">https://wiki.mozilla.org/WebAPI</a></li>
</ul>
<footer class="notes">
There are many ways to keep up to date with Firefox OS/Boot2Gecko.
Here are the most important ones.
</footer>
</section>
</div></div>
<div id="marketplace" class="slide"><div>
<section>
<header>
<h2>Web APPS on the phone</h2>
</header>
<img src="pictures/marketplace.jpg" class="middle" alt="Mozilla Marketplace">
<p class="demourl">
<a href="https://marketplace.mozilla.org/">https://marketplace.mozilla.org/</a>
</p>
<footer class="notes">
Of course a phone without apps is not going to be very interesting to audiences
out there. This is why Mozilla has its own app store that contains apps that can
run on a Firefox OS phone but also in the browser.
These apps are built with HTML5, CSS and JavaScript and all you need to give us
to be part of it is a manifest file.
</footer>
</section>
</div></div>
<div id="what-can-you-do" class="slide"><div>
<section>
<header>
<h2>What can you do?</h2>
</header>
<ul>
<li><strong>Code</strong> - Write apps, contribute to Gaia, contribute to B2G</li>
<li><strong>Use</strong> - Use Marketplace, Use the Web API, Use B2G</li>
<li><strong>Feedback</strong> - Give your input on APIs, request features, test and log bugs</li>
</ul>
<footer class="notes">
Firefox OS needs developers to help it out. You can contribute in many ways.
The easiest is to play with it and give us feedback as to what you'd want out
of it. Of course we love people to code with us, too, and we very much need
people to build apps on B2G.
</footer>
</section>
</div></div>
<div id="thanks" class="slide"><div>
<section>
<header>
<h2>Thanks</h2>
</header>
<img src="pictures/redpanda.jpg" class="right" alt="Red panda (Firefox)">
<ul>
<li>{name}</li>
<li>{title}</li>
<li>{<a href="http://twitter.com/">@twitter</a>}</li>
<li><strong>Slides</strong>: {slideurl}</li>
</ul>
<small class="credits">
<a href="http://www.flickr.com/photos/yortw/5798336827/">Photo by Yortw</a>
</small>
<footer class="notes">
Say thanks, add a URL where to get the slides, and where people in the audience
can contact you.
</footer>
</section>
</div></div>
<!--
To hide progress bar from entire presentation
just remove “progress” element.
-->
<div class="progress"><div></div></div>
<script src="scripts/script.js"></script>
<!-- Copyright © 2010–2012 Vadim Makeev — pepelsbey.net -->
</body>
</html>