199 posts in Linked

Kendra Albert, writing in her blog post about Heavyweight, a new tool she built to create “extremely law-firm-looking” letters:

Sometimes, you don’t need a lawyer, you just need to look like you have one.

That’s the idea behind Heavyweight, a project that democratizes the aesthetics of (in lieu of access to) legal representation. Heavyweight is a free, online, and open-source tool that lets you give any complaint you have extremely law-firm-looking formatting and letterhead. Importantly, it does so without ever using any language that would actually claim that the letter was written by a lawyer.
preview-1753379920512.png

Heavyweight: Letters Taken Seriously - Free & Open Legal Letterhead Generator

Generate professional-looking demand letters with style and snootiness

Earth 3 Streamline Icon: https://streamlinehq.comheavyweight.cc

In many ways, this excellent article by Kaustubh Saini for Final Round AI’s blog is a cousin to my essay on the design talent crisis. But it’s about what happens when people “become” developers and only know vibe coding.

The appeal is obvious, especially for newcomers facing a brutal job market. Why spend years learning complex programming languages when you can just describe what you want in plain English? The promise sounds amazing: no technical knowledge required, just explain your vision and watch the AI build it.

In other words, these folks don’t understand the code and, well, bad things can happen.

The most documented failure involves an indie developer who built a SaaS product entirely through vibe coding. Initially celebrating on social media that his "saas was built with Cursor, zero hand written code," the story quickly turned dark.

Within weeks, disaster struck. The developer reported that "random things are happening, maxed out usage on api keys, people bypassing the subscription, creating random shit on db." Being non-technical, he couldn't debug the security breaches or understand what was going wrong. The application was eventually shut down permanently after he admitted "Cursor keeps breaking other parts of the code."

This failure illustrates the core problem with vibe coding: it produces developers who can generate code but can't understand, debug, or maintain it. When AI-generated code breaks, these developers are helpless.

I don’t foresee something this disastrous with design. I mean, a newbie designer wielding an AI-enabled Canva or Figma can’t tank a business alone because the client will have eyes on it and won’t let through something that doesn’t work. It could be a design atrocity, but it’ll likely be fine.

This can happen to a designer using vibe coding tools, however. Full disclosure: I’m one of them. This site is partially vibe-coded. My Severance fan project is entirely vibe-coded.

But back to the idea of a talent crisis. In the developer world, it’s already happening:

The fundamental problem is that vibe coding creates what experts call "pseudo-developers." These are people who can generate code but can't understand, debug, or maintain it. When AI-generated code breaks, these developers are helpless.

In other words, they don’t have the skills necessary to be developers because they can’t do the basics. They can’t debug, don’t understand architecture, have no code review skills, and basically have no fundamental knowledge of what it means to be a programmer. “They miss the foundation that allows developers to adapt to new technologies, understand trade-offs, and make architectural decisions.”

Again, assuming our junior designers have the requisite fundamental design skills, not having spent time developing their craft and strategic skills through experience will be detrimental to them and any org that hires them.

preview-1753377392986.jpg

How AI Vibe Coding Is Destroying Junior Developers' Careers

New research shows developers think AI makes them 20% faster but are actually 19% slower. Vibe coding is creating unemployable pseudo-developers who can't debug or maintain code.

Earth 3 Streamline Icon: https://streamlinehq.comfinalroundai.com

This is gorgeous work from Collins in their rebrand for Muse Group, developers of music apps like Ultimate Guitar, MuseScore, Audacity, and MuseClass. Paul Moore, writing in It’s Nice That:

One of the issues, [chief creative officer] Nick [Ace] argues, in the design industry is a fixation on branding tech as “software from the future”, relying on literal representations from the 1980s that have created dull and homogeneous visuals that shy away from the timelessness of creativity. “Instead of showcasing technical specs or outlandish interfaces, we centered the brand around the raw experience of musical creation, itself,” says Nick. “Rather than depicting the tools, we visualized the outcomes—the resonance, the harmony, the creative breakthrough that happens when technical barriers disappear.”

Collins rebrand for Muse Group channels the invisible phenomena of experiencing music

Geometric abstraction, dynamic compositions and a distillation of musical feeling sets Collins new project apart from other software brands.

Earth 3 Streamline Icon: https://streamlinehq.comitsnicethat.com

Sonos announced yesterday that interim CEO Tom Conrad was made permanent. From their press release:

Sonos has achieved notable progress under Mr. Conrad’s leadership as Interim CEO. This includes setting a new standard for the quality of Sonos’ software and product experience, clearing the path for a robust new product pipeline, and launching innovative new software enhancements to flagship products Sonos Ace and Arc Ultra.

Conrad surely navigated this landmine well after the disastrous app redesign that wiped almost $500 million from the company’s market value and cost CEO Patrick Spence his job. My sincere hope is that Conrad continues to rebuild Sonos’s reputation by continuing to improve their products.

Sonos Appoints Tom Conrad as Chief Executive Officer

Sonos Website

Earth 3 Streamline Icon: https://streamlinehq.comsonos.com

Let's rewind 25 years and remember what websites and web technology used to look like. Kevin Gut:

This website is a trip down memory lane. I'm not trying to tell you to stop modern web development. This website uses technologies not available at the time the content here is about.
A simple website

A simple website

This website is a trip down memory lane. I'm not trying to tell you to stop modern web development. This website uses technologies not available at the time the content here is about. It works on mobile (tested in Firefox for Android) but you miss out on the background image. I created my first website somewhere in the early 2000s, and like most websites back then, it was very simple. Not surprising, considering most people (including me) were likely using notepad to create those websites, which puts a limit on their complexity. It was either that or WYSIWYG editors that would chain you to themselves because there was no chance the generated HTML would be maintainable at all without the tool, and if you did manual edits it could outright break your editor. There were no iPhones, there was barely any SEO, and JavaScript really was optional, and so was CSS. The color representation on early LCD screens was bad, so you better picked a color scheme with high contrast.

Earth 3 Streamline Icon: https://streamlinehq.comsimplesite.ayra.ch

Elizabeth Goodspeed contextualizes today’s growing design influencers against designers-cum-artists like April Greiman and Stefan Sagmeister. Along with Tibor Kalman, Jessica Walsh, and Wade and Leta, all of these designers put themselves into their work.

Other designers ran with similar instincts. 40 Days of Dating, a joint project by Jessica Walsh and Timothy Goodman created in 2013, was presented as a kind of art-directed relationship experiment: two friends, both single, agreed to date each other for 40 days (40 days being the purported time needed to build a habit). The project was presented through highly polished daily updates with lush photography, motion graphics, custom lettering, and a parade of commissioned work from other artists – all accompanied by alarming candid journal entries from both parties about the dates they were going on. It wasn’t exactly a design project in the traditional sense, but it was unmistakably design-led; the relationship itself was the content, but it was design that made it viral.

These self-directed, clientless projects remind me of MFA design theses where design is the medium for self-expression. Bringing it back to 2025, Godspeed writes:

Designers film themselves in their bedrooms and running errands, narrating design decisions and venting about clients along the way. Just as remote work expects us to perform constant busyness, design influencing demands a continuous performance of creative output. …Brands have jumped in on the trend, too. Where once a designer might have been hired to create packaging or campaigns behind the scenes, many are now brought forward as faces of collaborations – they’re photographed in their studios and interviewed about their process as part of launch. The designer’s body, personality, and public profile become a commercial asset.

And of course, like with all content creators, it becomes a job that just might require more work than it seems.

Influencing can seem like a good, low-lift side-hustle at first. Most designers already have tons of unused work and in-progress sketches to share. Why not just post it and see what happens? But anyone who’s ever had to write captions or cut reels knows that making content is, in fact, harder than it looks. The more energy that goes into showcasing work, the less time there is to actually make work, even if you want to. “Influencing” can quickly become a time suck.
preview-1753150717056.png

Elizabeth Goodspeed on the rise of the designer as influencer

As social platforms reward visibility, creatives are increasingly expected to make their practice public. Designers are no longer just making work; they are the work. But what started as promotion now risks swallowing design itself.

Earth 3 Streamline Icon: https://streamlinehq.comitsnicethat.com

It’s no secret that I am a big fan of Severance, the Apple TV+ show that has 21 Emmy nominations this year. I made a fan project earlier in the year that generates Outie facts for your Innie.

After launching a teaser campaign back in April, Atomic Keyboard is finally taking pre-orders for their Severance-inspired keyboard just for Macrodata Refinement department users. The show based the MDR terminals on the Data General Dasher D2 terminal from 1977. So this new keyboard includes three layouts:

  1. “Innie” which is show-accurate, meaning no Escape, no Option, and no Control keys, and includes the trackball
  2. “Outie,” a 60% layout that includes modern modifier keys and the trackball
  3. “Dasher” which replicates the DG terminal layout

It’s not cheap. The final retail price will be $899, but they’re offering a pre-Kickstarter price of $599.

preview-1752862402377.png

MDR Dasher Keyboard | For Work That's Mysterious & Important

Standard equipment for Macrodata Refinement: CNC-milled body, integrated trackball, modular design. Please enjoy each keystroke equally.

Earth 3 Streamline Icon: https://streamlinehq.commdrkeyboard.com

Stephanie Tyler, in a great essay about remembering what we do as designers:

In an age where AI can generate anything, the question is no longer ‘can it be made?’ but ‘is it worth making?’ The frontier isn’t volume—it’s discernment. And in that shift, taste has become a survival skill.

And this is my favorite passage, because this is how I think about this blog and my newsletter.

There will always be creators. But the ones who stand out in this era are also curators. People who filter their worldview so cleanly that you want to see through their eyes. People who make you feel sharper just by paying attention to what they pay attention to.

Curation is care. It says: I thought about this. I chose it. I didn’t just repost it. I didn’t just regurgitate the trending take. I took the time to decide what was worth passing on.

That’s rare now. And because it’s rare, it’s valuable.

We think of curation as a luxury. But it’s actually maintenance. It’s how you care for your mind. Your attention. Your boundaries.

This blog represents my current worldview, what I’m interested in and exploring. What I’m thinking about now.

preview-1752706649473.png

Taste Is the New Intelligence

Why curation, discernment, and restraint matter more than ever

Earth 3 Streamline Icon: https://streamlinehq.comwildbarethoughts.com

This is a really well-written piece that pulls the AI + design concepts neatly together. Sharang Sharma, writing in UX Collective:

As AI reshapes how we work, I’ve been asking myself, it’s not just how to stay relevant, but how to keep growing and finding joy in my craft.

In my learning, the new shift requires leveraging three areas
1. AI tools: Assembling an evolving AI design stack to ship fast
2. AI fluency: Learning how to design for probabilistic systems
3. Human-advantage: Strengthening moats like craft, agency and judgment to stay ahead of automation

Together with strategic thinking and human-centric skills, these pillars shape our path toward becoming an AI-native designer.

Sharma connects all the crumbs I’ve been dropping this week:

preview-1752771124483.jpeg

AI tools + AI fluency + human advantage = AI-native designer

From tools to agency, is this what it would take to thrive as a product designer in the AI era?

Earth 3 Streamline Icon: https://streamlinehq.comuxdesign.cc
Copilots helped enterprises dip their toes into AI. But orchestration platforms and tools are where the real transformation begins — systems that can understand intent, break it down, distribute it, and deliver results with minimal hand-holding.

Think of orchestration as how “meta-agents” are conducting other agents.

The first iteration of AI in SaaS was copilots. They were like helpful interns eagerly awaiting your next command. Orchestration platforms are more like project managers. They break down big goals into smaller tasks, assign them to the right AI agents, and keep everything coordinated. This shift is changing how companies design software and user experiences, making things more seamless and less reliant on constant human input.

For designers and product teams, it means thinking about workflows that cross multiple tools, making sure users can trust and control what the AI is doing, and starting small with automation before scaling up.

Beyond Copilots: The Rise of the AI Agent Orchestration Platform

AI agent orchestration platforms are replacing simple copilots, enabling enterprises to coordinate autonomous agents for smarter, more scalable workflows.

Earth 3 Streamline Icon: https://streamlinehq.comuxmag.com

Let’s stay on the train of designing AI interfaces for a bit. Here’s a piece by Rob Chappell in UX Collective where he breaks down how to give users control—something I’ve been advocating—when working with AI.

AI systems are transforming the structure of digital interaction. Where traditional software waited for user input, modern AI tools infer, suggest, and act. This creates a fundamental shift in how control moves through a experience or product — and challenges many of the assumptions embedded in contemporary UX methods.

The question is no longer:
“What is the user trying to do?”

The more relevant question is:
“Who is in control at this moment, and how does that shift?”

Designers need better ways to track how control is initiated, shared, and handed back — focusing not just on what users see or do, but on how agency is negotiated between human and system in real time.

Most design frameworks still assume the user is in the driver’s seat. But AI is changing the rules. The challenge isn’t just mapping user flows or intent—it’s mapping who holds the reins, and how that shifts, moment by moment. Designers need new tools to visualize and shape these handoffs, or risk building systems that feel unpredictable or untrustworthy. The future of UX is about negotiating agency, not just guiding tasks.

preview-1752705140164.png

Beyond journey maps: designing for control in AI UX

When systems act on their own, experience design is about balancing agency — not just user flow

Earth 3 Streamline Icon: https://streamlinehq.comuxdesign.cc

Vitaly Friedman writes a good primer on the design possibilities for users to interact with AI features. As AI capabilities become more and more embedded in the products designers make, we have to become facile in manipulating AI as material.

Many products are obsessed with being AI-first. But you might be way better off by being AI-second instead. The difference is that we focus on user needs and sprinkle a bit of AI across customer journeys where it actually adds value.
preview-1752639762962.jpg

Design Patterns For AI Interfaces

Designing a new AI feature? Where do you even begin? From first steps to design flows and interactions, here’s a simple, systematic approach to building AI experiences that stick.

Earth 3 Streamline Icon: https://streamlinehq.comsmashingmagazine.com

Speaking of prompt engineering, apparently, there’s a new kind in town called context engineering.

Developer Philipp Schmid writes:

What is context engineering? While "prompt engineering" focuses on crafting the perfect set of instructions in a single text string, context engineering is a far broader. Let's put it simply:
“Context Engineering is the discipline of designing and building dynamic systems that provides the right information and tools, in the right format, at the right time, to give a LLM everything it needs to accomplish a task.”
preview-1752639352021.jpg

The New Skill in AI is Not Prompting, It's Context Engineering

Context Engineering is the new skill in AI. It is about providing the right information and tools, in the right format, at the right time.

Earth 3 Streamline Icon: https://streamlinehq.comphilschmid.de

Since its debut at Config back in May, Figma has steadily added practical features to Figma Make for product teams. Supabase integration now allows for authentication, data storage, and file uploads. Designers can import design system libraries, which helps maintain visual consistency. Real-time collaboration has improved, giving teams the ability to edit code and prototypes together. The tool now supports backend connections for managing state and storing secrets. Prototypes can be published to custom domains. These changes move Figma Make closer to bridging the gap between design concepts and advanced prototypes.

In my opinion, there’s a stronger relationship between Sites and Make than there is Make and Design. The Make-generated code may be slightly better than when Sites debuted, but it is still not semantic.

Anyhow, I think Make is great for prototyping and it’s convenient to have it built right into Figma. Julius Patto, writing in UX Collective:

Prompting well in Figma Make isn’t about being clever, it’s about being clear, intentional, and iterative. Think of it as a new literacy in the design toolkit: the better you get at it, the more you unlock AI’s potential without losing your creative control.
preview-1752622395695.jpeg

How to prompt Figma Make’s AI better for product design

Learn how to use AI in Figma Make with UX intention, from smarter prompts to inclusive flows that reflect real user needs.

Earth 3 Streamline Icon: https://streamlinehq.comuxdesign.cc

In case you missed it, there’s been a major shift in the AI tool landscape.

On Friday, OpenAI’s $3 billion offer to acquire AI coding tool Windsurf expired. Windsurf is the Pepsi to Cursor's Coke. They're both IDEs, the programming desktop application that software developers use to code. Think of them as supercharged text editors but with AI built in.

On Friday evening, Google announced that it had hired Windsurf's CEO Varun Mohan, co-founder Douglas Chen, and several key researchers for $2.4 billion.

On Monday, Cognition, the company behind Devin, the self-described “AI engineer” announced that it had acquired Windsurf for an undisclosed sum, but noting that its remaining 250 employees will “participate financially in this deal.”

Why does this matter to designers?

The AI tools market is changing very rapidly. With AI helping to write these applications, their numbers and features are always increasing—or in this case, maybe consolidating. Choose wisely before investing too deeply into one particular tool. The one piece of advice I would give here is to avoid lock-in. Don’t get tied to a vendor. Ensure that your tool of choice can export your work—the code.

Jason Lemkin has more on the business side of things and how it affects VC-backed startups.

preview-1752536770924.png

Did Windsurf Sell Too Cheap? The Wild 72-Hour Saga and AI Coding Valuations

The last 72 hours in AI coding have been nothing short of extraordinary. What started as a potential $3 billion OpenAI acquisition of Windsurf ended with Google poaching Windsurf’s CEO and co…

Earth 3 Streamline Icon: https://streamlinehq.comsaastr.com

Ted Goas, writing in UX Collective:

I predict the early parts of projects, getting from nothing to something, will become shared across roles. For designers looking to branch out, code is a natural next step. I see a future where we’re fixing small bugs ourselves instead of begging an engineer, implementing that animation that didn’t make the sprint but you know would absolutely slap, and even building simple features when engineering resources are tight.

Our new reality is that anyone can make a rough draft.

But that doesn’t mean those drafts are good. That’s where our training and taste come in.

I think Goas is right and it echoes the AI natives post by Elena Verna. I wrote a little more extensively in my newsletter over the weekend.

preview-1752467928143.jpg

Designers: We’ll all be design engineers in a year

And that’s a good thing.

Earth 3 Streamline Icon: https://streamlinehq.comuxdesign.cc

Miquad Jaffer, a product leader at OpenAI shares his 4D method on how to build AI products that users want. In summary, it's…

  • Discover: Find and prioritize real user pain points and friction in daily workflows.
  • Design: Make AI features invisible and trustworthy, fitting naturally into users’ existing habits.
  • Develop: Build AI systematically, with robust evaluation and clear plans for failures or edge cases.
  • Deploy: Treat each first use like a product launch, ensuring instant value and building user trust quickly.
preview-1752209855759.png

OpenAI Product Leader: The 4D Method to Build AI Products That Users Actually Want

An OpenAI product leader's complete playbook to discover real user friction, design invisible AI, plan for failure cases, and go from "cool demo" to "daily habit"

Earth 3 Streamline Icon: https://streamlinehq.comcreatoreconomy.so

Geoffrey Litt, Josh Horowitz, Peter van Hardenberg, and Todd Matthews writing a paper for research lab Ink & Switch, offer a great, well-thought piece on what they call “malleable software.”

We envision a new kind of computing ecosystem that gives users agency as co-creators. … a software ecosystem where anyone can adapt their tools to their needs with minimal friction. … When we say ‘adapting tools’ we include a whole range of customizations, from making small tweaks to existing software, to deep renovations, to creating new tools that work well in coordination with existing ones. Adaptation doesn’t imply starting over from scratch.

In their paper, they use analogies like kitchen tools and tool arrangement in a workshop to explore their idea. With regard to the current crop of AI prompt-to-code tools

We think these developments hold exciting potential, and represent a good reason to pursue malleable software at this moment. But at the same time, AI code generation alone does not address all the barriers to malleability. Even if we presume that every computer user could perfectly write and edit code, that still leaves open some big questions.

How can users tweak the existing tools they’ve installed, rather than just making new siloed applications? How can AI-generated tools compose with one another to build up larger workflows over shared data? And how can we let users take more direct, precise control over tweaking their software, without needing to resort to AI coding for even the tiniest change? None of these questions are addressed by products that generate a cloud-hosted application from a prompt.

Kind of a different take than the “personal software” we’ve seen written about before.

preview-1752208778544.jpg

Malleable software: Restoring user agency in a world of locked-down apps

The original promise of personal computing was a new kind of clay. Instead, we got appliances: built far away, sealed, unchangeable. In this essay, we envision malleable software: tools that users can reshape with minimal friction to suit their unique needs.

Earth 3 Streamline Icon: https://streamlinehq.cominkandswitch.com

This post has been swimming in my head since I read it. Elena Verna, who joined Lovable just over a month ago to lead marketing and growth, writing in her newsletter, observes that everyone at the company is an AI-native employee. “An AI-native employee isn’t someone who ‘uses AI.’ It’s someone who defaults to AI,” she says.

On how they ship product:

Here, when someone wants to build something (anything) - from internal tools, to marketing pages, to writing production code - they turn to AI and... build it. That’s it.

No headcount asks. No project briefs. No handoffs. Just action.

At Lovable, we’re mostly building with… Lovable. Our Shipped site is built on Lovable. I’m wrapping hackathon sponsorship intake form in Lovable as we speak. Internal tools like credit giveaways and influencer management? Also Lovable (soon to be shared in our community projects so ya’ll can remix them too). On top of that, engineering is using AI extensively to ship code fast (we don’t even really have Product Managers, so our engineers act as them).

I’ve been hearing about more and more companies operating this way. Crazy time to be alive.

More on this topic in a future long-form post.

preview-1752160625907.png

The rise of the AI-native employee

Managers without vertical expertise, this is your extinction call

Earth 3 Streamline Icon: https://streamlinehq.comelenaverna.com

John Calhoun joined Apple 30 years ago as a programmer to work on the Color Picker.

Having never written anything in assembly, you can imagine how overjoyed I was. It’s not actually a very accurate analogy, but imagine someone handing you a book in Chinese and asking you to translate it into English (I’m assuming here that you don’t know Chinese of course). Okay, it wasn’t that hard, but maybe you get a sense that this was quite a hurdle that I would have to overcome.

Calhoun was given an old piece of code and tasked with updating it. Instead, he translated it into a programming language he knew—C—and then decided to add to the feature. He explains:

I disliked HSL as a color space, I preferred HSV (Hue, Saturation, Value) because when I did artwork I was more comfortable thinking about color in those terms. So writing an HSV color picker was on my short list.

When I had my own color picker working I think I found that it was kind of fun. Perhaps for that reason, I struck out again and wrote another color picker. The World Wide Web (www) was a rather new thing that seemed to be catching on, so I naturally thought that an HTML color picker made sense. So I tackled that one as well. It was more or less the RGB color picker but the values were in hexadecimal and a combined RGB string value like “#FFCC33” was made easy to copy for the web designer.

So an engineer decided, all on his own, that he'd add a couple extra features. Including the fun crayon picker:

On a roll, I decided to also knock out a “crayon picker”. At this point, to be clear, the color picker was working and I felt I understood it well enough. As I say, I was kind of just having some fun now.
Screenshot of a classic Mac OS color picker showing the “Crayon Picker” tab. A green color named “Watercress” is selected, replacing the original orange color. Options include CMYK, HLS, and HSV pickers on the left.

And Calhoun makes this point:

It was frankly a thing I liked about working for Apple in those days. The engineers were the one’s driving the ship. As I said, I wrote an HSV picker because it was, I thought, a more intuitive color space for artists. I wrote the HTML color picker because of the advent of the web. And I wrote the crayon picker because it seemed to me to be the kind of thing Apple was all about: HSL, RGB — these were kind of nerdy color spaces — a box of crayons is how the rest of us picked colors.

Making software—especially web software—has matured since then, with product managers and designers now collaborating closely with engineers. But with AI coding assistants, the idea of an individual contributor making solo decisions and shipping code might become de rigueur again.

Man sitting outside 2 Infinite Loop, Apple’s former headquarters in Cupertino, holding a book with an ID badge clipped to his jeans.

Almost Fired

I was hired on at Apple in October of 1995. This was what I refer to as Apple’s circling the drain period. Maybe you remember all the doomsaying — speculation that Apple was going to be shuttering soon. It’s a little odd perhaps then that they were hiring at all but apparently Apple reasoned that they nonetheless needed another “graphics engineer” to work on the technology known as QuickdrawGX. I was then a thirty-one year old programmer who lived in Kansas and wrote games for the Macintosh — surely, Apple thought, I would be a good fit for the position.

Earth 3 Streamline Icon: https://streamlinehq.comengineersneedart.com

Let's continue down Mac memory lane with this fun post from Basic Apple Guy:

With macOS 26, Apple has announced a dramatically new look to their UI: Liquid Glass. Solid material icon elements give way to softer, shinier, glassier icons. The rounded rectangle became slightly more rounded, and Apple eliminated the ability for icon elements to extend beyond the icon rectangle (as seen in the current icons for GarageBand, Photo Booth, Dictionary, etc.).

With this release being one of the most dramatic visual overhauls of macOS's design, I wanted to begin a collection chronicling the evolution of the system icons over the years. I've been rolling these out on social media over the past week and will continue to add to and update this collection slowly over the summer. Enjoy!
preview-1752036853593.png

macOS Icon History

Documenting the evolution of macOS system icons over the past several decades.

Earth 3 Streamline Icon: https://streamlinehq.combasicappleguy.com

This is an amazing article and website by Marcin Wichary, the man behind the excellent Shift Happens book.

…I had a realization that the totemic 1984 Mac control panel, designed by Susan Kare, is still to this day perhaps the only settings screen ever brought up in casual conversation.

I kept wondering about that screen, and about what happened since then. Turns out, the Mac settings have lived a far more fascinating life than I imagined, have been redesigned many times, and can tell us a lot about the early history and the troubled upbringing of this interesting machine.

Indeed, Wichary goes through multiple versions of Mac operating systems and performs digital paleontology, uncovering long lost Settings minutiae. It's also a great lesson in UI along the way. Be sure to click in the Mac screens.

preview-1752030135022.png

Frame of preference

A story of early Mac settings told by 10 emulators.

Earth 3 Streamline Icon: https://streamlinehq.comaresluna.org

Paul Worthington writing about the recent Cannes Festival of Creativity:

…nostalgia is rapidly becoming a major idea d’jour among marketers targeting that oh-so-desirable “Gen Z” demographic.

As a result, it should come as no surprise that if you were to walk around Cannes over the past month or so, you’d be forgiven for thinking brands no longer had any interest in the future: Lisa Frank notebooks. Tamagotchi cameos. Taglines from 1999. Brand after brand strapping itself to the past, seeking refuge in comfort. Instacart. Mattel. Burger King. Skoda. All treating relevance as if it were a rerun.

But along with nostalgia, another theme was present at Cannes—differentiation:

Cannes was also a parade of brands betting on something riskier. Something sharper. Something new. Liquid Death. Stripe. Tesla. Anduril. Companies building out from belief systems focused resolutely on what makes them unique. Making things you couldn’t have predicted because they weren’t remixes of the past—they were statements of the future.

Worthington argues that these two themes are diametrically opposed. Nostalgia brands are “fundamentally risk-averse” and feel safe. While differentiated brands are “risk-embracing,” betting that consumers are desperate for “something weird, sharp, and built from scratch.”

preview-1751949966152.png

Nostalgia Vs Differentiation

Beware winning today and losing the future.

Earth 3 Streamline Icon: https://streamlinehq.comoffkilter.substack.com

Stephen Heller, writing for PRINT magazine, revisits a long out-of-print book called Visual Persuasion by Stephen Baker, a creative director from the Mad Men era of advertising.

Although published in 1961, Visual Persuasion has as much relevance, vitality, insight, vision and spunk as any recently published book (including those that I’ve authored). The truth is this: I wish I had written it. Even though it is nearly 65 years out of print (and contains its share of outdated mores and stereotypes), it easily could still serve (with a minute refresh) to provide ideas to ward off what designers fear is the inevitable AI apocalypse—an end to original thinking and making, visual or otherwise.

One maxim, Heller notes:

Eye movements are based on conditioned reflexes. “Left-to-right habit makes our eyes travel clockwise in exploring a [layout],” Baker notes. The optical center of a page is slightly to the left. The tendency is to focus attention on a person’s eyes more than on any other part of their face. This mirrors one’s emotions with fair accuracy.
preview-1751949320516.jpeg

The Daily Heller: Visual Persuasion Hasn't Changed Since 1961

Steven Heller on the book he wishes he had written.

Earth 3 Streamline Icon: https://streamlinehq.comprintmag.com

Read past some of the hyperbole in this piece by Andy Budd. I do think the message is sound.

If you’re working at a fast-growth tech startup, you’re probably already feeling the pressure. Execs want more output with fewer people. Product and engineering are experimenting with AI tooling. And you’re being asked to move faster than ever — with less clarity on what the team should even own.

I will admit that I personally feel this pressure too. Albeit, not from my employer but from the chatter in our industry. I’m observing the younger companies experiment with the process, collapsing roles, and expanding responsilities.

As AI eats into the production layer, the traditional boundaries between design and engineering are starting to dissolve. Many of the tasks once owned by design will soon be handled by others — or by machines.

Time will tell when this becomes widespread. I think designers will be asked to ship more code. And PMs and engineers may ship small design tweaks.

The reality is, we’ll likely need fewer designers overall. But the ones we do need will be more specialised, more senior, and more strategically valuable than ever before.

You’ll want AI-literate, full-stack designers — people who are comfortable working across the entire product surface, from UX to code, and from interface to infrastructure. Designers who can navigate ambiguity, embrace new tooling, and confidently operate in the blurred space between design and engineering.

I don't know if I agree with the fewer number of designers. At least not in the near-term. The more AI is embedded into app experiences, the trend—I predict—will go in the opposite direction. The term "AI as material" has been floating around for a few months, but I think its meaning will morph. AI will be the new UI, and thus we need designers to help define those experiences.

preview-1751840519842.png

Design Leadership in the Age of AI: Seize the Narrative Before It’s Too Late

Design is changing. Fast. AI is transforming the way we work — automating production, collapsing handoffs, and enabling non-designers to ship work that once required a full design team. Like it or not, we’re heading into a world where many design tasks will no longer need a designer. If that fills you with unease, you’re not alone. But here’s the key difference between teams that will thrive and those that won’t: Some design leaders are taking control of the narrative. Others are waiting to be told what’s next.

Earth 3 Streamline Icon: https://streamlinehq.comandybudd.com