Browse Prior Art Database

Customized container which enables user to select features from products of different brands falling under the same domain. Such approach would help in creating a customized product for individual use which would fulfill users usability, accessibility and productivity improvements needs.

IP.com Disclosure Number: IPCOM000230815D
Publication Date: 2013-Sep-13
Document File: 9 page(s) / 104K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is the proposal for a Customized container which enables user to select features from products of different brands falling under the same domain. Such approach would help in creating a customized product for individual use which would fulfill users usability, accessibility and productivity improvements needs.

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

Page 01 of 9

Customized container which enables user to select features from products of different brands falling under the same domain . Such approach would help in creating a customized product for individual use which would fulfill users usability , accessibility and productivity improvements needs .

Problem Statement

Today, users migrate from one product to another in search of their needs in usability, accessibility and need improved productivity areas. These three areas are the key towards the success of any product. User never finds all his needed features in one product and thus has to limit his scope and live with the latest in hand. User works with a particular product for some time, practices some other product from same domain later in his carrier, gets impressed and migrates to that new product. As soon as he starts using the product, user starts comparing his earlier used product which had certain key features which used to improve his productivity / were easy to use / were easy to access, but now again he has stay limited with the features and hick-ups of this product.

Proposed solutions

Disclosed article which proposes to build a "Container" which would be deployed along with the logging mechanism. Container would keep on automatically updating the log generated with the feature details. Even if the feature does not support install / un-install facility on one click, container will be providing this option for every feature of the container.

Benefits of the container


- Choose what is required and pay only for features user picks.


- Choose from a variety of brands from same domain.


- Flexibility of developing a feature in any IDE and then integrating that in this container.


- Container helps to combine / integrate open source features.
-- Individual installed features can be un-installed when not required and can be installed again when required. This would be container provided install / uninstall facility.
-- To provide individual theme /skins setting for individual feature.
-- User gets an option to integrate the entire help contents at once place even if the features are delivered from different vendors.
-- User gets an option to add new help for his / her developed feature.

Components:


- Container for features to be integrated.


- Logging mechanism to analyze details of the features.


- Individual install and un-install for the features.

Scenarios which explain the regular problems faced

1


Page 02 of 9

Case1: User pays for the entire product and uses only certain features from the bundles. Also with that bundle, user has to invest lot of hardware space and memory to hold the product and its features. This container would facilitate the user to create his own application by just selecting a set of features which interest him the most, increase his productivity and are useful for his business goals. User just pays for the features he selects from a huge product.

Case2: Based on case 1 usage, user has selected certain features whic...