Google recently announced the release of their cross-platform BLE Beacon format. Here we look at what we can do with it and how to use this new API to manage our beacons. We recently saw the announcement of Google’s open beacon format, known as Eddystone. Released alongside this was the Proximity Beacon API, used to register and manage these beacons. Pairing this with the soon-to-be-released Nearby API – used by applications to interact with beacons – brings numerous possibilities for location experiences. I’ve had the chance to explore this API and its documentation. In this post I hope to give an insight into exactly what it is and how you can use it. To really understand how the API works, I decided to build a sample app, allowing me to really test the API’s functionality. Android users can find this on github here. So what‘s new? Previously, a beacon’s sole capability was to emit a signal to state its presence. Using the
This new library introduces several new components previously not available out-of-the-box. Here we take a brief look at what they are, what they do and how we can implement them. I’m a massive fan of material design. Everything about it provides a strong feeling of consistency between applications and as a whole makes them both easier and more aesthetically pleasing to use. Google I/O 2015 saw the introduction of some great new assets to the world of Android — including the new Design Support Library. With the introduction of this, there’s now no excuse not to follow the Material Design Guidelines provided by Google. Let’s take a look at these new out-of-the-box components that we now have available to us. Snackbar Snackbars automatically animate in and out of view Mostly inheriting the same methods and attributes as the Toast component, the Snackbar is a new component that allows us to show a quick message to the user at the bottom of the screen.