WO2008136020A2

WO2008136020A2 - Sharing user interface output

Info

Publication number: WO2008136020A2
Application number: PCT/IN2008/000278
Authority: WO
Inventors: Manohar Swami; P. R. Subramanya; V. Vinay; Setlur Bharani; T. Vasudevan
Original assignee: Geodesic Information Systems Ltd.
Priority date: 2007-05-03
Filing date: 2008-05-02
Publication date: 2008-11-13
Also published as: WO2008136020A3

Abstract

Disclosed herein is a method and system for providing an application on a first device that transmits the user interface outputs of the first device to a plurality of destination entities. The method disclosed herein non-intrusively and conveniently shares user interface outputs in a system where the recipient entities may be heterogeneous, and maybe asynchronous with respect to the transmitting device. A single tap share icon is provided on the first device. A plurality of intended destination entities is identified and confirmed. A click on the single tap share icon triggers the transmission of the interface output from the first device to a plurality of destination entities. The application is not required to be provided on the destination entities. The destination entities comprise servers, applications and physical devices. The first device and the physical destination devices comprise computers, handheld devices, mobile phones, laptops, etc.

Description

4. DESCRIPTION

SHARING USER INTERFACE OUTPUT

CROSS REFERENCE TO RELATED APPLICATIONS

The following patent application is incorporated herein as reference:

This application claims the benefit of the non provisional patent application titled "Sharing User Interface Output", bearing the application number 946/CHE/2007, and filed on May, 03, 2007 at the Indian Patent Office.

BACKGROUND

This invention in general relates to data capture and transmission over a communication network and in particular refers to a method of sharing information presented on the user interface of a device.

Given the shrinking form factor of computing and handheld devices, combined with the increased need for information sharing, there is a need for techniques that provide for improving usability and convenience in information sharing. In the current art, when a user is viewing the display on a computing device, and if the user wishes to share a part or the entire presentation on the user interface with, a recipient entity, the user would first need to open up e-mail, or Instant Messenger or other such communication application. This separate and discrete activity of opening another communication application is inconvenient, and distracts the user away from the context of their work. Also, the communication application may visually mask the current user interface in small form factor handheld devices. There is an unmet need for a method and system that allows a user to share a part of, or the entire information or image rendered on the user interface to a recipient entity in the least intrusive, and convenient manner.

The current art of sharing Information presented on the user interface of a device typically requires a real time connection between the participant entities. Additionally, in order to receive the user interface output, the recipient entities would require a special application installed on them for receiving and rendering the shared user interface output. The current art requires the application to be installed on both the transmitting device and the recipient device.

Hence, there is an unmet market need for non-intrusively and conveniently sharing user interface outputs in a system where the recipient entities may be heterogeneous and asynchronous with respect to the transmitting device.

SUMMARY OF THE INVENTION

Disclosed herein is a method and system for providing an application on a first device that transmits the user interface outputs of the first device to a plurality of destination entities. The method disclosed herein non-intrusively and conveniently shares user interface outputs in a system where the recipient entities may be heterogeneous, and maybe asynchronous with respect to the transmitting device. A single tap share icon is provided on the first device. A plurality of intended destination entities is identified and confirmed. A click on the single tap share icon triggers the transmission of the interface output from the first device to a plurality of destination entities. The application is not required to be provided on the destination entities.

The method and system disclosed herein for providing a single tap share application to share user interface output does not require device compatibility between the transmitting device and the receiving entity. In another embodiment of the invention, the method and system disclosed herein allows the editing of the received user interface output. The received user interface output maybe comprised of active links.

The single tap share application to share the user interface output resides on top of other application layers, thereby presenting the single click share icon on the user interface irrespective of the application running on the user interface.

BRIEF DISCRIPTION OF THE DRAWINGS

FIGURE 1 illustrates an exemplary block diagram representation for sharing user interface outputs of a first device with the destination entities.

FIGURE 2 illustrates an exemplary system architecture for sharing user interface outputs of a first device with the destination entities.

FIGURE 3 illustrates a method of providing an application for sharing the user interface output of a first device with destination entities.

FIGURE 4 illustrates the server architecture configured for the single tap share application.

FIGURE 5A illustrates an authentication procedure at the client device.

FIGURE 5B illustrates a configuration window for sharing user interface outputs with blogs as destination entities.

FIGURE 5C illustrates a configuration window for sharing user interface outputs with blogs as destination entities. FIGURE 5D illustrates the menus or toolbars provided in the single tap share application.

FIGURE 5E illustrates a configuration window for sharing user interface outputs with mobile devices as destination entities.

FIGURE 5F illustrates a configuration window for sharing user interface outputs with email servers as destination entities.

FIGURE 5G illustrates a property editor for a user interface output.

FIGURE 5H illustrates the single tap share icon on an application of the device.

DETAILED DESCRIPTION OF THE DRAWINGS

FIGURE 1 illustrates an exemplary block diagram representation for sharing the user interface output of a first device, which is a client device 101, with destination entities . The client device 101 comprises a single tap share application. The single tap share application facilitates user interface output sharing over a network. The single tap share application resides on top of other application layers of the client device 101. The single tap share application provides a single tap share icon 105. A client user can share a plurality of user interface outputs by clicking or tapping the single tap share icon 105. The client device 101 can transmit a user interface output to a plurality of intended destination entities . The destination entities may comprise servers, applications and physical devices. The applications may comprise websites 103, electronic mails 104, etc. The first device and the physical destination devices may comprise computers, handheld devices 102, mobile phones 107, laptops, etc. An address selection module integrated with the single tap share application communicates with an address database to intelligently determine the addresses of the plurality of intended destination entities. Server pool 106, comprising servers, provides functionalities such as synchronicity, protocol independence and area selections, etc, which are described in detail in the discussion of FIGURE 4. The transmission of user interface outputs may be performed over a plurality of data transmission networks and communication protocols.

The plurality of data transmission networks may comprise a telephony network, a mobile network, the internet or a combination thereof. For example, a client user with a mobile phone may be working on a document on a computer. The client user utilizes a mobile network to establish a communication with a second entity, a computer connected to the internet. The client user clicks the single tap share icon to transmit the user interface output of the mobile phone to the second entity. The user interface output may comprise a screen shot of the document or the whole document. By using the options in a drop down menu of the single tap share application, the client user may select the type of file, such as a screenshot of the document or the whole document.

The single tap share application parses the plurality of user interface output data of the client device 101 to determine the type of the selected user interface output, such as screenshots, hyperlinks, webpage, screenshot with active links, documents, folders, compressed files, multimodal files, audio files and video files. For example, a screen shot with an active link and a webpage which are currently viewed on the client device 101 may be transmitted to a destination entity . It is not necessary for the single tap share application to be installed on the destination entities for the destination entity to be able to run view the user interface transmitted by the client device 101.

The mobile communication standards may include but, is not restricted to, general packet radio service (GPRS), global system for mobile communication (GSM) and code division multiple access (CDMA). For example, consider a document to be transmitted which is currently viewed on the client device 101 where the client device 101 may be a mobile phone. If client user wants to share the current user interface output with a second entity such as a mobile phone, then the client user may utilize a GPRS network to transmit the user interface output. The second entity may utilize a CDMA network to connect and receive the user interface output.

FIGURE 2 illustrates an exemplary system architecture for sharing user interface outputs of a first device 201 with destination entities 202. The first device 201 comprises a single tap share application 204, a database 205 and communication interface 206. The single tap share application 204 facilitates sharing of user interface outputs over a network. The single tap share application 204 is activated using a single tap share icon 105. A user of the first device 201 can share the user interface output by clicking or tapping the share icon 105. An address selection module 207 integrated with the single tap share application communicates with an address database 205 to intelligently determine the addresses of the plurality of intended destination entities 202. If the single tap share application is installed on the destination entity 202, a real time mutual user interface output sharing between the first device 201 and destination entity 202 may be established. The single tap share application may be downloaded from a website. A device provided with the single tap share application may forward the installation file of the single tap share application to other devices over the network thereby enabling two way real timesharing of user interface outputs.

FIGURE 3 illustrates a method of providing a single tap share application on a first device 201 or a client device that transmits the user interface outputs to destination entities 202. The identity of a plurality of intended destination entities 202 is identified and confirmed 301 by a user of the first device 201. A single tap share icon 105 is provided 302 on a first device 201. The user interface output transmission is triggered 303 by clicking on the single tap share icon 105. A plurality of user interface outputs are transmitted 304 to the intended destination entities 202. The destination entities 202 are inherently compatible with the first device 201 for sharing the user interface outputs, irrespective of the configuration of the destination entities 202. The destination entities 202 may comprise a diversity of operating systems, such as Windows operating system (product of Microsoft® Corporation), UNIX® operating system and Linux operating system. This diversity in operating systems is not a restraint for receiving the user interface outputs. The application to share the user interface output therefore does not depend on the device compatibility. For example, if a mobile handset is enabled with the single tap share application, a scribbled text rendered on a display screen of a mobile phone can be uploaded and posted as on a website.

The destination entities 202 may comprise servers, physical devices and applications. The first device 201 and the destination devices may comprise server devices, computers, mobile phones, personal digital assistances (PDA), laptops, or any device with processing, storing and communication capabilities. The server pool 106, through which the client device 101 communicates, may be configured depending on the requirement, feasibility and network environment. For example, the network environment may affect the server pool 106 configuration depending on whether or not firewalls and similar network protocols are deployed on the network environment. In one embodiment, the features of a server pool 106 may be configured on the client device 101. In another embodiment, the server pool 106 is configured as an external entity. In yet another embodiment, the server pool 106 may be configured on both the client device 101 and an external entity.

The single tap share application is configured to allow non- real time and asynchronous user interface output sharing between the client device 101 and the plurality of destination entities 202. Asynchronous sharing occurs if the destination entities 202 are not connected to the network when the client device 101 initiates user output sharing. The single tap share application allows the client device 101 to transmit the user interface output to the destination entities 202 asynchronously after the destination entities 202 become available. The single tap share application may also be configured to allow real time and synchronous user interface output sharing between the client device 101 and the plurality of destination entities 202. The transmission of the user interface outputs may be through a real time communication when the destination entities 202 are connected in real time over the network. The synchronous and asynchronous sharing features may also be configured by using the drop down menu provided by the single tap share application, comprising the single tap sharing attributes. The synchronous and asynchronous communications may be established through, but not restricted to, e-mail, multimedia messaging service (MMS), blog, and instant messaging.

The plurality of user interface outputs that can be shared using the single tap share application may comprise screenshots, hyperlinks, webpage, screenshot with active links, documents, folders, compressed files, multimodal files, video files or audio files. The interface output sharing may be activated through a voice command. For example, a Microsoft Word (a product of Microsoft® Corporation) document currently viewed on a client device 101 is to be transmitted to a second entity. If the client device 101 has to share the current user interface output with a second entity such as a desktop computer, then the single tap share application provides the client device 101 with an option to select the rendered Microsoft Word document for sharing. If this user interface output of the client device 101 is to be shared with a third entity such as a mobile phone, then the single tap share application may automatically transmit a screen shot of the user interface of the client device 101 to the mobile phone.

The single tap share application resides on top of other application layers of the client device 101. The client device 101 may comprise a diversity of applications installed on it. The application layers of the client device 101 may comprise text processing applications, image processing applications, graphic processing applications, browser applications, media applications, etc. The single tap share icon 105 may be a floating icon, toolbar icon or fixed icon. The single tap share icon 105 appears on the screen of the client device 101 irrespective of the application running on the screen. For example, an image which is currently viewed on a client device 101 is to be transmitted, where the client device 101 is a computer. The single tap share icon 105 appears above the image displayed on the screen.

The single tap share icon 105 may provide menus for dynamically setting single tap sharing attributes. The menu provided may be one of a floating window, a tab, a drop down menu, or any other form of presenting a set of choices for dynamically setting parameters. For example, a drop down menu may comprise single tap sharing attributes such as multiple destination sharing, single destination sharing, grouping the destination entities 202, multiple file sharing, single file sharing, request for reply, synchronous sharing, asynchronous sharing, etc. For example, a plurality of files currently viewed on the client device 101 is to be transmitted to a destination entity. The client user utilizes the drop down menu to select an option of multiple file sharing. If the client user wants to share the same user interface output with a plurality of users, then the client user utilizes the drop down menu to select an option of multiple destination sharing. The drop down menu also provides a list of destination entities, a list of destination entity groups, a list of entity addresses for each of the destination users, a list of previously shared interface outputs, time of sharing each of the interface outputs and delivery reports from the destination entities 202.

The single tap share application may require authentication of the user at the client device 101 prior to sharing the user interface outputs. This authentication may be employed by the server to provide server access rights and user interface output transmission rights to the user. The authentication procedure may involve the server requesting the user for a username and password at the client device 101. The authentication procedure, for example, is performed when the user wishes to post a user interface output on a website. The client device 101 and the destination entity 202 may communicate via one or more means, such as instant messages, multimedia services (MMS), electronic mails, blogs and other websites. The user interface outputs of the client device 101 may be transmitted to and uploaded on a website. For example, a graphic image currently viewed on a client device 101 is to be transmitted to a destination entity. If the client user using a computer wants to share the current user interface output with a second entity such as another computer, then communication could be achieved by utilizing electronic mail. If the user with a mobile phone wants to share their user interface output with a third entity such as a personal computer, then the communication could be achieved by utilizing MMS.

In another example, a client user is using a mobile hand held device provided with the single tap share application. The client user viewing a graphic image on the hand held device may post the graphic image on to websites by clicking on the single tap share icon. The websites may comprise blogsites, photo and video sharing sites, social-networking sites, mediawiki sites (the technology used by Wikipedia™) etc. The client user may enter a new website address or select website addresses from the address database 205.

FIGURE 4 illustrates the server architecture configured for the single tap share application. A client user requests to connect to the single tap share service and the request reaches the load balancer 401. The load balancer 401 assigns the request to one of the connection handlers 402. Typically, each connection handler 402 runs on a different machine in order to distribute the load of client connections. The connection handler 402 authenticates the client connection and if valid, the client's presence is intimated to the presence manager 404. The database manager 403 is contacted by the connection handler 402 to collect information on friends and share site information along with any pending off-line messages. The presence manager 404 queries the presence status of each friend. The off-line messages and the presence statuses are then sent to the client user. When the client user wants to share (to a website, email, off-line message or MMS), the request is sent to the connection handler 402. The connection handler 402 contacts the sharelet dispenser 406 in order to complete the share request. The sharelet dispenser 406 is aware of the different protocols needed to complete a website sharing, an e-mail sharing , an MMS sharing, etc. The term "sharelet" refers to the output of the singe tap share application. The sharelet may comprise an image of the screen or screen image with handwritten annotations.

Exemplarily, the share destinations may be configured at the "IShare" website. New share clients may login on the "IShare" website. Additionally, there is a set of social networking features that the client user may avail at the website. The synchronizer 405 ensures that the user information, user messages and message archives at both the website and the share server are synchronized. The server architecture of FIGURE 4 represents the server pool 106, which provides features such as protocol independence, area selection, etc. The protocol independence is achieved by the sharelet dispenser 406, which completes a share process by automatically applying the required protocols for different communications. Remote servers are contacted depending on the geographical locations of the destination entities 202.

FIGURE 5A illustrates an authentication procedure at a client device. FIGURE 5B and FIGURE 5C illustrate a configuration window for sharing user interface outputs with blogs as destination entities. FIGURE 5D illustrates the menus or toolbars, on a display screen of a client device, provided in the single tap share application. The single tap share icon maybe a floating icon, toolbar icon or fixed icon. The menus provide single tap sharing attributes such as multiple destination sharing, single destination sharing, grouping the destination entities, multiple file sharing, single file sharing, request for reply, synchronous sharing and asynchronous sharing. The menus also comprise a list of destination entities, a list of destination entity groups, a list of entity addresses for each of the destination users, a list of shared user interface outputs, time of interface output sharing and delivery reports from destination entities 202. FIGURE 5E illustrates a configuration window for sharing user interface outputs with mobile devices, having MMS capabilities, as destination entities. FIGURE 5F illustrates a configuration window for sharing user interface outputs with e-mail servers as destination entities. FIGURE 5G illustrates a property editor for a user interface output. FIGURE 5H illustrates the single tap share icon 105 on a Windows (product of Microsoft^® Corporation) application.

It will be readily apparent to those skilled in the art that the various methods and algorithms described herein may be implemented in a computer readable medium, e.g., appropriately programmed for general purpose computers and computing devices. Typically a processor, for e.g., one or more microprocessors will receive instructions from a memory or like device, and execute those instructions, thereby performing one or more processes defined by those instructions. Further, programs that implement such methods and algorithms may be stored and transmitted using a variety of media, for e.g., computer readable media in a number of manners. In one embodiment, hard-wired circuitry or custom hardware may be used in place of, or in combination with, software instructions for implementation of the processes of various embodiments. Thus, embodiments are not limited to any specific combination of hardware and software. A "processor" means any one or more microprocessors, Central Processing Unit (CPU) devices, computing devices, microcontrollers, digital signal processors, or like devices. The term "computer-readable medium" refers to any medium that participates in providing data, for example instructions that may be read by a computer, a processor or a like device. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks and other persistent memory volatile media include Dynamic Random Access Memory (DRAM), which typically constitutes the main memory. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Transmission media may include or convey acoustic waves, light waves and electromagnetic emissions, such as those generated during Radio Frequency (RF) and Infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a Compact Disc-Read Only Memory (CD- ROM), Digital Versatile Disc (DVD), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a Random Access Memory (RAM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a flash memory, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. In general, the computer-readable programs may be implemented in any programming language. Some examples of languages that can be used include C, C++, C#, or JAVA. The software programs may be stored on or in one or more mediums as an object code. A computer program product, comprising computer executable instructions embodied in a computer-readable medium, comprises computer parsable codes for the implementation of the processes of various embodiments.

Where databases are described, such as the database 205, it will be understood by one of ordinary skill in the art that (i) alternative database structures to those described may be readily employed, and (ii) other memory structures besides databases may be readily employed. Any illustrations or descriptions of any sample databases presented herein are illustrative arrangements for stored representations of information. Any number of other arrangements may be employed besides those suggested by, e.g., tables illustrated in drawings or elsewhere. Similarly, any illustrated entries of the databases represent exemplary information only; one of ordinary skill in the art will understand that the number and content of the entries can be different from those described herein. Further, despite any depiction of the databases as tables, other formats including relational databases, object-based models and/or distributed databases could be used to store and manipulate the data types described herein. Likewise, object methods or behaviors of a database can be used to implement various processes, such as those described herein. In addition, the databases may, in a known manner, be stored locally or remotely from a device that accesses data in such a database.

The present invention can be configured to work in a network environment including a computer that is in communication, via a communications network, with one or more devices. The computer may communicate with the devices directly or indirectly, via a wired or wireless medium such as the Internet, Local Area Network (LAN), Wide Area Network (WAN) or Ethernet, Token Ring, or via any appropriate communications means or combination of communications means. Each of the devices may comprise computers, such as those based on the InteLRTM., Pentium.RTM., or Centrino.TM. processor, that is adapted to communicate with the computer. Any number and type of machines may be in communication with the computer.

The foregoing examples have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the present method and system disclosed herein. While the invention has been described with reference to various embodiments, it is understood that the words, which have been used herein, are words of description and illustration, rather than words of limitations. Further, although the invention has been described herein with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed herein; rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may effect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention in its aspects.

Claims

5. CLAIMSWe claim:

1. A system for sharing a user interface output of a first device with a plurality of destination entities, comprising:

a single tap share application residing on said first device;

wherein said single tap share application resides on top of other applications of the first device; and

a server pool to transmit said user interface output to said plurality of destination entities.

2. The system of claim 1, wherein said server pool comprises:

connection handlers for authenticating client users;

a load balancer that assigns user requests to one of said connection handlers;

a database manager that maintains information for said client users;

a presence manager that determines the presence status of client users, wherein said presence status is based on a valid client connection;

a synchronizer that ensures synchronization of user information and user messages at both a share website and the server pool; and a sharelet dispenser that applies communication protocols required for sharing a user interface output with the plurality of destination entities.

3. The system of claim 1, wherein said server pool operates over a telephony network, a mobile network, internet or a combination thereof.

4. A method for sharing the user interface output of a first device operated by a user, with a plurality of intended destination entities, comprising the steps of:

identifying and confirming the identity of said plurality of intended destination entities;

providing a single tap share application that is displayed as a single tap share icon on said first device;

clicking on said single tap share icon to trigger the transmission of said user interface output from the first device to the plurality of intended destination entities; and

transmitting the user interface output to the identified and confirmed destination entities, wherein the destination entities need not be provided with said single tap share application.

5. The method claim 4, wherein said single tap share application allows user interface output sharing between heterogeneous devices with a plurality of device configurations.

6. The method of claim 4, wherein said single tap share application is configured to allow non-real time and asynchronous sharing of the user interface outputs between the first device and the plurality of destination entities.

7. The method of claim 4, wherein said single tap share application is configured to allow real time and synchronous sharing of user interface outputs between the first device and the plurality of destination entities.

8. The method of claim 4, wherein the plurality of user interface outputs comprise screenshots, hyperlinks, webpage, screenshot with active links, documents, folders, compressed files, multimodal files, audio files and video files.

9. The method of claim 4, wherein the single tap sharing application resides on top of the other application layers of said first device, wherein applications on the first device may comprise text processing applications, image processing applications, graphic processing applications, browser applications and media applications.

10. The method of claim 4, wherein the single tap share icon provides a set of choices for dynamically setting parameters, said set of choices are presented in the form of floating windows, tabs and drop down menus.

11. The method of claim 10, wherein said drop down menus are provided for the selection of single tap sharing attributes comprising multiple destination sharing, single destination sharing, grouping of destination entities, multiple file sharing, single file sharing, request for reply, synchronous sharing and asynchronous sharing.

12.The method of claim 10, wherein the drop down menu provides for the selection of a list of destination entities, a list of destination entity groups, a list of entity addresses for each of the destination users, a list of previously shared interface outputs, time of interface output sharing and delivery reports from destination entities.

13. The method of claim 4, further comprising the step of authenticating the user at the client device, wherein said authentication is performed to provide server access rights and user interface output transmission rights to the user.

14. The method of claim 13, wherein said step of authenticating is achieved through a username and password provided by the user.

15. The method of claim 4, wherein the single tap share icon is one of a graphic image, or a text.

16. The method of claim 4, wherein the single tap share icon is one of a floating icon, toolbar icon or fixed icon.

17. The method of claim 4, wherein said user interface output is shared synchronously if the destination entity is in real time communication with the first device and the user interface output is shared asynchronously if the destination entity is currently not in real time communication with the first device.

18. The method of claim 4, wherein destination entities comprise servers, physical devices and applications.

19. The method of claim 4, wherein said first device and destination devices are server devices, computers, mobile phones and personal digital assistants.

20. The method of claim 4, wherein said transmission is enabled by instant messaging services, multimedia messaging services and electronic mails.

21. The method of claim 4, further comprising a mutual real time sharing of the user interface outputs between the first device and a destination entity if the single tap share application is installed on said destination entity.

22. The method of claim 4, wherein the single tap share application may be activated through a voice command.

23. A computer program product comprising, computer executable instructions embodied in . a computer-readable medium, said computer program product including:

a first computer parsable program code for a single tap share application that is displayed as a single tap share icon on a first device;

a second computer parsable program code for identifying and confirming the identity of a plurality of intended destination entities;

a third computer parsable program code for triggering a transmission of user interface outputs from the first device to said plurality of intended destination entities; and

a fourth computer parsable program code for transmitting the user interface output to the intended destination entities, wherein the destination entities need not be provided with said single tap share application.

24. The computer program product of claim 23, further comprising a fifth computer parsable program code for configuring non-real time and asynchronous sharing of the user interface outputs between the first device and the plurality of destination entities.

25. The computer program product of claim 23, further comprising a sixth computer parsable program code for configuring real time and synchronous sharing of user interface outputs between the first device and the plurality of destination entities.

26. The computer program product of claim 23, further comprising a seventh computer parsable program code for activating the single tap share application through voice commands.