Proximity-based experiences challenge mobile designers to think of the user experience in new ways.
iBeacon and Bluetooth LE powered beacons might be a simple technology – after all, the only thing they really do is broadcast a small radio signal. But that signal allows an app to, well, do stuff based not on a user’s location, but on their proximity to something.
The Gateway Drug to the Internet of Everything
We call iBeacon the “gateway drug to the Internet of Everything” for a reason: it’s easy to understand, it’s small and simple, and it gets a conversation going about how consumers apps and digital experiences will increasingly react to physical things.
Suddenly, the atomic world is part of your design interface. Things that move around (like a car, a dog, a product display or another person) can be embedded in an experience. And things we don’t need to worry about online such as ambient noise and lighting, radio interference, and signal strength become important.
We’ve preached before that if you’re thinking of beacons as coupon dispensers as you wander a mall or store then you’re missing the big news about Bluetooth LE: that your phone can suddenly “see” and can be attuned to the physical world in ways that weren’t previously possible.
iBeacon gets us started by introducing proximity to the UX equation, and is simple enough to understand (although not so simple to execute well). But once you’ve talked about proximity, the conversation easily shifts to what’s next – things like detecting temperature, acceleration, or your heart beat; and the larger challenges of security, privacy and mesh networks in a physical world that’s becoming, in itself, a digital interface.
User versus Business Value
As the ‘becosystem’ expands we’re starting to see that it isn’t just retail that will drive the use of beacons.
For example, Major League Baseball is using beacons. While they’re taking a cautious approach, their focus might include special offers or seat upgrades but their larger plan is to create more value for fans (and perhaps remaining attractive to younger, more tech-savvy audiences). In San Francisco, Engadget reports that they’ll take it slow:
All told, 19 iBeacons are located at all of the fan entry and exit points of the ballpark, per MLB policy. That number will vary at other stadiums — the Dodgers, for example, are reported to have 65 installed, presumably due to the presence of more ways to get inside Dodger Stadium. They’ll be used to check fans in upon entry, assuming they have an iOS 7 device running the MLB At the Ballpark app and have Bluetooth turned on when they walk through the gate. The app’s available to both iOS and Android devices — and provides maps, concession info, video clips and the ability to upgrade your seat — but only folks with Apple devices benefit from the bespoke iBeacon experience.
The UN is using beacons to raise awareness of land mines. They recently partnered up with digital marketing firm Critical Masss and set up beacons around the top floor of the city’s New Museum. When a person came across the virtual landmine, the app, called Sweeper ‘explodes’ on contact. Following this, information comes up through the app noting how devastating the injury might have been.
Design Tensions and Beacon Strategies
With all of reality a new potential interface, there could become as many examples of beacon-driven experiences as there are categories of things – whether places, people, or moving objects.
But as the ‘becosystem’ evolves, we’re starting to see design decisions with decidedly specific ‘flavors’. We talk to dozens of people each week about what they’re doing with beacons (and, of course, have our own concepts and approaches) and there are patterns emerging which point to clear decisions that UX designers and business strategists are making as they come to terms with beacons.
The decisions aren’t binary. You don’t always choose one over the other. But you’ll usually end up at one end of the spectrum or the other.
Visible or Invisible Interactions?
One example of this design tension is whether a user “sees” the beacon? Not necessarily the device itself – but a tag on a counter, a shelf talker, or a mark on the floor? Or does the experience instead make the “trigger” invisible – and you focus on the consumer simply thinking that their app is really really smart.
Similarly, an amazing project called Iconeme turns a mannequin into a visible point of interaction – allowing users to order the goods they see in the store window:
But in other cases, like the UN Minefield exhibit mentioned above, the very point of the beacon is its invisibility.
So one design tension to resolve is the ‘tangibility’ of the beacon or trigger to the consumer: Will you make interaction points in the physical world clear? Or do you prefer a user experience where things just, well, magically happen?
Resolving Design Decisions
There will be as many solutions as designers for a world of beacons. And yet they’ll often be attempting to resolve entirely new decisions in designing a flawless and compelling user experience:
- Will your experience focus on things ‘found’ in the world – a specific product, say? Or will they act as helpers, bringing in content from elsewhere to supplement an in-store experience?
- How do you resolve the level of personalization, knowing that how someone feels about highly targeted content online might be quite different from in a store, where concerns about privacy might have a different context?
- Are you after big data and analysis and the beacons play a minor role, or do you focus on the user’s enjoyment and experience? Both are valid, and both might play different roles at different phases of the evolution of an app or in-store experience.
The good news is that there’s an increasing pool of examples of how designers have resolved the decisions about how to design a beacon experience. The rest, however, is up to you.
Share Your Thoughts
What design tensions have you found in your work with beacons? What are the major decisions you need to make if you’re designing a user experience?