Let’s Get Physical With The Physical Web: Retail Store

Tweet about this on Twitter0Share on Facebook0Share on Google+0Share on LinkedIn11Pin on Pinterest0

Let’s Get Physical With The Physical Web features different use cases and ideas on how the Physical Web can be implemented in our day to day lives.

In this episode, I explore a Physical Web use case within the retail store environment. When approaching an end cap on the end of a aisle, we were able to receive Eddystone-URL signals that lead us to the products webpage. Giving us more information, product reviews, and other things such as the manual. After that, we were able to click on a separate Eddystone-URL link that gave us a mobile coupon for 10% or purchase. This would work great inside a retail environment to not only product more information about the product but also to entice the customer with an offer.

The important thing about this use case is that typically a retail store would need to create their own app to be able to have offers and specific webpages trigger by beacons. With the Physical Web, it is as simple as broadcasting a URL from a beacon. Making it better for both the business and the consumer.

Let’s Get Physical With The Physical Web: Rental Car

Let’s Get Physical With The Physical Web: Movie Poster

I hope you enjoyed this episode and stay tuned for the ones to come. If you know of any use cases or would like to see me demonstrate a specific use case, let me know in the comments below!

Tweet about this on Twitter0Share on Facebook0Share on Google+0Share on LinkedIn11Pin on Pinterest0
  • http://abiro.com/ Anders Borg

    Thanks for the video.

    Having one beacon per product item is not very realistic right now for a couple of reasons:
    – Cost
    – Installation work
    – Potentially also proximity, where several beacons would overlap, potentially generating a very long list of “hits” whenever you run Physical Web or Chrome

    For iBeacon (and I guess Eddystone-UID too) you can decide at what proximity a certain content should trigger based on settings related to a given content (well, at least that’s what we do). As Physical Web just links to existing sites, there’s no notion of such settings, so how do you achieve a “late” trigger on beacons? Do you simply control that by lowering the beacon’s transmission power?

    • Brandon Lane

      I didn’t emphasize it much in the video, but the reason I choose the end cap as the use case is because it wouldn’t be feasible for every product. But it is feasible for main displays and end caps. The Physical Web in retail stores is for businesses who want to be present on the consumers phone but don’t want to build an app. So connecting main displays and end caps would be feasible for those types of businesses.

      In order to control proximity, you would just lower beacon transmission power so that it only broadcasts a few meters. So it doesn’t work as well as iBeacon but it is still possible. Also, I was using two separate beacons to broadcast the two different URL’s.

      • http://abiro.com/ Anders Borg

        Another more or less obvious place is digital signage. It would be easy to announce the Physical Web possibility directly on the screen, to get more detailed information about what’s being shown, a coupon etc. Being able to change the URL remotely would be practical in that case.

  • http://abiro.com/ Anders Borg

    By the way, how did you achieve the two different views (information site and coupon)? Two different beacons or one beacon that broadcasted two URLs?

  • Pingback: Let's Get Physical With The Physical Web: For Sale Sign()

  • Kolykhalov Stas

    Thanks for the video, so as I understand I will need one beacon for each product, right?