search

MarketplaceUX / marketplace-community-editorial

The Community Editorial project for Firefox Marketplace Feed.
http://marketplaceux.github.io/marketplace-community-editorial/
2 stars 2 forks source link

Mockups: abuse patrol #20

Closed brampitoyo closed 10 years ago

brampitoyo commented 10 years ago

Here are some early mockups for the feedback reporting interface:

feedback-reporting-mockup

Up next: dashboard/triaging interface.

mhanratty commented 10 years ago

Great idea moving away from a blank text field that is our current Report Abuse UI. Be good to coordinate with changes to our feedback form (https://bugzilla.mozilla.org/show_bug.cgi?id=982831). Menlinda did some designs for the feedback form for the desktop redesign. It lines up with your Option 3: https://www.dropbox.com/sh/5zwemf12okf6p23/AABc7DChsjpeU-LA4kNygL6qa?dl=0

brampitoyo commented 10 years ago

Reporting user review

Have a look at this idea of flagging user review (the category select interface is still in development and might change).

A user review can be either hidden/deleted, or reported, for these reasons:

Report Success message What it means
App listing/content is misleading Review team has been notified The flagged review is filed in Reviewer Tools; the review team will be able to look at it and decide what to do with it.
App content is abusive/inappropriate IARC has been notified The flagged review is sent as an email to IARC
App has technical problem Developer has been notified The flagged review is sent as an email to the app developer

review-and-feedback-ui-v1 0

brampitoyo commented 10 years ago

Submitting app feedback

App feedback is submitted using the same categories as user review reports.

Feedback category What it means
App listing/content is misleading The feedback text filed in Reviewer Tools; the review team will be able to look at it and decide what to do with it.
App content is abusive/inappropriate The feedback text is sent as an email to IARC
App has technical problem The feedback text is sent as an email to the app developer

Feedback about misleading listing/content is filed on the Reviewer Tools. A user review that’s been flagged as having misleading listing/content is also filed on the Reviewer Tools. After all, they’re the same content.

The UI flow goes like this:

reviewer-tools-feedback-dashboard

What’s not yet clear from this UI flow is where the user feedback (whether it’s a feedback that’s submitted, or a user review that’s reported) should be positioned.

One thing for sure, viewing the feedback should eventually the reviewer into to ask: do we want developers to provide more information?

So the interface to view feedback, and the interface to ask for more info, should ideally be located close to each other.

brampitoyo commented 10 years ago

The UI flow for both reporting user review and submitting app feedback has been merged and updated.

(Unfortunately, GitHub won’t display the image here, so I’m linking directly to the file below)

http://f.cl.ly/items/0b2Z3y0L1B2C1P0c0m0G/report-review-submit-feedback-ui-flow-v1.0.jpg

It now includes decisions that the review team will need to make at the end of the process. It addresses concerns from @eviljeff.

For the customer journey map of this UI flow, have a look at issue #15.

eviljeff commented 10 years ago

@brampitoyo :thumbsup:

brampitoyo commented 10 years ago

Mockups from this issue has been posted on the spec page: http://pwalm.github.io/marketplace-community-editorial/concept-feedback.html

For further comments, please open a new issue.