Firefox Hello

» see hello.firefox.com as it lived, on the wayback machine

~ the last words ~

firefox was my default browser through most of 2010-2016, and i still missed firefox hello almost entirely. it shipped in firefox 34 in december 2014 as a small chat icon next to the address bar. you clicked it, you got a room url, you sent the url to whoever you wanted to talk to. that person opened it in any webrtc capable browser and the call started. no account, no install, no plugin. as a product it was actually pretty clean.

the part i missed was the whole product. through 2014-2016 my video calls were on skype, then on google hangouts inside gmail, then on whatsapp once the smartphone took over the use case. the conference call at work happened on bluejeans or webex. nobody i was talking to ever sent me a firefox hello link, and i never tried to send one out. mozilla's release notes had a paragraph about it, i read the paragraph and forgot it.

hello was built with telefonica digital, which ran the rooms server on the back end, and the underlying webrtc stack was the same one chrome and opera were also shipping. mozilla's pitch was that the open web should have a phone-call button inside the browser by default, the same way it has a download button. the pitch was right in the abstract. by 2016 the actual phone-call button people used was a tab inside gmail or a chat in whatsapp, not a feature in their browser chrome.

~ the record ~

~ how it worked ~

the room model was the second iteration of the product. firefox 34 launched with one-to-one calling where each user needed a firefox account, firefox 35 added persistent rooms you could share with anyone. by then the only thing the recipient needed was a webrtc browser, which by 2015 meant firefox, chrome, or opera. the rooms were named, the urls were guessable, and the audio quality was usually fine on a real broadband line.

on ttnet in ankara the audio held up most of the time, the video held up sometimes. the underlying webrtc stack handled the codec negotiation, which meant a hello call between firefox and chrome usually worked. the part that did not work was the social side, you had to convince the other person to click a weird-looking mozilla url, and people defaulted to whatever messenger was already open on their phone.

~ how it ended ~

mozilla announced the removal in the firefox 49 release notes on september 20 2016, with no big blog post and no extended retrospective. usage had been low for the whole life of the feature, the telefonica deal had run its course, and mozilla was already in the middle of the post-firefox-os strategic reset that would also eat persona, thunderbird's first-party status, and most of the consumer side experiments. hello was one of the cheaper cuts in that wave.

~ the long tail ~

the webrtc spec hello was built on stayed alive and became the load-bearing technology under almost every video call that happens in 2026. google meet runs on it, discord runs on it, jitsi runs on it, the new generation of remote-work tools run on it. firefox hello was an early bet that the browser itself should be the call ui. the bet was correct about webrtc and wrong about the browser. by 2020 the browser was a runtime, the call ui was somebody else's web app loaded inside that runtime, and the toolbar button mozilla had built was a small museum piece.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »