Thanks @Ancheta_Wis! Another user that actually reads this dialog and gets totally confused: https://meta.wikimedia.org/wiki/User_talk:Erik_Moeller_(WMF)#Phabricator_login_sequence

I bet we have many more that actually just trust and click or just silently leave with the hope that in the future this will be clearer.

@Qgil is getting better worded text for this dialog something that your team could help with? It turns out that back-end focused engineers are typically computer power users who are not intimidated by jargon and take cues from a variety of sources in a way that leads them to being blind to things that are "obvious" to more typical audiences.

I think most of the OAuth UI could use the practiced hand of a technical writer and/or UX designer to help define a more welcoming experience for this powerful and useful core feature.

In T598#1045742, @bd808 wrote:

@Qgil is getting better worded text for this dialog something that your team could help with? It turns out that back-end focused engineers are typically computer power users who are not intimidated by jargon and take cues from a variety of sources in a way that leads them to being blind to things that are "obvious" to more typical audiences.

I think most of the OAuth UI could use the practiced hand of a technical writer and/or UX designer to help define a more welcoming experience for this powerful and useful core feature.

I'd suggest analysing how Google Play handles their permissions system. Their use case is mostly the same, namely telling the user what permissions an app wants and letting them make a decision whether they're okay with it. They do a good job of it, in my opinion.

Example for the Wikipedia app, which needs relatively few permissions compared to some apps:

If you tap on the boxes, some additional explanation is offered... but not much. And it's really still really generic: