My initial ballpark thresholds to test, then, would be something like buckets of 0.1 starting at 0.95. @OTichonova is doing a similar runthrough for de.wiki and ru.wiki.

In T365134#10038271, @Samwalton9-WMF wrote:

As hinted above I think it might be helpful for us to do a little user research to understand what information users would find helpful when they look at the thresholds and need to make a decision about which to use.

Carrying over slack discussion:

@Dbrant, okay thanks, moving it forward.

Most frequently the suggested descriptions do take around 3 seconds to load.
I found that roughly every 10 articles ->


• 1 took 8-10 seconds (which felt long)

• 1-2 took 4-5 seconds 

• the rest took around 3 seconds 



Is it possible to have all article suggested descriptions to load in around 3 seconds?

Hi @Tsevener, thank you for the screenshots for iPad. It is a pretty cool use of popovers, looks good!

Hi @Rajparad, great to see that this ticket was picked up, thank you!

Ah okay sorry, I didn't read the ticket carefully. This looks good!
Couple things ->

Hi @Tsevener!
A couple small things.

1. Can we get rid of the line between the two toggles?
2. Could the text in the confirmation toast be gray 700 rather than blue 600?
3. To Glauco's feedback (from here T354219). Could we make the margins on these screens (in the editing flow also) 16points?

Hi @Dmantena,

2. Okay thank you for writing this out, lets leave it as is.
3. Sorry, looking again the line heigh for the longer text per section is looking good. Not sure what happened there on my end. Moving this ticket along.

Thanks!

Hi @Dmantena, updates are looking good thank you!
2 small things.

@Tsevener great thanks!

Hi @Tsevener, minor thing -> can the copy be 'Back' rather than 'Add image' when tapping back from the commons page?

Hi @Tsevener, I think this has been updated to de-emphasized rather than disabled.
So 'Publish' would be gray500 in the de-emphasized state.

@Dmantena okay thank you for including the screen shots. A couple of things I noticed.

Hi @Dmantena, looking good! Couple of things:

1. Can the area with the Button and link be sticky to the bottom and have the scroller show up when people access the page just like we have it for the Notifications onboarding page?

Thats great @ARamadan-WMF can you put them in touch with @OTichonova so they can serve as an experienced editor in our user testing.

@Dmantena

No worries if not, but do you happen to have any documentation/a direction to point me in to better understand this original decision on Android? To me it feels user hostile/confusing that the only way to proceed with more recommendations is either forced feedback via this survey or tapping "Not sure" on the previous screen, but I'd like to understand what context I may be missing to better understand the original decision.

Hi @Dmantena, thanks for writing these out.

1. It is normal iOS behavior to keep that text field standard one line. When designing I thought that would stay that way.
2. On Android the Cancel would takes you back to the same image so for consistency that would be the same case on iOS.
3. That logic sounds good to me.