Browse Prior Art Database

Method and System for dynamic updating a pluggable User Interface Disclosure Number: IPCOM000247628D
Publication Date: 2016-Sep-21
Document File: 4 page(s) / 120K

Publishing Venue

The Prior Art Database


A smart and effective way for managing a pluggable User Interface

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 4

Method and System for dynamic updating a pluggable User Interface

User Interfaces running on Laptops, tablets and smartphones devices are becoming day by day more complex and more integrated with cloud and social applications. They are formed by pluggable and re-usable components (widgets, …) that can be composed and customized in order to present to the End User the best User Experience.

Today this composition is performed manually:
1. when the product is installed the first time

2. at runtime when the Administrator / User apply additional customizations

3. when the product it upgraded to a new version

but what is missing is the capability to upgrade/update the User Interface based on the current usage (User Scenarios performed) of the application and linking the usage to the best new pluggable components that have been released by the time

What is proposed in this article is a mechanism to propose and perform a smart management of the composition of a user interface based on:
· Customer scenarios and usage
· User Profiling
· UI components already available and just released/updated
The changes are defined in policies and they can be performed automatically or through a proper notification sent to the Administrator.

The goal is to propose and update new user interfaces that can be optimized and tailored to the users and the scenario performed in order to get a better user experience, usability and performance.

Overview of the Solution

Before describing the solution let's introduce some basic concept and terminologies that will be used in the document.

The User Interface (UI) is made up of: · layouts

· gadgets

Layouts define how the UI will look like, using different strategies like:
- a grid system, composed by rows and columns
- a tile system, composed by square or rectangular areas the fills the available space on the screen.

Example grid layout:





Page 02 of 4

Example tile layout:





Layouts do not convey any information as instead gadgets do: a gadget is responsible for rendering information in the area of the screen it is assigned to and to react to events, such as user or system interaction.

Each gadget is described by some metadata, such as:
- id
- name
- rendering behavior for grid system (like minimum size 1 row 3 columns) - rendering behavior for tile system (like small, medium, large)

Given the above, a UI page can be defined declaratively as the composition of gadgets within a layout, and then an application is served to the users as a set of built-in pages, i.e. as layouts and gadgets together. All the pages are fully customizable in the sense that users can add/remove gadgets and layout items in order to optimize their experience.

The infrastructure serving the UI is capable of registering a wide set of information about the users, how they interact with the system and how their pages are customized: profiling data is collected each time a user connects to th...