One of my earliest UX wins was for Mac System 7. The Finder team wanted to truncate files names with '…' if it wouldn’t fit. I argued that too much critical info would be lost and suggested it be in the middle instead. The Finder team loved it and implemented it later that day. They were so easy to work with.
I'd totally forgotten about it until I overheard someone commenting it was an example of Apple's attention to detail. I'd didn't say anything at the time but yeah, that was me ;-)
=> More informations about this toot | More toots from scottjenson@social.coop
What I so enjoyed about the Finder team was that there was no string utility to remove the middle of the string. They had to write it themselves. It was extra work they just took on. I never heard a peep from them about "implementation complexity".
It's experiences like this that have spoiled me. When I hear over (and over) that UX needs to "work within business goals" I think back to this experience where I just had an idea... and they did it.
Why was it so easy then, and so hard now?
=> More informations about this toot | More toots from scottjenson@social.coop
@scottjenson
Thanks for sharing this look behind the scenes!
I’m a UI dev, and sometimes it seems like Product Owners do everything they can to keep UI from talking directly to UX. Earlier in my career, some of our best work, and most enjoyable work, was when I could just walk into the UX lead’s office and brainstorm.
Now there seems to be less focus on “Let’s build the best experience we can” and it’s more about “Stay in your lane and build with the blocks we give you.”
=> More informations about this toot | More toots from inaction_figure@fosstodon.org
@inaction_figure @scottjenson Often that's because management has bad UX as an explicit goal.
=> More informations about this toot | More toots from dalias@hachyderm.io
text/geminiThis content has been proxied by September (ba2dc).