Hackpads are smart collaborative documents. .

Harry Trimble

279 days ago
Unfiled. Edited by Harry Trimble 279 days ago
Phone numbers
 
Harry T Displaying phone numbers
 
  • Guidance
 
 
 
Formats
 
 
 
  • Examples on GOV.UK and other services
 
  • Google
Not a GOV.UK service, but I quite like how google deal with international phone number entry. The select-list combined with country icon and name is nice. Though it introduces other problems for people who struggle with select lists. Having a default (eg UK) appears to work well and makes it obvious which it is, and how you change it.
 
  • Discussion
 
Ed H
  • It sort of feels like we should let browsers deal with this. If it's marked up as a telephone number it's for the browser to do something sensible with it. NB I've used `<meta name="format-detection" content="telephone=no">` to try to disable auto-detection in some cases - though mostly only safari uses it AFAIK.
 
 
25 days ago
Unfiled. Edited by Harry Trimble 25 days ago
Harry T Tested well with users: allowing them to check completed tasks:
 
 
 
 
19 days ago
Unfiled. Edited by Harry Trimble 19 days ago
Harry T Save and return
Caroline J Users may not be able to complete a task in one go.
 
Harry T A user may:
Caroline J
  • need a break
  • be interrupted during their work
  • need to go to look for information that they do not have with them
 
 
Tim P
  • Guidance
 
Tim P
  • Use this section to draft guidance for the pattern. This will become the first draft of the pattern page when it's added to the Service manual, at which point it will be removed from this page. It's quite common for a single pattern page to describe a number of different approaches. We're using the following structure to document each approach:
  •  
  • Example: 1 line intro plus screenshot or HTML
  • Pros: What this pattern is good at and when to use it
  • Cons: What this pattern is less good at and when not to use it
  • Guidance: General guidance on implementing this pattern
 
  • Discussion
 
Harry T Save and return test in these prototypes with 22 users over three rounds of research
 
Save by email
 
Save by phone 
 
Return to application
 
Tim P
  • Examples on GOV.UK
 
 
Harry T Email with reference number to return to application
 
 
Joe L
  • Complete the deputy report
 
 
 
  • Register for anti-money-laundering supervision
 
 
 
  • Money claims
 
 
 
  • Online debt solutions
 
 
 
 
  • Get an impartial decision on your dispute
 
 
 
Tim P
  • Research
 
  • Describe or link to any research relating to this pattern.
  • If the pattern requires further research, record this here.
  •  
  • Further reading
 
  •  Links out to related articles, blog posts etc.
  •  
 
278 days ago
Unfiled. Edited by Harry Trimble 278 days ago
Form structure
 
Harry T
  • Guidance
 
 
Harry T Use this page to discuss that guidance.
 
  • Discussion
 
Jessica E
  • Was any A/B testing performed? That would be particularly valuable.
  • I'd also love to know whether you've tested a registration or login process with only one question per screen. Once, when I was a user of such a form, I found it frustrating, and it also slowed me down, because it was just so unexpected. De facto conventions may go against the pattern in a case like login/registration.
  • I appreciate that this is a good pattern for small screens. On Twitter Caroline indicated that more than 30% of  your forms are filled via mobile. I was wondering if you had tested the pattern on desktop/large screens (which are still the vast majority of your usage)? Also, did you think about allowing for a different approach on large screens versus small screens (e.g. allowing multiple questions per screen when screen is above a certain size)? The large screen offers the opportunity to provide context that may help the form filler (e.g. grouping questions in to steps and showing what steps there are). 
  • One thing that I'm not clear on is how the pattern reconciles with the pattern on progress indicators. If you have 20 questions, one per screen, should you have a progress indicator with 20 steps? Or are you advocating dropping the progress indicator altogether (given some of your other research has shown it doesn't really help users)? If it's the latter, I wonder if people might not feel the need for signposting more when there are more screens/questions not grouped into steps (Am I half way through? 10% done? Nearly finished?).
 
Caroline J
  • Why are you considering using them? They are about as far from our strong recommendation 'start with one thing per page' as it's possible to be! :)
 
Tim P
  • Examples on GOV.UK
 
Tim P
  • Post images and links to examples on GOV.UK or prototypes.
  •  
  • Research
 
  • Describe or link to any research relating to this pattern.
  • If the pattern requires further research, record this here.
  •  
  • Further reading
 
 
 
246 days ago
Unfiled. Edited by Harry Trimble 246 days ago
Principle: consent where possible, transparency otherwise.
 
Harry T When giving consent to share their data, users should know:
 
Who is data being shared with?
Why is data being shared?
How long is permission given for?
When did they give consent?
Can they remove consent? 
 

Contact Support



Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!


Log in / Sign up