Angelo Santagata's Blog

Smart watches in the enterprise?

Angelo Santagata

Although smart watches have been around for a couple of years (Sony had a v1 2+yrs ago, Pebble, Samsung gear, Google wear etc) now that Apple is poised to deliver its iWatch the worlds gone crazy about them.. or has it??
Personally I'm still struggling to identify the “killer” SmartWatch App where I would start to wear a watch again (I stopped wearing watches the day I discovered my Nokia mobile had a clock)..
One area which I totally “get” is Healthcare.. In that the watch/wearable device can monitor my steps, heart-rate, stress levels (skin resistance) etc… but what about the enterprise???

Anyway, some friends of mine at Oracle HQ (Jeremy & Ultan) have done some awesome R&D in this area, gotten hold of some watches, prototyped some ideas and come up with some compelling ideas.. ..

Is “glancing” and “glance-able” apps the game changer??
You decide..


Join the discussion

Comments ( 4 )
  • guest Wednesday, April 1, 2015

    Link is broken

  • angelo Wednesday, April 1, 2015

    Fixed, thanks!

  • Smart Watches Monday, January 25, 2016

    Where do we really draw the starting line when it comes to smartwatches? Like smartphones, there have been hints of a mobile device that can do so much more even before Apple put out the very first iPhone. To mark the starting point, we'll have to define what a smartwatch is. We'll try to keep it simple. It's a wearable device that hooks up with a smartphone for added functionality. Alternatively, it can connect to the Internet directly but still exhibit smartphone-like behavior. <a href="http://www.latestone.com/smart-watches">Smart Watch</a> This rules out many older devices in the early 2000s. And, of course, it needs to look like a watch, which excludes smart fitness bands.

  • tissot uk Tuesday, May 10, 2016

    Very interesting blog, looking forward to more wonderful!

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.