Abstract: There is provided a system and method for exchanging messages between a native application and a web browser using a server. The server configured to receive a message from a communication application of a first client device for delivery to the second client device, determine if the second client device includes the communication application, create a link to a webpage for rendering the message on the webpage when the second client device does not have the communication application, transmit the link to the second client device, render the message on the webpage to the second client device in response to receiving a request, receive a reply message from the second client device, and transmit the reply message to the first client device for rendering by the communication application. The message from the first client device may include a multimedia message, such as an animated avatar with a lip-sync audio.

Abstract: There is provided a system and method for exchanging messages between a native application and a web browser using a server. The server configured to receive a message from a communication application of a first client device for delivery to the second client device, determine if the second client device includes the communication application, create a link to a webpage for rendering the message on the webpage when the second client device does not have the communication application, transmit the link to the second client device, render the message on the webpage to the second client device in response to receiving a request, receive a reply message from the second client device, and transmit the reply message to the first client device for rendering by the communication application. The message from the first client device may include a multimedia message, such as an animated avatar with a lip-sync audio.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.