As I prepare for my talk in November at Better Software East on Mobile Wearables, I’m confronted with the need to constrain the talk to 1 hour. Its a big subject. Mobile wearables are just one sub-category of the Internet of Things, which is generating a huge amount of interest and press.
So what is key about mobile wearables that we developers and testers should be concerned about?
- Social Connectivity – Some things are for sharing with your friends and others aren’t. Any application that could enable social connectedness automatically breeds sense of community, something that all humans need and desire. This leads to user satisfaction. Otherwise we’d all be living by ourselves.
- Integration – Depending on the application, and I say that loosely because hardware and software are now fusing together via embedded more than ever before, the app will have to interface with many other apps in order to create an optimal user experience. No one wants to use an app that doesn’t tie into the rest of their apps (life).
- UX – This will be derived from many of the other factors, but here I want to emphasize satisfaction. Satisfaction will be dependent on how well the app understands the user and creates a personalized experience based on predictive and anticipatory presentation to the user. We all want to be understood…
- Trust and security – We want users to trust our app like their best friends; easy to get along with, straightforward, easy to understand and keeper of our secrets…
- Data integrity and privacy – Of course we all want our data to be private like on iCloud right? What’s more important is that the data be timely and accurate. Otherwise all the predictive and anticipatory analytics are for nothing.
There are probably several other bullet points that I haven’t mentioned either because I forgot, or just overlooked due to the nature of a blog being a stream of consciousness rather than a well organized academic paper. But its clear that mobile wearables development and test issues have many permutations.