Good question. Over the past 5 years we have seen a number of failed attempts at bringing new devices and applications to market. From web tablets and interactive television to Internet telephony and the servers that feed them, the reality is that these products have failed because the cost of producing them has far out weighed the value they deliver. And that is not because the vision of a world of connected, communicating devices is flawed. It is because the software needed to build these products has been absent.

So what makes Strings so special? Unlike traditional platforms, which are based on 30 year old architectures, Strings was designed from the ground up for a world that is increasingly networked, increasingly digital and ultimately connected. Strings is entirely different because Strings makes a radical departure from the traditional application architecture where developers build monolithic applications that communicate only through cumbersome interfaces. In Strings, applications are broken into discrete services that can exist locally or across a network and Strings, in turn, dynamically combines these services at runtime to provide end application functionality.

As a result, applications are dynamic so they change with the way you use them. They work together to share resources, computing power and content and they are efficient, predictable and responsive. All this means OEMs and ISVs can build solutions that do more, and ultimately users can expect them to cost less.

So why Strings? Because it is a promise that is available today... a promise that will change the way we provide, exchange and receive digital information forever.