I know people have worked hard on this, and I know the kind of work that goes into building this sort of thing.
That being said, I like the general feel of it, but it’s too chunky on the real estate.
Positives: shop names and flavor to where we get these things.
Negatives: Busy interface.
The + and - buttons are the kind of feature that people struggle with all the time. There is a group of people who will use them instead of keys for inputs, but they are a tad ugly and detract from the "you are browsing a shop" feeling that this should have. Using <input> type from what I understand eliminates the need for these for some webkits, making these simply a nice-to-have (or disposable, depending on your take).
The second interface item that could be reduced is the static "shop categories" pane. Instead of keeping that list visible at all times, it would feel more elegant to have a mouseover event (or touch on mobile) cascade the nodes out to be visible. This could also be used to add the narrative hooks such as "Visit a different shop" that aren’t being used now due to needing the screen real estate for the crammed interface.
It could also be cleaned up by splitting buying and selling. Right now you list an item at the far low level, and that item contains a buy and sell option in it’s class. This is necessary because "My Things" is (the default) shop class. If My Things was given it’s own class that allowed Sell and shops had Buy options, then when you called to display a new item, it would be context aware. How many items do we own that can’t be purchased anyway, and now we are forced to see grayed boxes with options never to be used.
I only noticed a performance issue on the initial load. It made me think about the loading_large.gif used during calls. If we know we’re going to be having a longer page wait with this new feature, maybe have a more context appropriate gif that ties in with the idea of a Bazaar that is invoked with this tab. Perhaps something like a shop door swining open/closed or handing over/receiving a purse.
Again, I know people worked hard, and this is only the first (public) iteration. Keep up the good work.
Edit: reserializing/reloading the array after a sale is a crime, especially when you have a great flavorful sale message that pops up. This feels like the sort of thing that has to already be on the high priority list for the next release, but you know, feedback.
edited by Theus on 5/30/2013