Glassware History and Vision Glassware 2.0 fou
Post# of 392
Posted On: 03/19/2015 11:54:05 PM
Glassware History and Vision
Glassware 2.0 found its beginnings in 2009 as a technology that was created to deliver a fully functioning Android environment to online PCs. That one basic problem premise led to years of development, culminating in the first demonstration of Microsoft Excel on an iPad in 2011. At that point, management realized the importance of what had been created and shortly thereafter, Sphere 3D took aim at delivering the first purpose built application virtualization technology.
Although our thoughts on the best way to commercialize the technology have changed, Glassware has not. At first we thought we had built a way for consumers to view PC applications on a tablet or phone but after taking our software out for a spin with some potential customers, we realized we had much more than that. Glassware had this ability to virtualize apps that to date, had not been virtualizable, and there are many of them. We found an enormous under-serviced market for legacy software applications that we could address; from the likes of Windows XP to proprietary mainframe applications.
As we continued to test the limits of Glassware, we found out how efficient it was, allowing substantially more users per CPU for Windows applications than traditional hypervisor-based virtualization solutions.
We thought about why the desktop exists and started building APIs between the applications running on Glassware. Through these APIs we can deliver a portal with a suite of different applications that can talk to each other, and share data. In other words, we built the desktop workflow without all that unnecessary desktop operating system software and without the need for most of the computer that exists for desktops today.
We have prototyped uniting the server and the local device. In other words we placed Glassware on a laptop and had it act as both server and user device. This could enable software applications to run on a very lightweight device because of the efficiency gained from our Microvisor.
We thought if we can do this with a laptop, how far can we go? We put Glassware on a small chipset with some storage attached (it fit in the palm of your hand). We connected it to a display and a keyboard, and voila we had the beginnings of Glassware on a chip.
We believe in a future where a person could walk around with inexpensive commodity devices that run any software from any operating system or chipset and leverage the cloud for additional horsepower when needed.
Perhaps one day, in a pinch, you could take over the CPU of your refrigerator, stream the display to your TV and use your phone to enter data into your impromptu computer. The third world would never throw another computer chip away again. It could be endlessly recycled as a dumb CPU used by our Glassware 2.0 Protocol.
We know we have some doubters- but that’s ok. Before all the cool, world-changing stuff, we need to continue to virtualize the un virtualizable Windows apps- an app at a time. Come check out our technology and see what it might imply for the future.
Glassware 2.0 found its beginnings in 2009 as a technology that was created to deliver a fully functioning Android environment to online PCs. That one basic problem premise led to years of development, culminating in the first demonstration of Microsoft Excel on an iPad in 2011. At that point, management realized the importance of what had been created and shortly thereafter, Sphere 3D took aim at delivering the first purpose built application virtualization technology.
Although our thoughts on the best way to commercialize the technology have changed, Glassware has not. At first we thought we had built a way for consumers to view PC applications on a tablet or phone but after taking our software out for a spin with some potential customers, we realized we had much more than that. Glassware had this ability to virtualize apps that to date, had not been virtualizable, and there are many of them. We found an enormous under-serviced market for legacy software applications that we could address; from the likes of Windows XP to proprietary mainframe applications.
As we continued to test the limits of Glassware, we found out how efficient it was, allowing substantially more users per CPU for Windows applications than traditional hypervisor-based virtualization solutions.
We thought about why the desktop exists and started building APIs between the applications running on Glassware. Through these APIs we can deliver a portal with a suite of different applications that can talk to each other, and share data. In other words, we built the desktop workflow without all that unnecessary desktop operating system software and without the need for most of the computer that exists for desktops today.
We have prototyped uniting the server and the local device. In other words we placed Glassware on a laptop and had it act as both server and user device. This could enable software applications to run on a very lightweight device because of the efficiency gained from our Microvisor.
We thought if we can do this with a laptop, how far can we go? We put Glassware on a small chipset with some storage attached (it fit in the palm of your hand). We connected it to a display and a keyboard, and voila we had the beginnings of Glassware on a chip.
We believe in a future where a person could walk around with inexpensive commodity devices that run any software from any operating system or chipset and leverage the cloud for additional horsepower when needed.
Perhaps one day, in a pinch, you could take over the CPU of your refrigerator, stream the display to your TV and use your phone to enter data into your impromptu computer. The third world would never throw another computer chip away again. It could be endlessly recycled as a dumb CPU used by our Glassware 2.0 Protocol.
We know we have some doubters- but that’s ok. Before all the cool, world-changing stuff, we need to continue to virtualize the un virtualizable Windows apps- an app at a time. Come check out our technology and see what it might imply for the future.
(0)
(0)