I see it there, YES :)
But it doesn't seem to be used as much as I thought it would be...or I guess as much as I hoped. BUT to be fair here- There are a handful of vendors that do use it regularly (much appreciated), and it seems things have improved there. I think having it collapsed makes for a more attractive page, but may lend to an "out of site out of mind" thing???? May not seem significant, but if you expand those hidden fields a few times only to find most or all as "unspecified", see more how easy would it be for folks to naturally lose focus or ignore that field all together? Especially with 26 more appealing products on the page yet to look at?
It seems- were I a vendor I would be increasing the integrity of my product by adopting this practice, regardless if there were fields I occasionally had to answer something less than favorable. It still says something positive though....I doubt it's going to kill the sale. It sends clients home with toys for their members, better informed. It goes hand in hand with the whole packaged documentation thing, which I tend to put a premium on. It seems everyone wins with every little move to grow a better informed community.
But- I'm not a vendor so....I don't know how it all works...
If those fields had to be filled out every time a product was updated- that prolly wouldn't be so fun....Does it work that way?
If so, I guess that would probably discourage it's use....
On the other hand- if it was mandatory- it may promote a more favorable updating practice among vendors......
I like to have the latest greatest......who doesn't?
I love seeing new products hit the Boonex Market...
FIRST STOP- the "Latest" tab...
NEXT STOP- the "Recently Updated" or "Updated" tab depending on which page I'm on....
BUT
I don't like so much spending an excessive amount of time trying to determine what exactly has changed with the modules I've invested in....
At times there are improvements/fixes without a product version change/update...
Other times, there are updates that are for the sole purpose of better marketing a vendor's product...better description or additional uses....(Hell- sometimes I can't even see what has changed since the last time a product was posted/updated 2 weeks earlier)
HEY- I totally dig discovering new uses or better ways to present or explain a module to members and visitors....
BUT- Tis the season for upgrading and nailing down 7.1, and it hogs a lot of time. I'll come back during MY marketing phase and check out the Vendor's new product verbiage.

Since the word "UPDATED" has multiple meanings and used so loosely-
It would be cool if there was an easily visible indicator denoting the type of update which has qualified a product to appear under the "Updated" tab---->File/Code Changes or Marketing Changes....
Come to think of it, Implementing- *****- "views" count for every product*** may actually exacerbate things, depending on how that is setup...
Who wouldn't want hella views on their Market Items?
Any Webmaster who subscribes to the idea of keeping their code/modules updated and monitor for changes with the products they've purchased may well be more or less actively marketing for the Vendors by racking up product views each time it appears among the "Recently Updated" products.
I don't mind helping out the Vendors I buy from....
But it would be cool if I headed back to the house with something more likely to improve my member's experience....that's likely gonna be code-related changes.
Right now- getting our sites updated...for many of us- getting our site up on her feet after a fresh install...is likely at the top of our list of priorities and better serves the interest of our members.
Vendors competing for highest #views# may feel compelled to get their products at the top of the list with the most traffic- (that's probably the "Recently Updated" list)

Am I wrong? Does it seem "Recently Updated" stands to lose it's initial purpose if it becomes the primary avenue for gaining views?
I mean- Wasn't that tab initially designed for customers to more easily keep track of code-related updates ? Or no?

IDK....I don't wanna be negative....but it does seem it would be better for everyone if the two main types of updates could be determined at a glance, and offer a more accurate view count, and also cause the view count to have more value as well???