I am spending this week explaining lots of press folk what the Geeksphone is about. I just got excited like a puppy on sugar rush about unpacking mine, after waiting for a long time to get it internally at Mozilla. See the unpacking photo set on Flickr

Posting this on Twitter and Facebook caused quite a stir and many people who bought a Geeksphone wondered about their delivery times. Here’s what I know about this: nothing. I also don’t have access to phones to give out or expedite delivery for you – nobody outside of Geeksphone or inside Mozilla can, so please don’t ask for any of this as it is impossible for us to help you.

I think it is very important to repeat what the Geeksphone Firefox OS preview device project means and stands for. So here it is, in a very clear fashion: the Geeksphone Firefox OS developer preview devices are developer tools for Firefox OS. They are not:

• Firefox OS phones for day to day use
• Swag to give out for free as prizes on conferences (so don’t ask)
• A collector’s item to buy and put on a shelf

Firefox OS is meant to fill a gap in the mobile space and bring HTML5 capable devices in a very affordable fashion to markets that can not get handsets with great web capabilities. In other words, it replaces feature phones, not your high end Android or iPhone.

That’s why we found ourselves in a pickle: how do developers test on a platform that is not sold in their locale as it would be pointless to add to a saturated market with a lower-spec phone? The answer is developer tools like the Firefox OS simulator and affordable testing devices where you can really see how responsive the hardware with the OS is. And these are the Geeksphone Firefox OS preview devices.

Having a Geeksphone Firefox OS preview device means you should be working on an app, that is what we need developers to do. We need the marketplace to have a lot of good apps on launch of the phones to the end users. All you need to do is to build an HTML5 app (that also can be converted to native code with PhoneGap) – you can develop that one to 80% in the browser. To get all the Firefox specific goodies, you’d need a phone like the current one Geeksphone provides.

So while it is very exciting to see people go nuts over the phones, I think it is very important to remember that these are tools to build and test apps and not phones to have instead of the phone that our partners will release in the target markets. These will be very different but share the same hardware specs.
Consider the Geeksphone Firefox OS preview device a Nightly build of a browser. You are helping the browser to test out future features for normal end users but you shouldn’t be surprised about quirks and errors. On the contrary – we want you to find them and tell us what is broken, that’s why there are preview and beta versions of browsers.

I am terribly excited about being able to give real hardware to people who work on exciting apps that will make a massive difference for people who now only can play snake and send SMS on their phones. You could be part of the new wave of mobile internet entertainmment and access in countries that hunger for a better experience. That’s what you’d need a Geeksphone Firefox OS preview device for. If all you want to do is to play with a phone, drop by in any Mozilla location or any of our events.

Right now Firefox OS needs you to build stuff for the web, and if you do that already, the device can give you the final testing platform you need. You won’t need one for most smaller apps though, so don’t feel left out as there are not that many available and it may take some time for yours to arrive.

That doesn’t mean that in the future there might not be devices sold by Geeksphone that are targetted at end-users. It simply means that the Geeksphone Firefox OS preview device is what it is – a preview device for developers.

The lovely people of Devs love bacon today released the video of my talk Helping or Hurting and I am blown away by the quality of it. Really TED style stuff.

Christian Heilmann – Helping or hurting? from BACON: things developers love on Vimeo.

I had given the talk slightly more focused before at the jQuery Europe conference (notes are available here) and thought it is important to bring the message out as a video. We are right now hurting the web of the very near future by building tools that seemingly make developers more effective but at the same time make them dependent on abstractions. And if we don’t make these abstractions not use the newest and most performance optimised technologies under the hood we are just adding more and more cruft to the web.

There is nothing more frustrating than things going wrong without you knowing what happened. Things breaking with a very obvious reason are not as bad. Say you drop your phone and you see the display smashed – there is no question why the touch interface doesn’t work any more. But when nothing happens and everything should be OK, we get very cross very fast.

This is why code that isn’t defensive in testing for what it needs before accessing it annoys me. Worse even, when code just assumes everything is OK and doesn’t have an error clause that gives a fallback or at least tells me what is going on.

This is where HTML5 multimedia on a plain markup level is terrible. It is not easy to play sound or video on computers, not a trivial task indeed. However, I would still expect to get a fallback when things go wrong other than a grey box that does exactly nothing.

When I add an image to a document and specify an alternative text this text gets displayed when the image can’t be loaded (at least in Firefox). I can also add an “error” event handler to the image and it will get fired when the image fails to load. You can try it in this Demo on JSBin

  <img src="meh.jpg" alt="cute kitten photo">

var img = document.querySelector('img');
img.addEventListener('error', function(ev) {
  if (this.naturalWidth === 0 && 
      this.naturalHeight === 0) {
    console.log('Image ' + this.src + ' not loaded');
  }
}, false);

Not so with multimedia.

Say you add a video into the page and the browser can not play it because it can not be loaded or the browser does not support its type. All you get is a grey box that does not do anything. You don’t even get a “save as” link or anything like it. And to add to the annoyance, no error handler gets fired on the video element – although the video or audio element very much has one to use. What’s going on?

What if you offer a fallback?

Say we do the right thing and offer a sensible fallback for the video should it fail to load or the browser being incapable of playing video:

<video controls>
  <source src="dynamicsearch.mp4" type="video/mp4"></source>
  <a href="dynamicsearch.mp4">
    <img src="dynamicsearch.jpg" 
         alt="Dynamic app search in Firefox OS">
  </a>
  <p>Click image to play a video demo of 
     dynamic app search</p>
</video>

If your browser doesn’t support the video element at all you get a screenshot of the video and an explanation what to do – you can still download and watch the movie in any mediaplayer on your computer. This is great. It is also a beneficial thing to do as for example links on Facebook would get a thumbnail of the image next to them.

When the browser supports the video element but doesn’t support MP4 you are out of luck though. You get the broken grey box and not the fallback content. Wouldn’t it be great if the browser showed the fallback when the video can not be played? Not according to the standard. It is up to the implementer to develop a fallback for this. And here’s how that is done: you need to assign an error handler to the last source element in the video element. If the browser doesn’t find any playable source, this allows you to replace the video with its fallback content.

<video controls>
  <source src="dynamicsearch.mp4" type="video/mp4"></source>
  <a href="dynamicsearch.mp4">
    <img src="dynamicsearch.jpg" 
         alt="Dynamic app search in Firefox OS">
  </a>
  <p>Click image to play a video demo of 
     dynamic app search</p>
</video>

var v = document.querySelector('video'),
    sources = v.querySelectorAll('source'),
    lastsource = sources[sources.length-1];
lastsource.addEventListener('error', function(ev) {
  var d = document.createElement('div');
  d.innerHTML = v.innerHTML;
  v.parentNode.replaceChild(d, v);
}, false);

Not the most intuitive, but it works. Wouldn’t it be easier if the video element showed the fallback content when it can’t play a video or at least fire an error handler saying “no valid codec found”?

• Video element standard document

Today I gave a talk at the State of the browser 3 event in London, England. The Slides are here, a screencast (with bad audio) is on YouTube and here are the notes.

Abstract:
When the web was defined as an idea it was based on the principle of independence of hardware, global location, prosperity or ability. This changed drastically when the mobile web came around and we got sucked into a world of software dependent on certain hardware and global location. HTML5 and the mobile web based on open technologies became something that needed conversion to native code to access the new hardware people use. This is against the main principle of the web and means we duplicate efforts all over the place. In this talk Chris Heilmann shows how Mozilla is battling this trend and how brushing up your HTML5 solutions allows you to reach millions of new users forgotten by native technology but nevertheless eager to be online.

When I was a kid, I had an uncle in America and he sent us comic books. One of the things advertised in these comic books were sea monkeys – awesome pets that are a whole society and play with another and anyone can look after. Turns out these things are just Brine Shrimp and don’t look at all like that. Actually they are really ugly and boring.

This is what I feel a bit like when we look at what happened to HTML5 on mobile devices. When the iPhone came out Steve Jobs announced that there is no need for an SDK and that Safari with web technologies is more than enough to deliver great experiences. When I tried though what worked I quickly found myself hindered in a lot of respects and the attitude of Apple towards web technologies on the phone vs. native apps changed drastically and very quickly.

And somehow this lead to a terrible experience of the web on mobile devices. This is especially annoying when the sites have been “optimised for mobile viewing” and still fail to deliver anything useful. Another big thing that is happening right now is web sites redirecting you to download a native app instead. This is not what I want when I am on the go on a limited connection and simply look something up. Brad Frost collects a lot of terrible user experiences on mobile at wtfmobileweb.com.

What happened? When did we give up on the idea of nice and responsive web products that use what is available to them? It can not be about the tools we have. Browsers have amazing developer tools built into them these days – all of them, really. Using these tools we have very fine-grained control over what happens in a browser.

For example in this shot you can see the difference using requestAnimationFrame instead of setTimeout makes.

Let’s not forget how far browsers have come in the recent years.
Browsers these days are nothing more but awesome. Whatever you can complain about you can file as a bug and if it is a real issue it can be fixed within weeks. Every few weeks there are browser updates and security fixed happen over night. All of them render HTML the same way.

And yet the web is full of sites that are plain broken on different devices. Simple things like forgetting to define a viewport size can make an interface unusable or really annoying to get around. Why?

I think as a community we get far too excited about products. The whole mobile space thrives on hardware sales. So instead of building stable and good solutions we continuously want the newest and coolest and support it exclusively. I remember when Retina displays came out and many voices in the web design community called out that we need to fundamentally change what we are doing now. This is fleeting, and in many cases we aren’t even allowed as web developers to access the new technology that makes a product what it is. You can look very silly, very quickly when chasing the shiny.

One big part of this was people getting too excited about the iPhone and Android as the only platforms to support prematurely calling WebKit the only browser engine worthy of our efforts (effectively repeating the same mistakes we did in the end 90ies which gave us all the fun “IE only” web products). With the announcement of the Blink rendering engine powering Opera and Chrome from here on forward the “webkit only” argument went down the drain. Good riddance.

How about we give web technologies a new platform on mobile devices? And how about not trying to compete with iOS and Android on high end devices while doing so? This is what Firefox OS is about – it brings the web to people who have mobiles as their main interaction with the web – based on web technologies and without the lock-out.

Here are the main differences that FirefoxOS bring in comparison to Android or iOS:

• Targeted at new, emerging markets
• Very affordable hardware
• No credit card needed – client billing
• Web technologies through and through
• 18 mobile partners, 4 hardware partners

Firefox OS was created to bring users of feature phones into the web-enabled mobile world. It is meant to cater to the markets not covered by iOS and Android. Yes, you can buy cheap Androids world-wide but the version of Android they support doesn’t have an out-of-the-box browser that allows you to do interesting things on the web. Much like Firefox and Opera for Android allow more users world-wide to have a great web experience without having the latest hardware, Firefox OS goes further. Its main goal is to bring millions of new users to the web on their mobile devices without getting a second-grade experience.

One huge differentiator of Firefox OS is that instead of solely relying on a market place to list apps, apps can be found by entering what you are looking for. This means that if you enter for example a band name like “u2”, you get music apps offered to you. For a movie title it is apps that have to do with films. These are both apps listed in the market place and web-optimised sites. Say you looked for a band, you could click on the songkick icon and get the mobile interface of songkick. You can try the app before you download it and see if you like it. If you want to install it you just tap it for longer and Firefox OS will install the app – including offline functionality, full-screen interface and the extra hardware access Firefox OS offers. This means your mobile interfaces become the ad for your application and users don’t need to download and install a huge app just to try it out. Everybody wins. We made App discovery as easy as surfing the web.

What makes your HTML5 site and app for Firefox OS is the manifest file:

{
  "name": "My App",
  "description": "My elevator pitch goes here",
  "launch_path": "/",
  "icons": { "128": "/img/icon-128.png" },
  "developer": {
    "name": "Your name or organization",
    "url": "http://your-homepage-here.org"
  }
}

In it you define the name, describe the app, give us info about yourself and which icons to display. You also define the localisations that are available and what access you need to the hardware. Depending on how many things you want to access, you can host the app yourself or you have to get it hosted through our infrastructure. This is a crucial part of keeping the platform secure. We can not just allow any app to make phone calls for example without the user initiating them.

These are the three levels of apps available in Firefox OS. For third party app developers, the first two are the most interesting.

• Hosted apps – stored on your server, easy to upgrade, limited access.
• Privileged apps – reviewed by the App store, uses a Content Security Policy, hosted on trusted server
• Certified apps – part of the OS, only by Mozilla and partners

Apps that run on your own server have all the access HTML5 gives them (local storage via IndexedDB, offline storage via AppCache) and the new WebAPIs defined by Mozilla and proposed as a standard. A few of these APIs are also available across other browsers, for example the Mouselock API or the Battery API.

• Vibration API
• Screen Orientation
• Geolocation API
• Mouse Lock API
• Open WebApps
• Network Information API
• Battery Status API
• Alarm API
• Push Notifications API
• WebFM API / FMRadio
• WebPayment
• IndexedDB
• Ambient light sensor
• Proximity sensor
• Notification

One very important API in this stack is the Open Web Apps API. With these few lines of code you can turn any HTML5 web app into a Firefox OS app by offering a link or button to install it. No need to go through the marketplace at all – you can be in full control of your app.

var installapp = navigator.mozApps.install(manifestURL);
installapp.onsuccess = function(data) {
  // App is installed
};
installapp.onerror = function() {
 // App wasn't installed, info is in 
 // installapp.error.name
};

All the APIs are kept simple, they have a few properties you can reda out and fire events when there are changes in their values. If you used jQuery, you should be very familiar with this approach. This code, showing the Battery API should not be black magic.

var b = navigator.battery;
if (b) {
  var level = Math.round(b.level * 100) + "%",
      charging = (b.charging) ? "" : "not ",
      chargeTime = parseInt(b.chargingTime / 60, 10),
      dischargeTime = parseInt(b.dischargingTime/60,10);
  b.addEventListener("levelchange", show);
  b.addEventListener("chargingchange", show);
  b.addEventListener("chargingtimechange", show);
  b.addEventListener("dischargingtimechange", show);
}

If you host your app in the Mozilla Marketplace your app can do more than just the APIs listed earlier. You can for example access the address book, store data on the device’s SD card, connect via TCP Sockets or call third party APIs with XHR.

• Device Storage API
• Browser API
• TCP Socket API
• Contacts API
• systemXHR

For a hosted, privileged app it is simple to create a new contact. That enables you for example to sync address books across services. As with all the other APIs, you get an event handler that gets fired on success or failure.

var contact = new mozContact();
contact.init({name: "Christian"});
var request = navigator.mozContacts.save(contact);
request.onsuccess = function() {
// contact generated
};
request.onerror = function() {
// contact generation failed
};

Certified apps – apps built by Mozilla and partners have full access to the hardware and can do everything on it, including calls and text messaging and reading and writing permissions as well as accessing the camera.

• WebTelephony
• WebSMS
• Idle API
• Settings API
• Power Management API
• Mobile Connection API
• WiFi Information API
• WebBluetooth
• Permissions API
• Network Stats API
• Camera API
• Time/Clock API
• Attention screen
• Voicemail

One question we get a lot is why hosted apps on your own server couldn’t get full access to the camera and the phone – something that always is an annoyance on iOS which is why we need to use something like phonegap to create native code from our HTML5 solutions. The reason is security. We can not just allow random code not in our control to access these devices without the user knowingly allowing it every time you want to access this functionality.

If however, you are fine for the user to initiate the access, then there is a way using web activities. This for example is the result of asking for a picture:

The user gets an interface that allows access to the gallery, the wallpaper or to the camera. Once a photo is picked from any of those, the data goes back to your app. In other words, web activities allow you to interact with the native apps built into the OS for the purpose of storing, creating and manipulating a certain type of data. Instead of just sending the user to the other app you have a full feedback loop once the activity was successfully done, or cancelled. This is similar to intents on Android or pseudo URL protocols on iOS, with the difference that the user gets back to your app automatically.

There are many predefined Web Actitivies allowing you to talk to native apps. All of these are also proposals for standardisation.

• configure
• costcontrol
• dial
• open
• pick
• record
• save-bookmark
• share
• view
• new, f.e type: “websms/sms” or “webcontacts/contact”

For example this is all the code needed to send a phone number to the hardware. For the user it would switch to the dialer app and they have to initiate the call. Once the call is hung up (or could not be connected) the user gets back to your app with information on the call (duration, and the like).

var call = new MozActivity({
  name: "dial",
  data: {
    number: "+1804100100"
  }
});

To get a picture from the phone you initiate the pick activity and specify an image MIME type. This offers the user all the apps that store and manipulate images – including the camera – to choose.

var getphoto = new MozActivity({
  name: "pick",
  data: {
    type: ["image/png", "image/jpg", "image/jpeg"]
  }
});

Again, a simple event handler gets you the image as a data blob and you can play with it in your app.

getphoto.onsuccess = function () {
  var img = document.createElement("img");
  if (this.result.blob.type.indexOf("image") != -1) {
    img.src = window.URL.createObjectURL(this.result.blob);
  }
};
getphoto.onerror = function () { // error
};

The great news is that if you have Firefox on Android, this functionality is also available outside of Firefox OS for you – any Android device will do.

I hope you are as excited as we are and you are ready to have a go at playing with these APIs and Activities. But where to start?

The Firefox OS Developer Hub is the one-stop-shop for everything Firefox OS. There you can find information on what makes a good HTML5 app, play and download example apps to change into yours and find information how to submit your app to the marketplace or how to publish it yourself. You also get information about monetisation and how to set up a development environment (basically installing the simulator).

The simplest way to test out Firefox OS is to install the Simulator, which is just an add-on for Firefox. Once installed you can test your apps on your server or on your local hard-drive in a Firefox OS instance running in an own thread and an own window. You can get all kind of feedback about your app working in Firefox OS with the developer console and the error logs.

alt=”Boilerplate App” height=”400” class=”middle shadow”>

Firefox OS Boilerplate is a demo app that has stub code for all the different Web Activities. You can try them out that way and just delete the ones you don’t need. It is a great demo app to get started with and base your efforts on.

Sooner or later you’d want to test your app on a real device though. The easiest way to do that is to get a developer phone from Geeksphone.com. These have the same specifications as the Firefox OS phones sold in the markets our partners are targeting. These are now ready for pre-order and the shop should be live soon.

Even if you don’t care for Firefox OS or don’t want to build something for it, rest assured that it will have an impact on the current mobile web. A whole new group of users will emerge and the mobile version of your site will become a calling card for them to get interested in your offers. And if anything, HTML5 is supported by every player in the market, so now is a good time to brush up what is out there. This is what Firefox OS brings you – and soon:

• A whole new audience
• HTML5 without the lock-out
• Your web site is your ad!
• Minimal extra work, it works across platforms

“Setting disruptors to stun” was the keynote at HTML5 Devcon in San Francisco in April 2013. In it, I am explaining why we can not directly compare native and web apps and that the technical differences are not really the main issue. The main problem is that native apps follow a very old principle of “built-in obsolescence” which means that they are built to break and be replaced with a newer version so you can sell more. The talk then shows how Firefox OS disrupts that idea with the dynamic app discovery and by going to where new audiences are.

• Video on YouTube
  
• Slides
  
• Screencast
  

Transcript

Thanks for coming again. Thanks for being in the grand ballroom. With this chandelier I would’ve expected people to dress up a bit more nicely, but we’re geeks so I guess that didn’t work out. Today I was asked to give an inspiring speech about things and stuff, and I think that’s a very good start for a day. I wanted to do something very, very technical, but then it’s a keynote so you don’t do that, so don’t expect that from me. We can talk technical in any way you want to later.

I want to talk about how the web used to be this massive disruptor to a terrible market and how it changed over the years, and how in the last few years, especially last year here, a lot of people started scaring us into thinking the web was not there any more and it’s a new thing that we have to do right now and we are all going to lose our job and be homeless in two months because we don’t support the newest coolest iPad. It’s like this children’s book that you can buy now, which is called, “You can’t be an astronaut, it’s just not realistic.” This is really cool to give to your kids, like, “Here you go.”

Back in the days when I started on the web it was like this. We had wired connections and we all had keyboards to surf on. We all had to keep the mouse up, otherwise it would fall off the keyboard. This is what the web was about. It was just beautiful and in nice colors, and every kid had the hat sideways. It was just this wonderfully cool thing.

In reality, it was a really cool thing. I worked as a radio journalist back then, and I saw the Internet as there for everybody to start publishing and for everybody to be found worldwide and to communicate with people worldwide. To me this was a totally new thing. Before that we had these BBS’s where you had to know the telephone number to call to connect and get data from another server worldwide.

Then with the Internet, we connected with modems that sounded a bit like Skrillex but really wasn’t. It was just connectivity. You stood there and like, “This almost looks like an image, just give it another five minutes and it’ll be fine.” You had connections where you loaded something and then you disconnected it because you paid per minute, and then you went through the cache to find all the images you’ve been downloading because while you where loading it was too slow.

All these were really cool things, but it was a geek thing. The main market basically saw us like that. They saw it like the Ubuntu launch party there. Basically these are the geek guys that just do that and it’s never going to catch on and nobody cares. Old-school programmers like mainframe programmers or people that use Java and things like that, people who have beards and suspenders and are real men, told us that the web will never be anything. “That’s just a toy. You use that angle bracket stuff that’s never coding.”

Nowadays it’s a bit different. The web is mainstream and we’re all these cool hipsters. Everybody uses the web for something. Most of the time horrible things, like following Justin Bieber on Twitter and things like that, but everybody uses it and we’re seen as these magical creatures that can build websites and nobody knows what we are doing.

The reason why that blossomed so much in those few years is that it’s built on a principle that anybody can be on the web just with an HTTP connection and something that shows HTML. It doesn’t matter where you are, it doesn’t matter what your ability is, what your language is, what your connectivity is. Everybody is invited. That was the Olympic Games, the opening, and that’s when Tim Berners-Lee typed this in and said the web that he invented, or with other people, is for everyone.

We keep forgetting that, just how powerful the web is for people who don’t have a voice in mainstream media, who cannot get a school education but they can go to an internet café and look at a Udacity course or look at a Khan Academy course if they wanted too. They can look at Wikipedia. I went to the library to do my homework. I didn’t have Wikipedia. I know teachers have actually put wrong things in Wikipedia articles to see how many students will actually bring that in their essays, which is a really cool way of using the web as well.

Everybody on the web is a consumer and a creator. We keep forgetting that because we are getting into that consumption thing. People get excited, “I can watch Game of Thrones streaming on my Internet.” You’re like, “How is that better than TV? You can start and stop it, that’s just like a VCR.” A streaming video, a streaming TV channel would allow the audience to remix it and to do things with it and to vote on different endings and make it different.

This is what we do in Mozilla with the Webmaker project where we invite kids and journalists and people who are just afraid of computers and not use to the web for anything to start playing with them and start creating. Seeing how empowered they feel when they start creating is just gorgeous, because for a lot of people it’s a totally new job that they couldn’t have had before. So good times we’ll have.

We have these browsers that get better and better and better. We had a few browsers that finally died and then we had a few browsers that actually agreed on everything. HTML 5 means first and foremost that all browsers run the HTML the same way. That was a big, big thing. We see this as a given now, but actually that white space in Internet Explorer between LI items means you couldn’t style them. That was just a very annoying thing. You had to delete all kinds of things in there.

The browsers got better and better and we’re like, “Yes, we got it made, we got these cool HTML 5 APIs, we can do something.” Then change happened. What’s the main difference between Bill Clinton’s inauguration and Obama’s inauguration, except for the size of the flag and the color of the president, is everybody has this phone and takes pictures. Really blurry ones, really bad ones but everybody wants to take a picture and put it up online and be the first one to put it online because the 600 other people in that room don’t do the same thing, they don’t have the same idea.

I love it when you are at concerts and people hold their iPads up and film the band. You’re like, “Yeah, that sound quality is going to be amazing.” I had it the other day at Dropkick Murphys. I’m like, “Dude, last time you wouldn’t have survived and your iPod wouldn’t have,” but fair enough.

The web came around and the mobile phones came around, the smartphone came around. All hail the hypnophone; everybody has one, everybody needs one. It’s a great thing. You can talk to your friends who are on the other side of the planet, so you don’t have to talk to people next to you because they’re smelly and they spit and stuff. You have your virtual friends, so you don’t need to have real connections with other people, but you can complain online that you don’t have any friends. It’s a very on-the-go market and sometimes you even have connectivity and video with AT&T.

It started well. This is Steve Jobs, the visionary, the really, really good man, a really, really interesting guy. He released the iPhone … well, he had a few people helping him. He released the smartphone and iPhone and the first thing he said, “To be really disruptive and re-invent the phone, we have to actually have no SDK. It’s the web, it’s a web-based phone. You have Safari, you have the power of Safari and HTML 5 in your hand. You can build everything on the web with the phone, you can build great applications that can talk to the telephone, can talk to the map application.” That’s what he said.

Then the big backlash came from the developers and internally. Why did that happen? Well first of all, the mobile web was this mixed thing that nobody knew what’s going on there. We had this thing in the middle, and we had web developers on one side and native developers on the other, and both of them wanted to do it.

The native app developer is different to a web developer in many, many ways. They are actually used to a different environment. As a web developer I’ve got not SDK. I use VI, I use sublime text, I use that and we argue for a month who’s got the better text editor. We don’t wait for actually downloading an SDK for it as well.

The mobile space is a competitive and very closed market. The success of companies is very much based off how many patents they have and what they can actually protect from another. Like, “Oh, you can’t touch the screen of my phone because that’s my right.” Developers coming from that environment, for them the web seems scary. Like, “Everything is free and you can look at my code?” “How can I protect my java script code?” is a question I get every single time. Put it on a memory stick; leave it in your desk.

Fragmentation is the next big horror. “Oh my God, people have different phones and basically different sizes, and I have to support all of them. If only we had one government issued phone for everybody that has a fixed static thing.” For web developers it was, “Yeah, so? This is cool, I can write things for different platforms.” So fragmentation is being this horror word for everybody.

Shouldn’t we cherish flexibility much more? Shouldn’t we say, “Hey, if everybody cannot afford the newest iPhone, they have an old one, why not give them something for an iPhone 4? I mean these are just people with so much hardship in their lives, they only have an iPhone 4, so we should give them something.”

If you think about it, these tablets and smartphones are actually very flexible. Because you see as soon as you tilt them, they get longer. Because nothing at an angle could be as high as the other one, as long as it’s longer. Every display of those … I guess if you have the phone and hold it, it just automatically happens slowly so you don’t realize it. So tilting the phone makes it longer, and this is something you care about in your designs as well.

I wondered what the whole backlash was about. Why do developers get so riled up about not having an SDK and actually bringing the web on the phone? I did some research and I found this wonderful website called, “The Story of Stuff,” which explains about consumption and how America with 1% of the world population creates 20% of the waste and all these kind of interesting things. It’s a great thing to learn on the web. It’s in Flash but it’s not evil, so it’s really nice.

I learned about an old, old idea from Victor Lebow in The Journal of Retailing 1955. Actually what they said, and he was one of the advisors of President Eisenhower back then as well, “To make American companies be successful and make sure that we have money and jobs for the next few years our enormously productive economy demands that we make consumption our way of life, that we convert the buying and use of goods into rituals, that we seek our spiritual satisfaction, our ego satisfaction in consumption. We need things consumed, burned up, replaced and discarded at an ever-accelerating rate.” That was in 1955, it’s called, “The Principle of Obsolescence” and I’m happy I managed to pronounce that word.

Now as evil minds thing alike, there was this person that a year before even took that further. The build in obsolescence means that products are built to break after a year or two so you buy a new one. You realize that with every brand out there. I remember when I could kick a car door and there wasn’t a dent except my foot. Nowadays you have to replace everything and there are fifteen sensors in there to actually realize, “Hey…” parking sensors and all kinds of things.

Clifford Brooke Stevens actually took that further – and you can see that he is a very content and happy person – because he came up with the idea of the planned and built-in obsolescence. You don’t even need to make things break, you just have to make them look old and look outdated. You have to instill in the buyer the desire to own something a little newer, a little better, a little sooner than is necessary.

Every advertising is about this. Everything we see on telly is like, “This now has rounded corners.” Okay. How many people really feel like “Oh now I need this”. I was at Mobile World Congress and they showed all these hardware providers who went there and I went to every stand and asked, “What do you have?” “We got a new phone.” “What does it do?” “It’s bigger.” “Okay, is it faster too?” “Oh yeah, it’s faster too.” “What else does it do?” “It’s bigger and nicer and…” It’s no change. It’s just like a constant change in there that has to happen.

Perceived obsolescence is the next. Planned style obsolescence occurs when marketers change the styling of products so consumers will purchase products more frequently. The style changes are designed to make the owners of the old model feel out of date. You feel embarrassed pulling your first generation iPhone out in the coffee shop in San Francisco. This is because of this. We’ve been trained to think that things have to be outdated quickly and they’ve got to get new, new, new, new.

These shoes are 12 years old. Doc Martens in England. Now that Doc Martens has been sold to a company somewhere in the East, Doc Martens break within a year now as well. These ones don’t yet. So I will be very unhappy when they break.

It’s just amazing how we got into that. Other people thought it already as well. This was the ‘50s and everybody’s, “Oh my God, we’ve got to do this.” Then in the ‘60s some cynical mind basically said the systemic attempt of business to make us wasteful, debt ridden and permanently discontented individuals. To a degree, that’s right. People really, really rack up their credit card bills to get a new smartphone that they don’t need because they actually have a good smartphone already, but they want to be the new cool ones to have to swag and be awesome about it.

In essence, this is not our struggle. This is Apple’s and Google’s struggle and Samsung’s struggle and hardware makers’ struggle. We cannot compete with that. We cannot go and say, “Look, websites, you can edit it, you can change it, you can change the interface of a website. It will be maintainable for five years in the future.” No, no, no this thing has to break tomorrow. What can you give me that makes people buy a new phone because they want to have the next version of that game? This happens.

Web development and native development cannot be compared one to one. We always do these HTML 5 showcases where we show that HTML 5 could be like native apps. Then we make it work across all the browsers and across all the platforms like we should in HTML 5, and it turns out not to be as performing and as good as the native app. If you really want to prove that it does the same, do it on one platform, one browser and one configuration. This is not HTML 5, this is just making a native app in some environment that should not be native.

Fragmentation to us is a given. I never knew what browser you use. Hopefully Firefox, otherwise you have a bad time. I didn’t know what connection you have. I don’t know what resolution you have. I don’t know if you’re drunk. I don’t know if you can read English. I don’t know if you’re sober but you can’t read English. I don’t know anything about you and I love that. I love to write defensive code that actually says, “Can you do this?” “Yes.” “Okay, do this.”

@supports was put in Firefox Nightly yesterday, so basically you can have modernizer in CSS itself and in JavaScript. That’s kind of the stuff we need. All of these things [different hardware on screen] should get something. They should not get the same. They should get something that people can stomach.

To me it’s this golden playground. It’s a bit like Temple Run. You’ve got this street full of gold and there’s all kinds stumbling blocks and stuff, and we actually have to fix these stumbling blocks. It’s a bit like the 101. You go down to the Silicon Valley, you see how many millions of dollars are spent on different companies and you’ve got all these potholes at the same time.

The mobile web is there for us to make a good living with, but we just try to go for that big gold gem in the sky all the time. We want to be that $30 million seventeen-year-old kid that got bought by some company because this is the future. This is the same … I don’t want to say a strong word. This is the same lie that we have with this built-in obsolescence.

Yes, there will be one guy who’s actually starting to Facebook, there will be one guy who gets $1 billion for his company, but this is not maintainable. Not all of you can be that guy, and not all of you probably want to be that guy because they don’t have free time in their life anymore and a lot of pressure on them.

Who here plays an instrument or sings in a band? Why? You can never be as good and as successful and fast and rich as Justin Bieber. You don’t need to play your instrument, you need a producer. You need a nice dance move, you need some swag, and that’s about it. Why do you bother with this? You cannot be Justin Bieber. He’s much younger than you, he’s much faster than you, he’s much better than you.

Why do you do it? Because you like it. It’s fun to do. A musician is a person that takes thousand of dollars of gear 100 miles away to play $100 gig, because we love it. Because we want to do things and we don’t want that mainstream mediocrity that means that if you do the Justin Bieber thing and you’re successful for half a year you’re going to be in rehab two years later. So let’s play the long game a bit and think about what you’re going to do in 10 years with that, rather than, “Oh, money, money, money, more, more, bigger, bigger, bigger.”

We need lateral thinking. Which line of this one is longer? The upper, downer? Are they the same? No, they’re not. So why did all of you think that this is the same length? Because you’ve seen that thing before, it’s an old trick. It’s an old trap. It’s a clever trap. It’s obvious that they should different lengths, but it actually isn’t. You’re like, “I’ve seen that, you’re not going to get me again with this.”

This is how we build things right now. We learn hacks in browsers and then we internalize them and say, “The web will always be shit at that so I cannot do that in the future. I will do it like this for the next 15 years and, ‘The web just can’t do it, I’m sorry.’” Let’s think about it. Let’s measure things. Don’t get too excited about measuring like this. Lots of people get JS perf and these kinds of things, but it’s just like you can measure things but you have to measure them in context. Don’t fall into the too-clever trap. Don’t see the thing for the first time and you remember it didn’t work last time and say, “It’s not going to work again.”

What do we do now, instead of thinking about why we come and use the web? We build many, many, many, many awesome solutions. We build so many awesome solutions it’s incredible. We’ve got this Bootstrap. You don’t need to learn any HTML, just use Bootstrap and start from that if you’re not a professional. Grunt, Ember, Backbone, jQuery, Sencha, Hammer.js, Emmett, Compass, SASS, LESS, Zepto, blah blah blah, all these cool things that are coming out.

All of these things are great. They really are good. They are tools for power users that need to actually make their day-to-day job easier. They’re great. We just make new ones every month, that’s the problem with it, but we actually want to be more professional about it so we tell people, “These are the things you have to use, otherwise you are not really a web developer.” When I hear people say you need to know command line to be a web developer I’m like, “No, sorry, this is not the same. The command line is not on the web. You build things that are visual, you build interfaces, you build things that people need.”

We’ve got many, many awesome demos. This was going around a few months ago, a few weeks ago, a very, very remembrable URL fff.cmicmcn.com which showed all kinds of playful things and HTML 5 canvas demos and stuff. All of the things we’ve done in Flash four years ago and we now use in HTML 5 and we say, “This is awesome.” I think what we are having right now is an overflow of awesome.

I’m getting tired of seeing awesome, awesome, awesome, awesome. What I want to see is, “We’ve got this really terrible content management system. We have a room booking system, here’s how we fix it with HTML. Here’s how we made people happy across five different platforms.”

We don’t have to impress each other. We have to impress the mainstream. So stop building tools for each other and making the other tool do one thing less than the other one does. They’re all open source. Fork them, do things with them. Don’t build your own again.

I get excited about people building things. I’ve just been at POSCON in South Carolina, and all the developers you meet there are actually in small companies or freelancers. You show them something, I did a CCS 3 talk and two weeks later you get an email, “Oh, thanks for your talk, here is how I implemented it into my product.” I’m like, “Yes, this is exactly what I want to do.” Please build these things. Give it out to the main market. Don’t be excited that everybody is clever on stage and then be depressed that you’re not on stage and you build your own system so you get on stage. That’s a bit of loop we do at the moment.

The other day I had a guy in my gym in London ask me, “Hey you’ve got a computer, so you know about the Internet?” I’m like, “That’s obviously an interesting fallacy.” He’s like, “Oh, I want to get a new job. I want to learn about the Internet stuff. People say it’s really good to be a web developer and it’s a really good job to know that.” So I found this old laptop in my house that I cleaned up and I just put Ubuntu on it and a text editor and an HTML 5 book, and that’s what I gave him. I didn’t tell him, “Use Grunt, use Ember, start with Bootstrap.” That’s how I learned it, that’s how I got incredibly excited realizing that if I put a different color in there it looks different. Wow.

We can do that nowadays. The web needs no massive tools for production, for power users. Tools are great. For starters, don’t overload them with things that they can’t rely on in the future. All of these things are not built in the browser, so they might get outdated. They might get replaced. Don’t teach people things that are for just for the next two months.

How do we disrupt? How do we change that whole market? How do we get back to that idea that from the very beginning we said software is on the web and content is on the web, and it’s distributed worldwide without having to send floppy discs and CDs to each other? How do we go back to that?

The first thing is to stop being scared. Last year we had a few interesting things on stage here where people said, “Maybe the web is over. Maybe the web is going away.” We’ve got to keep the lights going. We’ve got to keep the lights going! I mean who of you as a web developer has problems paying their electricity bill? I didn’t know it was that high in San Francisco. My brother’s a fire man, he can’t find a job at the moment or a better job. He hates his job. But when he doesn’t do his job, people burn. When we don’t do our job things are five pixels off.

Don’t be worried about the future of the web. The web survived Flash. The web survived Java. The web survived Java Server Faces. The web survived any kinds of things out there because it’s a distribution model. It’s not technology. It’s not a certain stack of technology.

Will the web be the same in seven years? Hell, no. It will not be the same next month. That’s the power of the web. It keeps mutating. It keeps getting better. You cannot compare it with systems that are actually, “This is version one of the web, this is version two of the web.” No. This is worldwide changing constantly every second, and that’s the cool thing about it.

Chill out. Breathe. You’re going to have a job in five years, ten year’s time easily if you bet on the web right now. It may not be the same job, you have to be up on your feet and learn new things, but that’s what makes it interesting. I always hated a job that I got a pamphlet and like, “This is what you are going to be doing the next twelve years. No change, don’t worry about it.”

On the web, different story. New challenges every single day. I think we should stop copying. A lot of people, “Oh, there’s a native app that everybody uses right now, so let’s copy that in HTML 5. Let’s copy that in our technologies.” No, it’s a different idea. First of all you’ve got your obsolescence thing. Not every native app has everything in there in the beginning because they want to roll it out. If your app has all the features at the beginning you’re not going to have good time. You want to roll it out month by month by month. Trying to keep up with that is not possible.

Try to actually see the power of the web and the benefits of the web, of web technologies over native technologies. The biggest one is flexibility. If your app is not flexible you are doing it wrong. The thing should actually tell the user, “Okay, this works, this works, this works. I have a problem with that so I don’t give you that functionality.” Or just don’t show the functionality. Don’t promise things that you can’t fulfill. It’s an if statement, it’s not that hard to do.

If you copy, then kick ass. Sencha did this Fastbook and showed that the whole HTML 5 and stuff from Facebook was actually a misnomer and actually based on wrong assumptions. They did a good thing there and they showed basically that you can do a fast app on an iPhone in HTML 5, who should have known, like the ex-CEO of the company wanted it to be. That’s great. If you do these kinds of things then we should stop saying, “Yeah, but it only works in IOS and it only works in that.” Yeah, that’s what we cared about it in this moment.

We are fixing it together with them right now, and Flexbox is now in Firefox partly because Sencha Fastbook wanted to have it. We actually had a real, real good reason and demo to actually see what the problem was.

The other way to disrupt is to go where others don’t go. The problem is they’ll be like, “if you want to make money now only go for the iPhone market in America. That’s where people spend money.” This earth is this round blue thing and there’s these people, people everywhere and they want to do things on the web as well. Why not tap into a market that is not there for others? Why not tap into a market where the people that are actually driven by obsolescence cannot go, because the market can’t afford it, because the market can’t do it?

That is what we are doing with Firefox OS. I’m not here to make a pitch. I’ll just say what it is right now, because it is 90% of my life at the moment and I get incredibly excited about. We went to the Mobile World Congress, which is the most evil sales show on this planet. I spent two days just reporting incidents of booth babes to blogs in America that talk about inequality at conferences.

We rocked that thing. We were in every headline. Everybody released new phones, everybody released new things, and Firefox as an open source company, as a non-for profit organization giving out a free operating system was the main headline. Why? Because we got 18 mobile partners to partner with us and four hardware partners to bring out phones that are internet connected, that are web connected with smartphone functionality to markets that cannot get iPhones and that cannot get Android phones and can’t afford them.

Emerging markets like South America, like Eastern Europe, we have a lot of partners that go out to them. These aren’t partners that sell the thing with us, these are partners that actually code the thing with us. Instead of just having salespeople around them, we’re just like, “Okay you want to be part of this? Show us your engineers.” This is what where doing with that.

What Firefox OS does is replace old feature phones. We don’t replace the Androids, we don’t replace the IOS’s because we can’t compete on that market. We don’t have the marketing budget, we don’t have actually the hardware, we don’t have the people that want to actually partner with us because they’re like, “We’re just stinky free open hippies, that’s not right to work with.”

One of the main differentiators for us here in Firefox OS is first of all that everything is HTML 5 on that phone. Nothing in here is Java or Cocoa or Objective C. This is all HTML 5 and it’s on Github. You can go play with it. Of course for the mainstream market this means, “Oh, who cares?” What people care about is actually making it easier for them to find apps and to play with apps.

What is easy? Finding things on the internet. Maybe a search functionality, maybe something like playing with it. If you go on Firefox OS and hopefully my connector is working here, and I have a mouse somewhere, there you go. This is the emulator that was just put into Firefox as an add-on. Once you put it in there and it starts … Why does it do that to me when I go on stage? There you go. You can start the emulator. This is what it looks like. You got the error console, you can play with it, and this is the operating system itself.

If I go to a market right now and I want to have an app about my favorite band, I want to know something about a band, what do I do? I click through music apps, then I got 6000 of them, all of them reviewed by probably paid reviewers. I don’t know the name of those things. I don’t know what to do. That’s why we have to pay posters. That’s why we have to pay advertising, to get our name of our app into people’s heads. This is software, this is indexable software, why do we need this?

In Firefox OS, if you go here, you search for example Nine Inch Nails. Let’s do a good band. You get the background already changed into Nine Inch Nails and you get … oh we have nine here, wonderful. There’s a space in there, that was the problem. Let’s use U2 as another demo.

U2. I’ve got my background here. It changed into U2. I’ve got YouTube for videos, I’ve got Grooveshark for music, I’ve got SoundCloud for music, Wikipedia for written information. I can buy tickets on Songkick. It realized that I was entering a band and gave me your applications, anybody’s applications that are submitted in the market or are on the web. These are not the apps that are in my phone, these are apps on the web.

I can now click on this one for example, Grooveshark, and start listening to a U2 song if I really don’t like my life. Once I had a good experience with that app, I can go back and do a long click on the app and install it. A long click will then install it on the operating system. It will operate it like a bookmark like it does in IOS. It actually will install it with app cache, with everything going offline and giving you access to the hardware in ways that IOS doesn’t give you.

We made app discovery and app try before you buy as simple as actually surfing the web. If you have a mobile website and you want to sell an app, your mobile website is your advertisement for the app because we can index that for you and you can actually show up and do search results. This is bringing search technology to the app world, which is very interesting to me. I think it’s just, for you, a good idea to spruce up your mobile HTML versions that you have right now of your pages. You can play with that yourself.

Somewhere I’ve got my presentation again. There you go. I found that hard to explain to people at times. Once they started playing with it they entered a movie title and then they realized, “There’s movie apps, there’s Flixster, I can watch these movies.” You go from the use case to the app and from the app to the use case, which is what we do with closed markets right now.

The other thing we do is we enable hardware access. You’ve got all these API’s to access the hardware directly from JavaScript. The vibration API, which was called Vibrator API, I made too many stupid jokes, geo-location was one of the first things that we did years and years ago and then it went out to all the browsers. All of these APIs are not inside a SDK, these are standardized API proposals that other browsers can implement as well. Geo-location is across all browsers, the battery API is across all browsers. Network information, speed connectivity APIs have been used for others as well, indexedDB has been used by others.

You get full access to the hardware. That was always the problem in the iPhone, basically you got promise to access the hardware but you couldn’t get to it. You just had to build a native app going through PhoneGap or something like that. The other thing we did, of course we cannot allow any app to access every piece of the hardware, because you could make a puzzle game that calls 1-900 numbers in the background and racks up lots and lots of money. We actually have to review some apps in terms of security, how much access to the hardware you want.

We also came up with a system called Web Activities, which was much like Web Intents in Chrome, but it’s actually active. What it does, it allows you to use other apps to do something on your behalf. If you want to do a telephone call you have to have an app that is listed in the marketplace and reviewed by Firefox or by Mozilla. If you want to just do a telephone call from a web app that you host on your own server, you can use the telephony pick API here, so you’ve got the pick action. Nope. Okay, again.

You need a photo. If you want to have a photo you just call a pick action. You don’t care where the photo comes from. You don’t want to know if it’s from the gallery, from the wallpaper or if it’s from the camera. That’s what you do. You do a pick action, the user then chooses which ones he wants to actually use. Give you a photo; you get the photo back.

Same with the telephone call, you give the telephone action a call … telephone number. It switches to the dialer app. The user has to initiate the call. You don’t do it on their behalf. It’s up to them to actually make that call. Once they hang up you go back to your app automatically and you get the duration of the call and the telephone number that was called.

The difference to the pseudo-protocols and things that we had on IOS is that you get a feedback loop. You bring something to a native app and then you get the data back. That is cool because I don’t want to use your phone app all the time. I have a phone app that works fine on my phone. Why can’t I just use that? The Web Activities allow you actually to … any websites and any web app, to actually tie into other native apps of the operating system.

That works across Android and that works across Firefox OS as well. I love that because I don’t want to be in control for that. I don’t want to have your Flickr or Twitter or whatever credentials. These are yours, don’t give me them. It’s your way to share it on Twitter. It’s yours to actually take away. I don’t want my app to be responsible for things happening on your Twitter stream.

That is right now happening because we identify on behalf of the user the whole time. Web Activities allow any HTML 5 app to go into native apps and do their thing and get the data back. It’s much more important to me then actually accessing it myself and getting their information.

It works well with others. If you put Firefox on your Android all of these things, well not all of the APIs but the Web Activities, for example, work as well. So you can do that. Firefox for Android supports down to Froyo, so you don’t need the newest coolest Android to actually get HTML 5 support, sensible HTML 5 support.

Opera does the same thing now. Opera is also a browser you can install on Android to go back to an old version of android, rather than having Chrome only on the newest one.

Another big thing that we just released is that you shouldn’t make people think about the web but just come halfway. At the game conference that was just here in San Francisco we’ve announced ASM.js, which is also … there’s a meetup at 6:00 in our office today on the Eventbrite I think. What that one is, it actually allows you to convert C++ games or C++ code into JavaScript code.

If you’re a C++ company and you want to do something on the web but you really don’t want to re-educate all of your developers onto JavaScript because C++ guys looking at JavaScript makes them covered in hives and stuff, you can use that. One thing that we announce is the Unreal 3D engine, now running in JavaScript and Canvas and web GL in the browsers. You don’t need Flash to run 3D games.

Electronic Arts was one of our partners to actually bring out the 3D gaming onto the web and just convert their apps, convert their games, not write them from scratch because that’s not going to happen. We want to have the fidelity of 3D gaming on the web but we don’t want people to have to write from scratch, so we wrote a converter.

Same as the PDF displayer in the browser – it is also done through the same engine. Instead of having a plug-in that gets hacked every two months we just ran the PDF in JavaScript and the original thing was a C++ library. If you’ve got cool C++ stuff right now you can convert it to JavaScript rather than learning JavaScript, which to me is a handshake back to the 1980s where we can work together. The web will not replace you. We want your stuff. That’s what we do.

What can you do? How can you be part of that? The first thing that I have not seen yet and I want to see much more is context aware applications. Everybody has … okay this is a responsive design, it’s smaller on the phone and shows five buttons and it’s bigger on the other one. It doesn’t change the context. It doesn’t give you a way to actually work with it.

Imagine a company that actually has a guy walking around going to meetings. The interface on the phone could be start it there, find my location, stop the meeting there. When he goes back into his office and starts the desktop, he opens the same app, the same HTML app, and it actually shows him, “Okay, here’s what you did today. Please put the notes in there. Please put the photos in there. Upload the other stuff.” We do different things that we do on a phone than we do on a desktop.

We shouldn’t just make everything dumber because the mobile phone is the clever thing. We should give you a context aware app. What do you want to do on a desktop? What do you want to do on a mobile? What do you want to do on a tablet? Give you the best experience on all of these. HTML 5 is the only technology that allows you to do that because a native app cannot do this. You have to install three different apps on three different platforms.

That’s just not clever to me. That just doesn’t make any sense, that I have Temple Run on my tablet and my mobile phone, they’re out of sync and I have to do the same challenges on both of them? That’s just terrible for a small problem but it’s just not nice.

Go small. Go offline. If you can cut out a few k’s cut out a few k’s. If you can make the thing work offline that people can enter things while they’re actually waiting for it to load, great, that’s what we want. We want this experience to be as smooth as possible because we are impatient when we are on the phone.

We don’t really care about reloading a page three times on our desktop but on the phone it’s like, “This is broken, this is broken.” I love it in maps when people like, “We can’t find the map.” “Well it’s going to space for you, be a bit more grateful.” When I’m here, one pound, fifty per megabyte Internet roaming. If you have this 20 MB animated gif landing page, I hate you.

Fix the first generation mobile web. This was the login system at the airport in Barcelona, how it looked on my Android. Well that’s fun. Especially when you go through a second step it asked you for your passport number to get fifteen minutes of Internet access. Sure, I found somebody else’s passport so it’s all good.

That shouldn’t happen anymore. This is just silly. This is just … a viewport meta tag should be enough to fix that kind of crap. Make sure you realize … we’ve got wonderful things like VW and VH now in CSS as well, it can make typography resize according to the size of the screen. We can make the flexibility that Flash had years ago in web technologies easily nowadays.

Trust and help the platforms. You’re complaining that something doesn’t work in Firefox. Go to Bugzilla, complain, be annoying, put screenshots there. Put test cases there. Tell people what is wrong. Don’t go on Twitter and say, “Oh, Firefox does this wrong; I hope somebody from Firefox reads this and does my work for me.”

Same with Chrome, same with Opera, same with Internet Explorer, all of these things are available to you to complain where people are working on them. Not where we get applause from other people when we complain about them. Help us make the web better by using what browsers put in. I told you about @supports. Look at that tonight. Don’t animate anything in JavaScript. We cannot hardware accelerate your JavaScript animations. We can hardware accelerate anything in CSS because that’s our engine, but when you simulate what the browsers do natively we cannot help you make the web faster. Then it’s no help complaining that browsers are slow. You made that. You took over the browser’s job, so you make it fast.

Let us do what we need to do. Use translate instead of top and left. Use CSS animation. Use CSS transitions instead of JavaScript animate. We can make the thing better. Every six weeks there’s a new browser out. These things change constantly, please use that stuff. Give us feedback, what is necessary, what is unnecessary, what you like, what you don’t like. Jump right in, it’s fun. Yes it’s messy, but hey, this is fun.

Nothing stops you from actually helping the web of the future by helping the people who build the platform of the web. You can be massively successful tomorrow with a great native app. Good luck. Have fun with it. In half a year’s time it is going to be obsolete because the next one has to come. If you want to do that, if you want to play on the web, play by its wonderful, open rules and be successful by sharing and actually playing with things that come in there.

Every week I find something new in browsers and it gets me terribly excited. It’s a sad life. If I had some of the things that I had in the past … that I didn’t in the past, I would be on a beach now or something because I wouldn’t have to work anymore. Every browser is a developer platform. Every browser is a conversion tool. Reader Mode in browsers allows you to actually fix a lot of sites and actually read them nicely rather than have to click through two thousand ads. With that, I am out of time. I thank you very much.