876031 - UX work - Crash report pages

Status: RESOLVED FIXED

(Firefox for Metro Graveyard :: Browser, defect, P1)

Description

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

This bug is created to track the UX design work for 831972: Story - Crash reporting.

Comment 1

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

Attachment: [Mockup]Crash reporting_0606

This is the version 1 of Crash report design.
Will probably have small iterations on the copy and privacy statement after reviewing with UX and Privacy team.

But feel free to post your feedback in this bug!

Comment 2

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

Attachment: [Mockup]Crash reporting_0606

Comment 4

[Robert Kaiser]

Note that B2G has practically the same work flow there, so you might be able to borrow some ideas/text/flow-design from that.

Comment 5

[Robert Kaiser]

(Needless to say that all those crash reports will be vastly inferior to Windows desktop crash reports in terms of data we get out of there, because we'll be missing comments and user email addresses, possibly even URLs - but I don't see a good resolution for that at this point without the ability to display a per-crash dialog there.)

Comment 6

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

(In reply to Robert Kaiser (:[e-mail]) [away until early June] from comment #4)
> Note that B2G has practically the same work flow there, so you might be able
> to borrow some ideas/text/flow-design from that.

Note that this design is created based on the V1 story Asa and the team agreed upon. A per-crash dialog would be ideal but unfortunately not a priority to work on for the V1 release at this moment. 

I've also looked through the B2G crash flow design specs. Since B2G supports per-crash dialog while Metro does not, the flow needs to be designed differently. 

I will update this document today based on the feedback I received from UX team.

Comment 7

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

Attachment: [Mockup]Crash reporting_0611

Finalized IxD flow based on the feedback from UX team.

Once I finish a sync-up with privacy team early next week, there might be changes to the privacy statement. 

But the basic interaction flows and wording should be good to go!

I assume we could just reuse the visual theme for info bar. Flagged Stephen to review the visuals.

Comment 8

[Robert Kaiser]

Unfortunately, this design may very well give us very low opt-in rates, as it's incredibly easy for people to click to never send. I'm not happy with that.

Comment 9

[Stephen Horlander [:shorlander]]

Comment on attachment 761188 [details]
[Mockup]Crash reporting_0611

(In reply to Yuan Wang(:Yuan) – Firefox UX Team from comment #7)
> I assume we could just reuse the visual theme for info bar. Flagged Stephen
> to review the visuals.

Yes we should use the same button styling from the info bar. I think we have overlay styling also?

Comment 10

[Jim Mathies [:jimm]]

Design appears to be complete, unblocking the design bug.

Comment 11

[Jim Mathies [:jimm]]

Attachment: use the same class for all chrome text links

Comment 12

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

Alina is okay with our current design. She said we can start implementing while awaiting for her privacy review. 

She will get back to us with a more consistent language and tune of crash report message.

So mark this bug as complete for now.

Comment 13

[Jim Mathies [:jimm]]

Comment on attachment 767159 [details] [diff] [review]
use the same class for all chrome text links

moving to a new bug.