Blog

The problem with automatic email sorting

New email apps keep coming out, trying to organize your inbox. Folders in email were invented nearly fifty years ago, and since then we’ve had filters, rules, and now AI — all aiming to automate sorting.

Some apps don’t even call them “folders” anymore, but “categories” or something else that only adds to the confusion. Every new app tries to outsmart the others at sorting: “inbox”, “important”, “newsletters”, “social”, “purchases”.

Even Apple Mail recently jumped in with its own version: “primary”, “promotions”, and so on. Surely, I have no idea how it decides where things go. To avoid missing an email, I have to check all the categories, so the workload goes up, not down. “Didn’t get our message? Check your spam, secondary, non-urgent, and low-priority folders!” I turned that off immediately, of course.

For some reason, email designers don’t get that folders only work when you create them yourself and sort things manually. If the system exists in your head and you stick to it, you can trust it. But someone else’s system makes you second-guess everything.

Instead of sorting emails into folders, computers should be mining the actual information from them.

Yes, finding booking references and boarding pass QR codes in your inbox is a pain. But even finding them inside an email you’ve already opened is a pain! I don’t want just a folder with those emails — ideally, I’d see the info without even opening a message. If I do need more context, let there be a shortcut to the original message. And I don’t care what folder it’s in.

If an email invites me to a conference and asks me to respond by the 25th, I want that deadline clearly flagged next to the message. And show me, in my inbox, the three emails I should respond to today — based on what they say. Leave folders for people who actually like manual sorting.

Noise cancellation on a Mac mutes keyboard clicks

The Mac’s built-in noise cancellation suppresses keyboard clicks. It makes perfect sense, but there’s an annoying side effect. When you’re taking notes during a client call, it looks like you’re just reacting slowly or constantly zoning out. It’s hard to convince anyone you’re actually typing because they can’t hear a thing!

Apple Watch swimming screen

On the left is how Apple Watch displays a swim workout, on the right is how it could:

And below is what you can see in both cases, if your goggles are fogged up (Photoshop simulation).

Apple’s design is silly: what’s the point of using small type when you can use large type? But it’s especially silly that even if you enable enlarged fonts in the accessibility settings, it doesn’t apply to the workout screens anyway.

Wayfinding for Wildberries suppliers

Check out a new large project: wayfinding for suppliers of Wildberries, the largest Russian online retailer.

Wayfinding is not about drawing signs, but about streamlining the whole scenario of how people find something, and even how they understand what they need to look for. The project included signage, maps, printed instructions, a mobile website, an LED board, and a banner. And that’s all systematized for multiple warehouses.

Reversibility of an interface element

Reversibility is a property of an interface input control, where the user can return the control to its initial state at any time. Or, more generally, where the user can freely switch between all available states. Irreversibility, consequently, is when the element has states to which it cannot be returned after some actions. Well-designed controls are reversible.

An example of an irreversible control is a group of radio buttons of which none are initially selected. Once one option is selected, there is no way to return the group to the initial blank state. This creates discomfort and frustration. In a proper radio group exactly one element is always selected, including in the initial state, so the group is reversible.

But what if picking an option is required to proceed to the next step? There is no point in unselecting all options! Why would the user want that? Well, the reversibility requirement stands even if the initial state is not “valid”. This has to do only with the mechanics of the interface control, not with its role in the interface external to it. It affects the sense of control. Consider this: a text input field does not resist having all characters erased from it, even if it is required. Any other element, if it has a blank state at all, should let you return to it. In the case of a radio group, remove the blank state altogether by providing a default option.

Here’s another example of irreversibility. Suppose you have a required text field, initially blank. The user clicks the field, then clicks another element, leaving the field blank (or fills it in, but then erases everything). The system now draws a red border around the field, hinting that the field cannot be left blank. Now it is impossible to return the field to its initial “clean” blank state. A solution would be to fade out the red border so that the field returns to the initial state after a second.

ATP: how kids become programmers

John Siracusa in the 446th episode of ATP talks about how kids become programmers and how it didn’t work with his kids, starting at 40:36:

With my kids, I had no success getting them to want to learn to program at any age. I didn’t really push it that hard, but I was putting it in front of them, see if they are into it, see if it would grab them. And it never got hooked. And we all — all three of us — know what it means to get hooked on programming. It’s one of those things that just happens, right? You can see when programming gets its claws into somebody. And you know, it’s not subtle. You’ll find yourself just sucked in and just constantly working on this program — we all experienced it. That’s how we became who we are. But when that doesn’t happen, it doesn’t happen.

Earlier Ctrl + ↓