Can't see asset comments
I have a Note and a Movie. Both have a single comment. Neither guest nor admin can see comments by default in any view - Blog, Chronological, Media, or Page. To see a comment, the user must know that they need to mouseover the asset, pull down the list, and select Comment. They must further be educated that if there is no quote bubble over the asset that there are no existing comments. It didn't used to be like this.
Preview mode doesn't show comments either. The user must essentially go to add a comment, or use the Go To File option before they can see existing comments
If I email an asset to a drop, the subject and body of the email are used to explain the asset. If all someone sees is the first frame of a video they have no idea what the asset is about, and I don't want to require people to go through a multi-step action on every asset just to see if they're interested.
What can be done to show one, all, or some pre-defined number of comments by default for each asset?
Thanks!
Preview mode doesn't show comments either. The user must essentially go to add a comment, or use the Go To File option before they can see existing comments
If I email an asset to a drop, the subject and body of the email are used to explain the asset. If all someone sees is the first frame of a video they have no idea what the asset is about, and I don't want to require people to go through a multi-step action on every asset just to see if they're interested.
What can be done to show one, all, or some pre-defined number of comments by default for each asset?
Thanks!
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Starbuck,
What we've chosen to do is to keep the thumbnail as unobstructed as possible. After there's a comment left on the file, the hover over becomes displayed with the corresponding number of comments contained within.
It sounds like what you are getting at is really more of a labeling system, rather than comments. This is something that could potentially be accomplished with the new grouping feature within /media view. You can organize your files in a customized group, rename it, give it a new icon, etc. The /system view is also a really good way to display your drop's content with all of the files' important information exposed.
We are looking into other ways to display content so this input will be brought into the equation.
As always, thanks for your detailed question. We really do live and die by pulling in the features that the community needs and making sure to tailor the drop.io experience in the most thoughtful way.
Best,
Peter F.
drop.io
The company says
this solves the problem
-
Inappropriate?I appreciate the thought process but there's a usability issue when someone looks at a UI and can't figure out what to do without being told.
I'm not looking for a new feature. I want to point people to a web page and get them interacting with it without me having to point them to a separate page of documentation.
Try this usability experiment. Create a drop with a couple assets. Add a comment to one asset but not to another. Now ask some people who have never seen drop.io before to comment on the assets in the UI. See how long it takes for people to figure things out without you telling them where everything is. If you need to tell the user anything, the test fails. If it takes them more than (arguably) 5 seconds of mousing around, it fails. If they can't find help to tell them what to do, it fails. If you consistently point people to a page and they "get it" without any wasted time or extra instructions, then I'll have to re-think about how much faith I put in the average website user.
The bottom line is that no UI should have too many hidden ways to access primary features. In some ways I think drop.io was designed to be a little too clever - designed for "us", not for "them".
I'd love to see people post results of the above test here, and please include some indication about the type of person doing the testing: younger/older? developer? internet savvy? complete noob? occasional surfer? ...
I’m sorry the discussion is on something so fundamental
Loading Profile...



EMPLOYEE