Depending on the type of records being compared, the comparison view can either add value by highlighting the differences between similar items or provide very little value by comparing items that share very few common fields. For instance, comparing two similar television sets will help the user by making clear the differences. On the other hand, comparing a television set to a toaster would be meaningless, as there are almost no common attributes. Maintaining separate comparison lists for different types of records or different segments of a catalog can help to avoid meaningless comparisons by only displaying products together in a comparison view if they come from the same group.
What this means is that the system will maintain a separate comparison list for each unique user for each product category within the site. For example, if a user selects digital cameras for comparison and then switches categories to look at vacuum cleaners, the cameras will no longer appear in the comparison list. If the user later returns to digital cameras, the previously selected cameras will be restored to the comparison list.
This increases the amount of development work for the application, but it can support user scenarios where a user is likely to shop for different types of items, as in a department store. Consider the tradeoffs for your project when planning the implementation of a comparison feature.
Comments (0)
Leave a comment...