Browse Prior Art Database

A mechanism to inform users that the feature has been modified recently, when the user is in the proximity of that feature.

IP.com Disclosure Number: IPCOM000220503D
Publication Date: 2012-Aug-02
Document File: 1 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

Quite a few times, during the product evolution options/preferences are added to modify a certain behaviour of the product. Just for the sake of example assume that we were doing some task pro-actively like indexing automatically on save. Since indexing is slowing down the system and people want to manually run indexer from a menu, we can provide option 'not to index automatically'. Also in order not to disturb the behaviour for other users, the default behaviour remains the same. This is just an example. Another example is say the in version one of product, I needed to login manually. In version 2 I have provided a preference to login automatically. However I have left the default behaviour same as version 1. For user to know about this new feature ( if he is not the one who has asked for it ), he either need to read the what's new or noteworthy, or help document, or navigate to context sensitive help for that feature. Otherwise he can remain oblivious to this new setting. The problem that I'm trying to solve is to help user discover that something has changed without having to do explicitly something ( like reading help ) and they get to be aware only when the feature is about to be used or is getting used.

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

Page 01 of 1

A mechanism to inform users that the feature has been modified recently , when the user is in the proximity of that feature .

Quite a few times, during the product evolution options/preferences are added to modify a certain behaviour of the product. Just for the sake of example assume that we were doing some task pro-actively like indexing automatically on save. Since indexing is slowing down the system and people want to manually run indexer from a menu, we can provide option 'not to index automatically'. Also in order not to disturb the behaviour for other users, the default behaviour remains the same. This is just an example. Another example is say the in version one of product, I needed to login manually. In version 2 I have provided a preference to login automatically. However I have left the default behaviour same as version 1. For user to know about this new feature ( if he is not the one who has asked for it ), he either need to read the what's new or noteworthy, or help document, or navigate to context sensitive help for that feature. Otherwise he can remain oblivious to this new setting. The problem that we are trying to solve is to help user discover that something has changed without having to do explicitly something ( like reading help ) and they get to be aware only when the feature is about to be used or is getting used.

Let's take the case of manual login feature, which has now been enhanced to auto-login in the background with no visible UI change. Please take this as an example to explain the concept and not the feature itself.

User can read about this in the help.

1.

2.

3.


4.

However 1, 2, 3 require the user to be pro-active and option 4 will require developer to modify it at a lot of places and may not work when their is no GUI as would be the case for the indexing example I have given in section one.

The proposal is to hav...