Android Beam

~ the obituary ~

Android Beam is the one here I actually had, in the sense that it was on the phone whether I wanted it there or not. Any Android phone sold in Turkey from about 2012 onward that had NFC in it also had this, sitting in the settings under a name that explained nothing to anyone. I could not tell you the last time I saw two people deliberately put their phones back to back.

It arrived with Android 4.0 Ice Cream Sandwich in October 2011, which was the release where Android stopped looking like a prototype. Beam was one of the headline features. You held a screen up, touched another phone to it, and the display shrank into a small card that said Tap to Beam. Tapping it sent whatever you were looking at over to the other device.

The engineering was better than the outcome. NFC only carried the handshake, because NFC is far too slow to move a photo. What it actually did was use that handshake to turn Bluetooth on at both ends, pair the two devices with no dialog and no PIN, run the transfer, then shut Bluetooth off again. From Android 4.1 Jelly Bean that path handled photos and video. Samsung shipped a variant called S Beam that handed off to Wi-Fi Direct instead, which was considerably faster on the Galaxy phones that supported it.

~ the case file ~

~ how it worked ~

The part worth remembering is that Beam was not a file transfer feature. It was a way of moving context. A web page beamed as a bookmark and directions beamed as a map location, and a YouTube video arrived as a video already playing on the other phone. Apps could declare their own payload, so an app could beam a pointer to itself and open on the receiving device at the same screen you were already on.

That is a genuinely good idea, and it is what people describe when they describe Beam years later. Everything about the design assumed two people standing next to each other, which was correct, and assumed that standing next to someone was the hard part of sharing, which was not.

~ why nobody used it ~

Sharing had already moved. By 2013 anything you would have wanted to hand somebody was in a chat app, and the send button was one thumb away and worked at any distance to any platform. Beam needed both phones to be Android with NFC switched on, and it needed both people to know where the antenna sat, which on most handsets meant guessing and then adjusting until something buzzed.

There was also nothing anywhere telling you it existed. No onboarding and no prompt, just a settings entry a normal person had no reason to open. Bump had already tried the same gesture as a standalone app and had already found out that the physical act of touching two phones together is charming exactly once. Google eventually said out loud that usage was low, which was accurate and was not really a defense of the decision to bury it.

~ the long tail ~

Deprecation was announced in January 2019 and landed with Android 10 on 3 September. The replacement, Fast Share, was renamed Nearby Share before launch and is a straight answer to AirDrop: Bluetooth for discovery and wifi for the transfer, with no NFC anywhere in it. It works, and it is what people actually use now. What it dropped was the whole beam-the-live-app-state idea, which was the part that made the original interesting.

Beam kept limping along on devices through Android 13 for apps targeting old API levels, which is the usual arrangement for a deprecated API. Then Android 14 shipped in October 2023 and the NFC peer-to-peer stack came out of the framework completely. Twelve years and two separate death dates, for a gesture that now survives only as something people bring up when they want to argue that Android used to try weirder things.

@}-->--

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

« previous  ·  random  ·  next »