Splashtop Streamer was already compatible with Windows 8 like most Windows 7 applications. But as always it lacked any custom gestures for use in actually interacting with the OS being streamed, just swipes for the app.
Splashtop has now been updated to support certain Windows 8 gestures allowing a chance to try the touch-centric Sindows 8 Consumer Preview on an iPad or Android tablet.
"Slashtop has released a $25 remote desktop client that brings the Windows 8 experience to the iPad. Aimed squarely at developers, the Win 8 Metro Testbed app offers support for Windows 8 Metro UI gestures in what appears to be a fast, low latency environment.
It all looks very convincing, but this isn’t the real deal by any means. Remote desktop software requires a constant web connection to a running host computer, so you won’t necessarily be taking Windows 8 on the go just yet.
That said, this will be a boon for developers who couldn’t make it to Microsoft’s BUILD conference last year, and lack access to a Windows 8 development tablet to test the software they’re creating. Windows 8 is likely to drop sometime before the end of the…”…
We were given no indication of how it might function, just how it might be used.
This is great and all but how might it be functional in the world of limited battery life that we live in these days?
Below I have detailed a few expected specifications for the device that outline how it might preserve battery power for the long term use like seen in the video above.
Pardon the informal, note-style writing. It’s a work in progress.
Battery, Radio(s), sensors, “Display”
Battery: 80 percent of device, possibly new high capacity/graphene technology
Radio(s): Bluetooth? Wifi:yes, LTE:including voice so no dedicated voice network,
Antenna: the large flat long outside of the device farthest from the head ,it would be the chassis that doesn’t ever touch skin
Operating system: will be serverside, obviously a striped down android OS, but so the device doesn’t have to store the operating system files or power hungry processors, it can be streamed for the entire duration of its use.
Otherwise the device would constantly be consuming battery on location services and processing other tasks. This would normally drain even a decent battery pretty quickly, never mind a small one .
If the OS was rendered server-side at Google, and streamed, it would reserve all that power to make the device just an assimilation of censors sipping battery by sending compressed data back and forth over the network, sending output directly to a low powered tiny projection on the users eye.
Reserving the battery for just sending output from its sensors to Google’s servers for processing and back to your device via a compressed transmission direct to the out put on your eye to wait for more input.
You might compare this to Siri or OnLive.
Operating System Cont: A striped down version of android. A lean kernel, no local processing, Optimized for smart sensor usage and network traffic handling and (de)compression.