2015 will probably be the year of wearables. As part of an innovation project at BTEXX we tried to unmistify the magic behind it and implemented a couple of Smartwatch prototypes based on SAP Portal backend data, because you do not need to wait for S/4HANA to build a fancy SAP Smartwatch App … 😉
We are happy to share our experience in a “Portal on Smartwatch” blog series. Which we would like to divide in 3 parts:
- Part 1: Introduction and Portal Scenarios on Pebble Smartwatch
- Part 2: One more thing: Portal Scenarios on the Apple Watch
- Part 3: Portal Scenarios on Android Wear
Introduction to Wearables
Current research studies, e.g. from Forrester, have shown that end users and enterprises are interested in wearables and are planning to use them or are willing to invest in business cases based on them. Forrester has published the following 5 predictions of wearables:
- The people want it
- The business wants it even more
- Companies are inventing new business and service models around wearables
- Wearables involve surprises
- The target can be an all-body network
If you are following the smartwatch market, you have probably heard of Pebble. Pebble was successfully funded via the crowd-funding platform Kickstarter in 2012 and till now they have sold over 1 Mio. Smartwatches. Currently they are funding their new edition “Pebble Time”, which will be again the biggest campaign on Kickstarter. On the first day of the campaign they have raised over 5 Mio. dollar alone…
For our development we used the “Pebble Steel” which works as companion watch for Apple iPhones or Android Phones. The watch has a 144 x 168 pixel black and white e-ink display and you can implement the following kind of watch apps:
- Watchfaces: Modern or classic watchface enriched via smart information, e.g. from an SAP System
- Notifications: Push notifications, primarily the Pebble is displaying notifications from the connected smartphone
- Watch Apps: Custom smart watch app implementations based on the Pebble SDK
What I loved during the development/prototyping was the cloud based development environment, without a local setup I was able to develop my first watchface in a couple of minutes and was able to deploy and test the development on the watch. A good start for Pebble developers is the Pebble Developer Site, which offers good tutorials and API documentation.
But now let’s have a look what scenarios/prototypes we have implemented for the Pebble.
Portal Scenario 1: UWL Watchface
Simple UWL (Universal Worklist) watchface implementation, which shows next to the time (it’s still a watch) the total number of open tasks (e.g. 8 tasks) and details of the latest task, in this case a HR time correction request (Clock-in) of Dieter Martens…
Update (08.03.2015) based on the new Pebble SDK 3.0 (Pebble Time, Platform: Basalt)
The screens show the migrated watchface to the new SDK 3.0, which supports colors, and two screens of the BTEXX mobilePortal companion app to show the workflow/interaction:
Update (17.03.2015): Picture of the watchface on the unpublished Pebble Time
Thanks to the Pebble development team I got an picture how our watchface would look on a real (unpublished) Pebble Time. Good to know that the watchface works also on the real watch 😉
Portal Scenario 2: BTEXX mobilePortal on Pebble
This menu based smartwatch application displays the latest news, tasks and services…
The UWL tasks can even be approved/rejected via the watch…
Via bluetooth coupling between the watch and the smartphone the Pebble SDK on the watch can connect via the Pebble Companion App on the smartphone to our REST API of the BTEXX mobilePortal to access e.g. Universal Worklist entries, etc…
I hope you found the provided information valuable! I am looking forward to your feedback or questions!
Stay tuned for the Portal Scenarios on Android Wear and on the Apple Watch… hopefully we will find time to write the blogs in the next weeks…
Based on the connection between user perspective, SAP technology and process know-how, BTEXX implements user-friendly solutions that make companies more efficient and users happy.