Method, System and Programming Framework for Sharing User Interfaces (Widgets) between Multiple Devices and Users by facilitating a Central Application Sharing Server
Publication Date: 2015-Dec-01
The IP.com Prior Art Database
The idea is to share a user's set of applications across the set of devices in his possession. A central application server is responsible for distribution to client-side counter parts of the software, which is being installed on each single device supposed to participate.
Page 01 of 4
System and Programming Framework for Sharing User Interfaces
System and Programming Framework for Sharing User Interfaces (((Widgets Widgets) )
between Multiple Devices and Users by facilitating a Central Application Sharing Server
During the last years IT landscapes have changed drastically. Years ago ordinary users usually possessed one single, often stationary, personal computer to manage their personal as well as business-related work. Today, even ordinary, non IT-affine, users possess multiple devices all connected to the Web. Prices for these devices as well as for broadband connections have droped leading to such an accelerated technology adoption. Thus, esp. smartphones, or mobile devices in general, are becoming more and more popular.
As a consequence data consolidation and synchronization has become a more and more prominent problem. Users expect to have access to their entire set of data
whereever they are, at any time using whatever device. But, of course, they do not want to store data redundantly as this would cause it to run out of sync quickly. Thus cloud-based solutions, network-attached storage solutions or simple synchronization tools have experienced a triumphal procession.
What has been considered less is the fact that users are often also using mutiple devices almost synchronously. For instance, users can often be observed to sit in front of a stationary personal computer working with some application while at the same time playing around with their smartphone (or any other - or even multiple other - device(s)). Even if meanwhile data can be shared among devices easily, there are currently almost no solutions (except simple desktop sharing tools like RDC or VNC) allowing to share the applications themselves between those devices.
In an ideal world applications could be shared between multiple devices - and maybe even between multiple devcies owned by different users. Single applications could be installed on just one single device (or a cloud-system) and then transparently shared (or "transported") among one or multiple devices.
Consider the following scenario to understand the rationale behind this approach:
A user Alice being in her office and sitting in front of her stationary personal computer might have started working with some application, e.g. a simple notepad alike application. She needs to finish the document she is working on soon, but has to run into a meeting. Thus she would love to continue writing on this document during said meeting using her smartphone. But she has not installed any proper application on the smartphone to continue writing on this document, nor does she use any data sharing tool (like Dropbox). What she would need is some mechanism to transfer the application (actually the graphical user interface) to the mobile device - without installing anything and without manually transferring data files - simply by sending the GUI to the other device.
With the following invent...