Defining the Architecture of Help in the Future



I am currently working on defining an architecture for uniblue on a greater scope. The idea is to build a help system for the future.

Personally, I paraphrase the mission of uniblue as follows: “Enable consumers to get the outmost of their digital environment.” As usual, every word in this sentence has a deeper meaning. Obviously, we define the target audience – the consumer. What outmost means is somewhat obvious, too.

But digital environment needs to be defined. I think in the hay-days of Microsoft, this used to be the PC. It was the only digital device (on every desktop as stated by Microsoft). Today, it is your mobile device, your tablet, and less and less the PC. With this came the reduction of perceived complexity. I would argue that a major success factor for those devices are the fact that they are somewhat closed. They are reducing the degrees of freedom to configure and being programmed. This also reduces possible failure sources. To be successful in the consumer space, usability is key.

Looking in the future, the digital environment changes yet again. I would argue, it will loose its current face. Future computers will not easily be identified as such. We are talking about wearables like Google Glass, smart phone (but not as we have it today), smart home, smart car, smart city. Some call it Internet of Things (IoT), some call it internet of everything. This provides an explosion of complexity. We have more devices, more platforms.

We are currently laying out an architecture to answer this… great stuff to work on.