Today Salesforce.com offered a formal update on its Salesforce Wear offering (which I wrote about at its release here). Salesforce Wear is a set of developer tools and reference applications that allows enterprises to create applications for an array of wearable devices and link them to Salesforce1, a cloud based platform that connects customers with apps and devices.
Salesforce’s entry into the wearables space has been both bold and well-timed. Salesforce Wear constitutes a first mover in the wearables platform space; while Android Wear offers a platform, it only reaches Android Wear based devices – unlike Salesforce Wear, which operates across a wide array of wearable devices. While it’s early to market, it’s not too early: Enterprises in a wide array of verticals are leveraging wearables worn by employees or by customers to redesign their processes and customer experiences, as I have written.
On June 10, Salesforce.com announced Salesforce Wear, a bundle of free tools and reference applications aimed at evangelizing the power of enterprise wearables. The offering supports six different wearable devices, each with its own open-source reference application to help developers design and build wearable apps that connect to the Salesforce1 platform.
Salesforce Wear has the potential to turbo-charge the growing market for enterprise wearables. Enterprises using Salesforce Wear will gain tools and reference applications that immediately apply to six wearable devices: three smart watches (Pebble, Samsung Gear, and Android Wear), plus Google Glass, the Myo armband, and Bionym’s Nymi authentication device.
Some of the reference applications are pure enterprise/B2B workforce enablement applications, like the Google Glass application for oil rigs, which can be generalized to other field service scenarios (and which, conceptually, I have written about before). Salesforce Wear’s app facilitates real-time field actions by providing schematics of the equipment being serviced, offering a view into the full service history of the equipment, and connecting field workers to colleagues for real-time collaboration. All in all, the reference app helps field workers fix problems more quickly and effectively.
Salesforce Wear's Casino Reference Application with the Bionym Nymi Band. Source: Salesforce
It’s been a couple of weeks since Dreamforce ended, and in between client engagements and research I’ve had some time to digest the event — so I’d like to share some lessons from Dreamforce 2012:
1. If you build it they will come (no, really)
Setting a record for attendance at a vendor-led technology conference, Dreamforce 2012 was BIG. With over 90,000 attendees, it was hard not to be impressed by the logistical efforts taking place behind the scenes. Think of it ... How do you feed 90,000 people in a couple of hours? Not to mention the enormous bandwidth issues for Wi-Fi and even 4G providers when you put this many social people together. Back when I was running marketing at a tech vendor, I was planning events based on how many square feet of conference space we would we need ... the Salesforce team plans on a scale of how many conference centers will they need. This was an amazingly large event with very few crowd control issues. And the mobile app for the conference made everything much easier, despite occasional Wi-Fi outages. My hat's off to the conference team at Salesforce for pulling this off.
2. Salesforce.com has adopted a business strategy which embraces social business
On 9/9/09 Salesforce.com announced the launch of Service Cloud 2, a new set of three collaborative offerings: Salesforce Knowledge, Salesforce Answers and Salesforce for Twitter.
With Salesforce Knowledge companies can share data in the Service Cloud, Salesforce Answers enables companies to create communities to capture knowledge and Salesforce for Twitter allows companies to screen and participate in the 45mio user Twitter community directly from the service cloud.