Max Glenister

UX & Design • 4 min read Plain text

O cursor, where art thou?

All too often on my computer, I’ll finish typing something, reach for my mouse, and have no idea where the cursor has got to. Not on the monitor I was looking at. Possibly on the laptop screen, but I’d have to turn my head and check. So I do what I always do, shake the mouse until macOS inflates the cursor to the size of a dinner plate, and carry on.

I wondered at first whether this was a problem with my eyes. I’ve had two pairs of glasses for a couple of years now, one of them purely for sitting in front of a computer, and I recently switched to varifocals, which trade a wide focus band for having near and far in one lens. With the right pair on I can see the cursor perfectly well once it’s in front of me, but the narrower band makes scanning a 32” panel slower than it used to be.

A small cursor arrow getting lost against a busy desktop background

Eyes aside, there’s also the area to cover. My 32” 4K monitor and the MacBook’s own 16” panel give me around 550 square inches to lose a cursor in, a long way from where the cursor started. Alan Kay drew the arrow at PARC on a 16x16 grid of one-bit pixels, angled because that was what read clearly at that size, and the Mac inherited it in 1984. On that 9” screen, running 512x342 at 72ppi, the cursor was about 0.22” (5.6mm) tall. The screen area I’m searching is sixteen times bigger now.

Screen area since 1984, drawn to physical scaleThree screens drawn to the same physical scale: a 32 inch 4K display, a 16 inch MacBook panel nested inside it, and the 9 inch original Macintosh screen. Each contains a mouse cursor drawn at the same true size, about 0.22 inches tall. The 1984 screen was around 34 square inches; the two modern panels together come to around 550.32" 4K display438 sq in16" MacBook118 sq in9" Mac, 198434 sq in

Forty years of work has gone into how the cursor looks, almost none into where it is. It’s antialiased now, with a white outline and a soft drop shadow, and it scales smoothly instead of stepping between fixed bitmaps. macOS will make it considerably bigger if you ask, and let you recolour the fill, which helps more than size does when it’s sitting over something the same tone. It all helps once you’re looking at the thing, but nothing tells you which corner to look in.

The cursor arrow through the years: PARC, System, OS X and macOS

I suppose I’ve also stopped using the mouse as much. Almost everything I do happens on the keyboard now, shortcuts inside whatever app I’m in, and Raycast for the rest. I use it as a cmd-space replacement and for window management, which matters on a display this size, since snapping something to a half or a third by keyboard beats dragging it there. The mouse gets picked up for dragging files around and for the occasional site that still insists on hover. The rest of the time the cursor sits motionless in a corner of a screen I haven’t looked at for ten minutes.

Shaking the mouse on macOS causes the cursor to balloon in size so it's easier to spot

Apple’s answer is the shake, which has been in macOS since El Capitan and lives under Accessibility, Display, Vision. I’d guess most people using it every day have never once thought of it as an accessibility feature. Windows made the same admission in a different shape, press ctrl and concentric circles close in on the cursor. Someone even ported the shake itself to Windows, for anyone who prefers macOS’s version.

Neither puts anything permanent on screen, which is right. A constant locator would be noise for anyone with a hand on the mouse all day. It’s only worth anything once you’ve drifted far enough from the cursor to lose track of it.

  • UX & Design · shares #ux
    The progress of progress bars

    I was waiting for Claude to answer a token-heavy question at work the other day, the little “Thinking…” label flickering into “Wibbling…” and then “Moseying…”, and I caught myself doing the thing I always do when a spinner takes too long, staring at it, trying to divine meaning from the word choice. Is it nearly done? There’s no percentage, no bar, just a word standing in for “trust me, something is happening.” It sent me down a rabbit hole into where progress bars came from, and it turns out they were never really about progress at all.

    July 2026 • 8 min read
  • UX & Design · shares #macos
    Making GIMP feel less like punishment

    GIMP has always had an interface problem. I’m not blaming the GIMP team (they’ve built something powerful on a shoestring). They’ve been clear they’re not interested in copying Photoshop wholesale; their FAQ argues that designing around actual user research beats imitating someone else’s interface decisions. Fair enough in principle, but coming from years as a Photoshop user, that design still feels hostile to me. I’m just one user story out of many they’ve had to design for, but it still expects me to learn its own way of doing things rather than offering a config closer to what I’m used to out of the box.

    June 2026 • 2 min read
  • UX & Design · shares #ux
    Your forecast is accurate and still wrong

    Icons work because they’re fast. One glance, immediate meaning, no reading required. The tradeoff is that they compress complex information into a single symbol, and compression always drops something.

    March 2026 • 5 min read

Discussion

No interactions yet

Join the conversation

Comment on the GitHub issue, or reply from your own site with a Webmention (how?).

Comment on GitHub

Webmentions last fetched 21 November 2026, 17:19