Heart rate monitors have made their appearance a long time ago, but lately, with the increased number of gadgets carried around by end users, they have become a trend.

Lots of mobile phone applications exist that take advantage of heart rate monitor data, combining it with gps data to represent your sporting activities. The main problem with this kind of applications is that the data remains in your mobile phone. The other option is to export the data manually, share it with your trainer who will have to import it in his application and then make their recommendations.


Imagine this data being stored on your device in a generic way that is easily accessible by all applications you have (the ones that have been granted the required permissions) or even shared with anyone you want, so his applications can take advantage of it.

Enter the webinos heart rate monitor application! This innovative application allows you to monitor your heart rate and graphically depict it on your smartphone, while sharing this information with your personal zone’s devices. You can even share this data easily with someone else’s device.

If you were lucky enough to be present on our launch day, you could have witnessed my colleague Ziran (and actually the developer of this awesome application) wearing the heart rate monitor and having her data streamed live to her trainer’s computer.

So here’s some jargon in order to bring you up to speed with the terminology. The personal zone hub consists of your own devices and is named PZH in the webinos eco system. Each device is a personal zone proxy, also known as a PZP. Each person has his own PZH, so in order to share information between people, their PZHs must be connected. The dataflow of the heart rate monitor information is depicted below:


So coming back from the interlude, you may still have the question, why do I need to share this information in my personal zone? The idea is that if you can share the information, you can use multiple devices to do a task. So, although it’s pretty nice to have a small graph on your mobile phone of your pulse while running, it’s very difficult to see a map that depicts your heart rate level in a two hour walk (unless you are up to zooming in and out over and over again). Instead, you can use your television to display this map and since pitching on it would only leave you with some finger marks and the map would not zoom in (unless you have a touch screen), you can use your tablet or your phone to do this action instead. webinos provides all the required infrastructure to do this in a secure manner, very easily (both from the developer and the end user perspective).

This functionality is also demonstrated in various other demos, what is truly unique with the heart rate monitor demo is that this is the first one to show that your data can also be shared with your friends and in this particular occasion your trainer. After setting up the appropriate permissions, your trainer is allowed to receive a live feed from your heart rate monitor and comment or even warn you in case you overdo it. For developers, this can be done easily using the events API. You simply send an event, which is routed to any app that is authorized and waiting for it. Moreover, if you combine this functionality with the context API, the trainer will be able to retrieve historical data and combine it with contextual information concerning  the user in order to diagnose potential health hazards, like the fact that he was clubbing all night long and the next day went running for two hours. Thank god I haven’t given access to this kind of contextual information to my trainer 😎 .

Hopefully, this blog post gives you a good idea of how the webinos platform can help you with things in your life. Combine the information produced from your devices and share it with whoever you want, while keeping absolute control over your personal data.