First, let's acknowledge that "Mobile" and "Internet of Things” (or IoT) are very large and quite separate technology domains. However, the way current market is evolving, I see some overlap, as shown in the attached graphic (click to enlarge).
At the intersection of Mobile and IOT
Wearables to a large extent fall under the rubric of IoT-oriented, connected devices. However, some fall at the intersection of Mobile and IoT, and you'll want to consider them as part of your overall mobile strategy.
Consider for example devices that are linked to your mobile phone or tablet in some way. Smart watches, such as Apple Watch, are a prime example of this category since you use your mobile phone to provide content and services (e.g., GPS) to the watch. Other types of wearables, such as activity trackers, require an app on your mobile phone for initial configuration and setup.
Besides the ability to be able to deliver content and services to these devices, another example is the ability to push information from these devices back to your mobile phone. Analyzing data from your morning bike ride on your phone, or getting a notification on your mobile app as you check out an exhibit in a museum, represent a couple examples here.
Tool support for wearables?
So as you evaluate tools for enterprise mobility, you should consider what kind of support they provide for phone-connected wearable devices.
Start with what kinds of devices they support. As an example, IBM’s MobileFirst provides some support for Apple Watch and Android wearables. Many other mobile app development platforms also support some sort of content delivery to wearables.
Note however that most of these tools consider wearables as an extension of your mobile device. While that is a good way to quickly scale up your device-delivery capabilities, it could also become a major limitation if you wanted to support wearables more generally.