Dear Threads: Please Fix Your “Edit Post” Microcopy

Threads has been growing in popularity since its official release last July. According to Meta, the social media platform currently has 33 million daily active users, which is nothing to sneeze at. I’m still a Bluesky guy myself, but I’m glad to see that users have more social media options in light of X/Twitter’s ongoing death spiral.

One feature available to all Threads users is the ability to edit your posts. (You must be a paying subscriber to edit your posts on X/Twitter while editing Bluesky posts currently requires a third-party app.) Once you post something on Threads, you have a 15-minute window during which you can make as many edits as you’d like, which comes in handy should you see a typo or some missing punctuation.

There’s one aspect of this process that consistently throws me for a loop, though. When you cancel out of Threads’ “Edit post” modal, you’re asked to confirm your choice (see above screenshot). You can either discard your changes and return to the original post sans any edits or return to the “Edit post” modal to make additional changes. However, this confirmation modal has two issues.

First, its title is “Discard thread?” This implies that going through with the process will delete your entire post when, in fact, it simply discards the most recent changes you’ve made, leaving your post unedited. A better, less obtuse title for this modal might be “Discard these edits to your post?” or, more simply, “Discard edits?”

Second, the confirmation modal contains two options: “Discard” or “Cancel.” Clicking on the former discards your changes while the latter cancels the process and returns you to the “Edit post” modal. However, this modal was already launched by clicking a “Cancel” button, so seeing another “Cancel” button is a bit disconcerting. What am I canceling? Am I canceling my cancellation? A better option might be to simply change “Discard” and “Cancel” to “Yes” and “No.” Or, if you want to be a bit more verbose, then “Yes” and “Return to Editor”

(It’d also be nice if Threads tracked whether you had actually made any edits in the “Edit post” modal. If you hadn’t, then clicking “Cancel” would just close the “Edit post” modal without displaying any confirmation modal, since there’s nothing to confirm one way or the other.)

This is an example of the importance of microcopy, i.e., short phrases and labels used in interface elements — buttons, headings, alerts, errors, etc. — to guide the user and give them enough context to understand what’s happening and what they can or should do next. Good microcopy must strike a balance between detail and brevity. If it’s too long, then the microcopy clutters up the UI. If it’s too short, then it becomes ambiguous, even misleading — as is the case here with Threads.

UI design often focuses on the sexy, like color schemes and animations. Though certainly less glamorous, good microcopy — be it a modal heading or a button label — is equally critical to the success of a user interface. Writing microcopy can be a chore; trying to fill up an interface with text that’s neither too long nor too short, and isn’t ambiguous but also not too detailed, is difficult. But the right microcopy can go a long ways towards reducing confusion and mental strain, and making a UI feel easy and effortless to use.