|
Last week I wrote about the problem with using the accept attribute for uploading files. As a quick reminder: When you use accept to specify which file types will be allowed like this:
…the dialog will disable invalid types like this: This is bad because:
But a developer called Jaroslaw responded to me on X to say: This is on Apple, elsewhere you get a proper filter that you can disable. I’m against ruining stuff for everyone just because Apple did something stupid. I appreciated the message because it got me thinking: “What if the UX on other operating systems like Windows and Android avoid these issues?” So I decided to take a quick look. And here’s what I found: How Windows implements the accept attributeWindows hides the invalid files instead of disabling them, like this: This avoids the problem with disabling the files. So that’s good. But this leads to another problem: If the user is looking for a file that they know is inside the folder, and they can’t see it, they’ll be confused. Most users aren’t going to think:
It might be even worse if there are no valid files, making the entire folder look empty. But Jaroslaw’s point was that on Windows, there’s a menu in the bottom-right corner that allows you to remove the filter by switching from “Custom files” to “All files”: That’s good because it gives users control. But most users won’t spot the menu. Or think to even look for it. Think about it. Most people will be thinking:
And maybe they’ll leave the upload flow to check. And when they do, the file will be right there. This is long-winded and confusing, all because: The Windows designer assumed that simply adding the drop down menu is enough. But just a tiny amount of usability testing would prove it’s not. Funnily enough, I took a closer look at MacOS. And I realised it has the same functionality as Windows. You have to click “More options” to reveal it: That’s worse than just having the menu there, but either way you’ve got confused users. Confused users = bad UX. How Android implements the accept attributeAndroid is worse. Here I’ve set the attribute to only allow PNG, GIF or JPG: All I got were my photos. There’s no way to browse my files. And there’s no way to use the camera to take another photo, something that’s particularly useful on mobile. I tested setting the accept attribute to allow for DOC, DOCX and PDF - not just images. This changed the UI completely and gave me the option to use the camera or browse all the files. That’s good. But then if you browse to any invalid files you get this: Only one of these files can be selected. If you’re finding that difficult to see which one that is, that’s the point. The Android designers completely screwed up every moment of the journey. But luckily, all you need to is not use the accept attribute. And instead spend your time solving much bigger problems, not just in general, but with file uploading specifically. Many designers don’t realise that: Uploading a file is one of the most labour-intensive interactions there is. It involves multiple steps, all that can cause varying degrees of pain. It’s 100x more complicated than typing words into a box. So I’m running a live training on Thursday 11 June at 5pm (UK time) where I’ll cover:
It’s a 60 minute session with plenty of time for your questions. Access is included with Form Design Mastery. If you’ve already purchased it, you’ll get an invite shortly. I’ll share a recording after if you can’t attend. If you haven’t, and would like to, you need to sign up before Thursday. I won’t be promoting this again. https://formdesignmastery.com Cheers, |
Join 10,000+ designers, content designers and engineers who get my free weekly newsletter with evidence-based design tips (in 3 minutes or less). Mostly forms UX, but not always.
Last week, someone paid me to review their form flow. One thing they wanted advice about was interruption pages. Coincidentally, the following day the GOV.UK Design System added the interruption page pattern. Interruption pages are designed to pause the user within a journey - usually to warn them about a possible mistake or give them important information before they continue. Here’s an example from the GOV.UK Design System: It has: An h1 heading to ask a simple question A paragraph to...
Last week, Kate Ivey-Williams, the Head of UCD on my programme, asked me: “What do you think your role is as a designer?” I said: “Errr... I design products that are easy to use... errr... I realise that’s a rubbish answer...” Kate saved me: “Don’t worry, I put you on the spot” But even so, as a designer you should be ready to be put on the spot because: If you aren’t able to explain what you do, it’s much harder for your teammates and stakeholders to value what you do. I messaged Kate later...
Last week, I ran a live training on file upload UX. Every day leading up to the event, I was stressed, constantly thinking: “Shall I just purchase one month of Zoom?” Let me explain: I use Circle to run my courses and it comes with something called Live Rooms. It’s like Zoom. But Live Rooms is better than Zoom because: it’s quicker and easier to set up for me it comes with my Circle subscription for free it automatically posts the recording afterward the call it has better UX for my students...