-
Notifications
You must be signed in to change notification settings - Fork 437
Feedback disambiguation #420
Conversation
…re/feedback-disambiguation
…eedback scenarios
| // DuckDuckGo | ||
| // | ||
| // Copyright © 2018 DuckDuckGo. All rights reserved. | ||
| // Copyright © 2019 DuckDuckGo. All rights reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Old" FeedbackVC became SiteFeedbackVC and this is actually a new file.
brindy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still testing - few minor pieces of feedback so far...
|
|
||
| let interactionRect = interactionAreaForEditingMode() | ||
|
|
||
| if let rect = scrollView.desiredVisibleRect(forInteractionArea: interactionRect, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
guard and return would be a little cleaner
|
Generally looks good, subject to the feedback already given. There were some changes came up in O-A - you'll see those tomorrow. Also a conflict to resolve. Should be a quick re-review when you need it. 👍 |
|
@brindy Thanks for the feedback! :) This should be ready for re-review. |
brindy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
Thanks! |
Task/Issue URL: https://app.asana.com/0/856498667320406/1109166030178657
Tech Design URL:
CC:
Description:
Updated feedback flow with categories and subcategories to disambiguate the feedback.
Q: When are Pixels fired?
A: Pixels are fired for each "submit feedback" action, which is:
Q: Where we can see feedback?
A: Asana Mobile/AppFeedback project and Grafana
Q: What about old feedback form?
A: We leave it as it is for now.
Steps to test this PR:
UI-related corner cases:
For all of the above, observer if keyboard&scrolling works properly on Feedback Form (in both regular and Negative Feedback->Broken website flow).
Feedback Flow - Category & Subcategory
Feedback Flow - Category & Other
Feedback Flow - Website issues
Feedback Flow - Other issues
Feedback Flow - Positive flow -> Rate app
Feedback Flow - Positive flow -> Share Details
Feedback Flow - Positive flow -> No thanks
Report broken site
Internal references:
Software Engineering Expectations
Technical Design Template