Singapore Heritage Trail

There’s a new heritage trail of Little India in Singapore that uses Physical Web beacons to guide visitors through unique facts and stories, historical photographs, and crowd-sourced content.

The article on their web site is a great example how you can a) provide clear instructions on how to use the Physical Web and b) provide an incentive to start using. In the case of the trail there’s a contest. If you use your mobile device to access the Little India Physical Web Experience you can redeem a gift.

Samsung Browser Brings the Physical Web

There’s an interesting article by Peter O’Shaughnessy, Developer Advocate for Samsung on Bringing the real world to your browser with CloseBy. It describes how Samsung’s web browser detects Physical Web beacons. It works in a similar way to Google’s Chrome/Android in that it uses a proxy server to get and cache information (the title) of destination web addresses.

While it’s good to see the Physical Web expanding, we can’t help but question what this means for multiple notifications. Will Google and Samsung be both providing notifications for the same Physical Web beacon?

Chrome, Eddystone and the Omnibox

There are some posts on Twitter and articles talking about how Eddystone appearing in iOS Chrome’s Omnibox might transform proximity notification scenarios. So what is this and what does it look like?

This came about due to the Physical Web/Chrome teams experimenting with new ways to show Eddystone notifications:

At the moment, notifications appear at the end of the ‘Today’ view. They get a bit lost because you have to swipe down get the notifications, swipe left and then scroll to the bottom:

BeaconZone Eddystone notification at the bottom

Noone is going to see this unless they know it’s there and are trying very very hard. Even though Eddystone detection is designed to be ‘pull’ rather than ‘push’, it’s a bit too difficult to find local Physical Web beacons.

With Google’s experimental Omnibox implementation, beacons come up when you go to do a Chrome search. At the moment, to try it out you have to enable an experimental flag by visiting chrome://flags:

After you do this, local physical web beacons appear when you start a search:

It’s far more likely people will see this rather than the Chrome widget at the bottom of the notifications Today panel.

It’s unknown whether this will find it’s way into future versions of Chrome without having to set the flag or whether it might appear on Android. Android has more visible Eddystone detection as it’s built in Android itself (Play Services to be more specific) and appears near the top of the notifications panel.

UPDATE: As of October 2017, Google removed Eddystone detection from Chrome on iOS and Android. Only Android can provide notifications.

New ASensor Beacon

We have the new ASensor beacon in stock. This is our smallest sensor beacon measuring only 37.3mm x 37.3mm x 7mm and it uses the power efficient Dialog DA14580 that gives up to 1.5 years from a CR2025 battery.

The beacon supports iBeacon, Eddystone or sensor advertising. For sensor mode, the temperature, acceleration and battery level are in the advertising data.

asensor_smallerasensor_pcb_smaller

Inside the iB001M

Here’s a look inside our smallest beacon, the iB001M. The circuit board measures only 2cm across and the height of the beacon is is only 2.6mm.

ib001m_inside_smaller

The waterproof iB001M can transmit iBeacon and Eddystone at the same time. There’s also a press switch to turn on/off and a buzzer that’s found in the top side of the beacon (not shown) together with the waterproof ring. This beacon can be set up to only transmit advertising data when motion is detected.

It weighs only 4g so is great for wearable and pet-related applications.