Re: keygen and client-certificates document available

On 3 December 2015 at 02:30, Noah Mendelsohn <nrm@arcanedomain.com> wrote:

>
> On 12/2/2015 4:54 PM, Noah Mendelsohn wrote:
>
>> Not making substantive technical content, but just wanted to say I'm
>> delighted to see the TAG working through drafts like this.
>>
>
> Argh...the perils of speech recognition: I meant to say:
>
> I am not making a substantive technical COMMENT, but just wanted to say
> I'm delighted to see the TAG working through drafts like this.
>
> If anyone thought I found the draft to be content-free, I apologize. On
> the contrary, it's terrific.
>

Regarding the section on improving the user experience.

If I may give an example of a user experience I encountered today using
this technology with a brand new android phone.

Here is a screenshot that I took:

https://melvin.databox.me/Public/Screenshot_2015-12-03-15-06-10.png

Perhaps I am mistaken, but as a user, when viewing that popup my natural
instinct was to hit the "install" button.  However, this opens a file
system dialog that I found confusing, as I was expecting to use my cert to
authenticate.  What I had to do was cancel and go back.

Simply hitting "Allow" would have taken me through authentication, with the
single certificate that I had installed.  But that was less obvious to me.

Some general suggestions:

- Make "Install" type functionality less close to the OK / Cancel type
buttons.  Or not have it on that page at all.

- Allow the user to remember their choice.  Although the dialog implies the
choice will be remembered, it does not seem to be.

- Make the text slightly less verbose and technical, if possible, more in
line with popups for geolocation, camera use or notifications.

The user experience in modern browsers is generally of quite a high
standard.  If perhaps some of the designers of other widgets could have
some time to look at these type of interactions, and give feedback, small
tweaks might lead to a much improved user experience.


>
> Noah
>
>
>