|
(0068583)
|
|
dbaz
|
2014-07-10 23:46
(edited on: 2014-07-10 23:48) |
|
At least, the following points should be done before fixing this issue:
* Add ALL the characteristics to the product card view (not only the ones shown in the SEARCH/BROWSE/Receipt)
* Related to issue 27051: Add the capability of open the product card, at least, from the EDIT view. Probably the product image tap solution, the a), be the best one.
|
|
|
(0069436)
|
|
mtaal
|
|
2014-08-17 17:47
|
|
Copying the complete email from David to the issue, we should do as much as possible which is feasible for Q4...
Hi all, after speak with some of you I want to share the first iteration of the Product Characteristic excess data removal from the WebPOS.
Right now all product characteristics are shown in the SEARCH, in the BROWSE and in the ticket. This kills the UI. The proposal is add a flag inside "Product -> Characteristics" to determine if this characteristic should be shown or not in the WebPOS for this product in the mentioned places. This flag, by default, should have the same value than the "Variant" flag, so if the characteristic is variant type it should be shown by default and the other way around.
With this approach, then, there is a relatively important gap: how could a user view all the product characteristics of a particular product from the WebPOS? Imagine the situation where a worker of a shop is walking with a tablet/smartphone (with the WebPOS) and someone asks him about the mAh of a particular battery. In a small shop this could even happen that the guy in the cash register be asked the same question.
The proposed solution for this, is add a way to show the product record/index card, and show all the characteristics inside this view. Btw, this view is the one that is shown in the left when you select the "Plastic Bottle" item in live.builds. Right now there is a configuration that allows specify per product if this view should be shown or not when an item is tapped; this capability/behavior should continue unmodified.
The main difficulty in terms of UX, is determine which is the best way to open this view from the SEARCH, BROWSE and EDIT windows. I can think in several solutions, and depending on your point of view and the effort of each one of them, we will make a decision.
SEARCH and BROWSE cases:
a) Pressing the image of the product: With this approach, if you press the image of the product, you open the index card view, and if you press in the test of the product, it adds the product to the ticket.
b) If you press the whole thing (image + text) it adds the product to the ticket (exactly as it works right now) but if you press during > 1 second, it opens the index card view. Here some deeper tests should be done, because right now in the tablets/smartphone, if you press during > 1 second, you see two arrows and the text-selection mode is enabled. For this solution is a must that this behavior doesn't happen.
c) If you press the whole thing (image + text) it adds the product to the ticket (exactly as it works right now) but if you swipe from the right to the left the whole thing, it opens the index card view. This solution is very nice because it is like if you send something to the left with your fingers, and it is there (in the left) where the index card view is going to be shown, but it should be reviewed how good works with the mouse.
d) Use a context menu. Using the mouse, with the right click should open a contextual menu allowing to open the index card view or add the product to the ticket. Using the fingers, it should use long tap or two fingers tap (to be determined) to open this contextual menu
EDIT case:
a) Add a new orange icon with an "i" icon. Once you press this button, the index card view of the selected product will be opened.
b) When you click the product image, the index card view is opened.
Besides of the election of the way of opening the index card view, it would be pending also how the characteristics should be shown inside the index card view and also I would like to do some small css modifications of the characteristics style to do a better use of the available space. The problem is that I will not be able to prepare this mockups until, at least, next week.
For Q3 I think that it would be enough "just" with:
* Add the flag to show or not the product characteristic
* Add the characteristics to the index card view
* Add the capability of open the index card from the EDIT view.
The small style adjusts and the capability of open the index card from the BROWSE and SEARCH views could be done later.
Also, there are some issues that I have already reported of several UI glitches I have found: http://tinyurl.com/lvery5f [^]
I would like to hear your opinion, specially about the topic of how to open the index card view of a product.
Thanks and regards! |
|
iconInformation.png (1,771) 2014-11-26 18:12