<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Guthrie Watson on Medium]]></title>
        <description><![CDATA[Stories by Guthrie Watson on Medium]]></description>
        <link>https://medium.com/@guthrie.watson?source=rss-d6841b505998------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*urkvAMOUQv98XPQ4FYy6nQ.jpeg</url>
            <title>Stories by Guthrie Watson on Medium</title>
            <link>https://medium.com/@guthrie.watson?source=rss-d6841b505998------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:51:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@guthrie.watson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tai Chi and the art of volume control]]></title>
            <link>https://medium.com/the-design-loop/tai-chi-and-the-art-of-volume-control-b4549c76d16a?source=rss-d6841b505998------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4549c76d16a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[sonos-app]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Guthrie Watson]]></dc:creator>
            <pubDate>Fri, 28 Aug 2026 11:31:01 GMT</pubDate>
            <atom:updated>2026-08-28T11:31:01.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXOLd2BZWmFycWH48GbWzQ.png" /></figure><h3>Why Sonos’s new volume control is more significant than it looks</h3><p>In May 2024, Sonos released a ground-up redesign of its app, not just a visual refresh, a complete rebuild of the technical foundation, replacing the older UPnP and SOAP-based system with a new, more cloud-dependent architecture. It was pitched as faster and better, and timed to launch alongside its first headphones, the Sonos Ace.[1][2] What followed was one of the more serious missteps in recent consumer tech. The new app shipped without long-standing features like sleep timers and alarms, broke accessibility support for VoiceOver and screen reader users, and left some longtime customers unable to control speakers they’d owned for years.[3][1] The impact was severe: Sonos delayed two major hardware launches, reportedly including a next-generation soundbar and a long-rumoured set-top box, to redirect engineering effort towards fixing the app. Revenue fell, around 100 staff were laid off, and by January 2025 the fallout had cost CEO Patrick Spence his job, with board member Tom Conrad stepping in as interim chief executive.[4][5][6]</p><p>It’s against that backdrop, over a year of apologies, patch cycles, and slowly rebuilt trust, that Sonos’s latest app redesign is worth paying attention to this new redesign.</p><p>I’ve a number of Sonos speakers and I remember this app relaunch, including the fact that they had done it as a big bang release, meaning they couldn’t easily roll back the release because they’d changed the underlying technical architecture. For months it was barely usable.</p><p>Each morning I open the Sonos app to set up music for my Tai Chi practice, the app is a key part of the process after the morning alarms it needs to be reset. I turn down the volume and pick a playlist, it needs to be a quiet but audible as an accompaniment to my daily routine. It’s a small, habitual task, one I’ve done hundreds of times. So when I opened the app recently and found the volume control had changed, nothing else, just that one small interaction, it caught my attention. Importantly the rest of the app hadn’t changed — no deleted features or connectivity issues.</p><figure><img alt="The Sonos App icon and a selection of Sonos product shots showing the connection between the app and the physical speakers." src="https://cdn-images-1.medium.com/max/1024/1*XVesObJfNVVejDvb3bZfSw.png" /></figure><h3>Why the app is the product</h3><p>Sonos speakers have almost no meaningful physical controls. No mute button. Nothing beyond basic on/off and volume on the hardware itself and some slightly tricky multi-room options (which involve long presses and don’t always work). Everything else, playing music, switching audio sources, setting alarms, configuring voice control, happens through the app. This isn’t a case of a “smart” add-on wrapped around a product that works fine without it, the way a smart water jug bolts an app onto something that was already a jug. With Sonos, the app is the control surface. If the app doesn’t work, the speakers effectively don’t either, and the hardware investment goes with it.</p><p>For a long time that’s the tension that defined the product. The hardware itself was always reviewed well: strong sound quality, easy home cinema setup, once configured they all worked well, including a robust multi-room experience that allowed you chain speakers seamlessly. Sonos understood the app was the only way to set up and really control their system, and that for many users it was something used daily. The problem it turned out was underinvestment, not neglect: they knew the app mattered but didn’t put in the work to match it, then rolled out sweeping changes without testing them properly. That gap barely touched people with one or two speakers, or anyone leaning on Bluetooth rather than the app. It hit hardest for the people running multi-room systems or home cinema setups, switching between speakers and music sources daily, exactly the use case where there’s no way around opening the app.</p><figure><img alt="The compact app control component showing volume and mute controls." src="https://cdn-images-1.medium.com/max/1024/1*M4jFNboQtKgWY9xgSoiq1A.png" /><figcaption>The compact app control component showing volume and mute controls.</figcaption></figure><h3>A different kind of rollout</h3><p>Sonos began rolling out the latest update on 14 July 2026.[7] The headline change is tabbed navigation at the bottom of the screen, replacing the stacked screens and gestures introduced in 2024 with a familiar Home, System and Search layout. Alongside it came the ability to sort and pin speakers and rooms, and a rebuilt volume interface on iOS, with Android to follow.[8][9] In the months before launch, interim CEO Tom Conrad had flagged all three as priorities: clearer navigation, a genuinely new volume interface, and more control over how players are listed and displayed.</p><p>What stands out isn’t only what changed, but how it arrived. The update was rolled out gradually, in phases, over roughly two weeks, rather than landing on every device at once. The new navigation and volume interface are opt-in, something you switch on deliberately rather than something imposed overnight. Set that against 2024, when the redesigned app arrived all at once, mandatory, barely tested, and stripped of features people relied on daily. This year’s approach clearly reflects lessons learned.</p><h3>The detail that stood out: a volume slider worth noticing</h3><p>Of everything in the update, it was the volume control that made me stop and pay attention, not because it’s the biggest change on paper, but because of how it felt to use. Tapping the slider now shifts the interface into a focused volume-control state. The slider itself is thicker, with plus and minus buttons at either end for small, precise adjustments. Drag it and the phone gives a faint haptic pulse with each increment, like turning a real dial rather than smearing a finger across glass. A numeric display confirms the current level as you go, read-only, feedback rather than input. And tucked into the same interaction is a mute toggle, a capability the hardware doesn’t have. Previously the only option was to turn everything off, or slide the volume down and then back up again once the interruption had passed. Now a brief interruption, someone at the door or a phone call, is just one tap away.</p><p>None of it required heavy engineering. It’s a handful of modest, well-considered choices that, together, turn a routine task into something that feels considered. It’s a small, useful illustration of what the rest of the redesign is reaching for: interface decisions made with real daily use in mind, rather than a coat of visual polish.</p><figure><img alt="Thicker slider, plus and minus controls, numbered, and mute affordance." src="https://cdn-images-1.medium.com/max/1024/1*Ojs9TxHT39RRF8OlfKaDQA.png" /><figcaption>Thicker slider, plus and minus controls, numbered, and mute affordance.</figcaption></figure><h3>The bigger shift this signals</h3><p>For years, Sonos used the app as a shop window for Sonos Radio and its various premium audio and subscription features, pushed prominently into a space where people mostly just wanted to control what they were listening to. That’s a crowded market where Sonos has no real advantage over Spotify or Apple Music, and competing there always felt like a distraction from what the company actually does well.</p><p>This redesign, and the careful, phased, opt-in way it’s being delivered, reads as a quiet admission of that. It’s a pivot toward Sonos’s genuine value: being the best possible control layer for whatever music service you already use, rather than trying to be a streaming service itself. Nothing about tabbed navigation or a rebuilt volume slider needed a large engineering investment. It needed clear-eyed product thinking about what people actually touch every day, a decision to invest there instead of chasing streaming ambitions that were unlikely to pay off, and the discipline to ship it properly this time rather than rushing it out the door.</p><p>There’s a familiar shape to this kind of recovery. When Steve Jobs returned to Apple in 1997, the company was spread thin across a sprawling product line, chasing every market it could justify rather than doing a small number of things well. His fix wasn’t a bigger roadmap, it was a smaller one: cut the product line down to a handful of machines, and put the focus back on the everyday experience of using them. The turnaround came from restraint and clarity, not from new ambition. Sonos, in a much smaller way, looks to be making the same kind of move: less concerned with expanding into what it isn’t, more focused on doing the core thing, letting people control their music, exceptionally well.</p><p>If Sonos brings that same care to the rest of the app, the case for doing so is hard to argue with: low-cost, high-impact, good for the business, and good for the people who just want their speakers to do what they’re told, reliably, every time.</p><p>Tomorrow morning I’ll open the app again, set the volume for Tai Chi, quiet enough not to dominate the room, and probably won’t think about it at all. That’s the point. The best interface is the one you stop noticing, and for the first time in a long while, Sonos seems to understand that the small, unnoticed moments are exactly where the trust gets rebuilt.</p><h3>References</h3><ol><li>Faster to use, but missing many features, the new Sonos app is a work in progress. Digital Trends, May 2024. <a href="https://www.digitaltrends.com/home-theater/sonos-app-redesign-2024-work-in-progress/">digitaltrends.com/home-theater/sonos-app-redesign-2024-work-in-progress</a></li><li>Pennell, A. What happened to the Sonos app? A technical analysis. LinkedIn, July 2024. <a href="https://www.linkedin.com/pulse/what-happened-sonos-app-technical-analysis-andy-pennell-wigwc">linkedin.com/pulse/what-happened-sonos-app-technical-analysis-andy-pennell-wigwc</a></li><li>2024: The year Sonos slipped. TechRadar, December 2024. <a href="https://www.techradar.com/televisions/2024-the-year-sonos-slipped">techradar.com/televisions/2024-the-year-sonos-slipped</a></li><li>Sonos Announces CEO Transition. Sonos Newsroom, 13 January 2025. <a href="https://newsroom.sonos.com/254650-sonos-announces-ceo-transition">newsroom.sonos.com/254650-sonos-announces-ceo-transition</a></li><li>Fitzgerald, D. Sonos CEO Patrick Spence is leaving following bungled app update. TechCrunch, 13 January 2025. <a href="https://techcrunch.com/2025/01/13/sonos-ceo-patrick-spence-is-leaving-following-app-update-disaster/">techcrunch.com/2025/01/13/sonos-ceo-patrick-spence-is-leaving-following-app-update-disaster</a></li><li>Sonos CEO leaving after botched app revamp led to customer revolt. Fortune, 13 January 2025. <a href="https://fortune.com/2025/01/13/sonos-ceo-patrick-spence-out-tom-conrad-in-botched-app-revamp-customer-revolt/">fortune.com/2025/01/13/sonos-ceo-patrick-spence-out-tom-conrad-in-botched-app-revamp-customer-revolt</a></li><li>14th July 2026, New Sonos App and Player Updates Now Available. Sonos Community, 14 July 2026. <a href="https://en.community.sonos.com/product-updates/14th-july-2026-new-sonos-app-player-updates-now-available-6934332">en.community.sonos.com/product-updates/14th-july-2026-new-sonos-app-player-updates-now-available-6934332</a></li><li>Sonos Tries to Repair Its App With Tabs, Better Volume Controls and Speaker Sorting. <a href="http://ecoustics.com/">ecoustics.com</a>, July 2026. <a href="https://www.ecoustics.com/news/sonos-app-update-2026/">ecoustics.com/news/sonos-app-update-2026</a></li><li>‘I’ve been waiting for this for ages’: The Sonos app’s new navigation, volume controls and speaker ordering are finally rolling out. TechRadar, July 2026. <a href="https://www.techradar.com/audio/ive-been-waiting-for-this-for-ages-the-sonos-apps-new-navigation-volume-controls-and-speaker-ordering-are-finally-rolling-out-though-you-might-not-get-them-right-away">techradar.com/audio/ive-been-waiting-for-this-for-ages-the-sonos-apps-new-navigation-volume-controls-and-speaker-ordering-are-finally-rolling-out-though-you-might-not-get-them-right-away</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4549c76d16a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-design-loop/tai-chi-and-the-art-of-volume-control-b4549c76d16a">Tai Chi and the art of volume control</a> was originally published in <a href="https://medium.com/the-design-loop">The Design Loop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Copy Across Dimensions: Building a Collaborative UX Writing Practice]]></title>
            <link>https://medium.com/the-design-loop/copy-across-dimensions-building-a-collaborative-ux-writing-practice-1b0bbd6045a1?source=rss-d6841b505998------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b0bbd6045a1</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-microcopy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-copywriting]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Guthrie Watson]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 11:31:01 GMT</pubDate>
            <atom:updated>2026-06-01T11:31:01.220Z</atom:updated>
            <content:encoded><![CDATA[<p>UX copy writing sits at the intersection of information architecture, interaction design, and the cultural specifics of language. It has to work across all three at once. When I recognised that, it became clear that copy couldn’t live outside of product design. It had to be part of the workflow itself. So I made a deliberate choice. Copy should be embedded in the design process from the start, worked through collaboratively, bringing our collective expertise to bear on that part of the work in focused, dedicated sessions.</p><p>The idea was straightforward enough. The practice of doing it has shown us something more: that shared ownership of copy changes what becomes possible. This piece reflects on what we’ve learned from taking that approach.</p><h3>Copy as UX, not content</h3><p>Our products sit between sustainability and mobility, offering flexible solutions designed to help users and organisations adapt to a rapidly evolving regulatory and transport landscape. For organisations, they provide the means to measure and report sustainability performance in line with global regulatory requirements. Our work in this context is to create copy as user experience for products. Copy that helps people use them to meet their goals as employees or organisations. We don’t provide copy as content. We provide copy as UX.</p><h3>Creating UX copy without a product copy specialist</h3><figure><img alt="Diagram of UX copy writing, a circular collaborative exercise. Copy creation, review sessions to finalised copy for hand off to the engineering build team." src="https://cdn-images-1.medium.com/max/1024/1*deEQziK9JDPRoeCdScHQVA.png" /></figure><h3>Copy sessions and collaboration</h3><p>Copy sessions have become a weekly discussion. Often about whether copy or UX/UI needs to be addressed. Do you alter part of the UX or adjust the copy? Where does the copy fit in the context of the experience’s information hierarchy? Does the interaction design negate the need for additional explanatory copy? Lastly, we consider the actual words. How will they translate? Are they already in the glossary? Do they need testing?</p><p>Answering these questions together in weekly copy sessions has meant a better UX process and higher performing copy.</p><h3>UX copy, more than just a UI label</h3><p>UX copy is multidimensional. It exists within an experience’s information hierarchy (UI layout), works within a digital application’s interaction space, that non-linear time defined by an app’s task space, as so well described by Brenda Laurel in Computers as Theatre (1991). On top of this, it has to work in a localised translation domain. Idioms, grammar, and culture come into play in order for people “reading” the experience to understand it. Lastly, the copy must be relevant to the language of the service or domain of the business providing it.</p><h3>First dimension: Information architecture</h3><p>If you look at a poster for a film in a bus stop or train station, there is an order in which you typically read the information. Top of the poster is usually the largest name of the film, maybe with a subtitle or a phrase like “in space no one can hear you scream”. Then typically either the director or actors, depending on how well known they are.</p><p>The importance of the information is structured so that even at a glance you grasp the important details first. It’s not always determined by the size of the type. It can be any combination of colour, typographic treatment, style, or position within the bounds of the poster.</p><p>The same pattern appears in screen and web design. Here, button backgrounds use your most striking brand colour, and titles and navigation frame the stage of action. The design of a mobile screen directs the eye to focus on the task at hand.</p><p>Contextual elements, navigational or functional tools, help you complete the task and focus your attention. Which is where we start to move into the next dimension.</p><figure><img alt="Photo by Kevin Luke on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*FI6NgM4uqnNZdYyxloO2Zw.jpeg" /></figure><h3>Second dimension: Interactions and time</h3><p>Like scenes in a play, our experience of software moves from one action or context to another. Some of these scenes are connected and may or may not be linear. Some have a start, middle, and end; others follow a more controlled, reflexive mode of interaction.</p><p>Context is carried forward with us as we move from one step to the next. Text is a key part of this multidimensional experience. The words we use help to frame and direct us through the experiences we interact with.</p><p>This balance isn’t instinctive at first. Over time the mix becomes more considered, with graphic icons, text, and white space balancing out the designs. The balance itself is a learnt reflex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i209DTbe5tsTyHDUgun9zg.png" /></figure><h3>Third dimension: Localisation</h3><p>The next dimension is the translation and localisation space. This space is tightly bound to the business language, where a contextual layer is added from the base language’s UX copy.</p><p>It’s not enough to literally or even correctly translate idioms and phrasing from the base language or culture. We must translate the business’s linguistic context, the meaning of the copy as it relates to the service delivered via the digital application.</p><p>KINTO Join supports more than ten languages now. We maintain one meaning across all languages. The user completing a task in English, our base language, should encounter the same intent and conceptual clarity regardless of whether they’re presented German, Spanish, or any of the other languages we serve.</p><p>Our approach has evolved to handle that complexity. We’ve built glossaries and style guides that carry forward not just words but the business context those words sit within. That material becomes the starting point for AI translation tools, which give us a first pass. But the real work happens when that output goes to human translators working in market. They’re the ones who catch where cultural adaptation risks diverging from the original intent.</p><p>We’ve also learned to write the base copy with translation in mind, keeping it simple and direct enough that adaptation across languages doesn’t require rewriting the meaning. And where we’re uncertain, we test. If something feels like it might not travel well, we validate it across the languages we support before it ships.</p><p>It’s a more rigorous process than we started with, and it demands investment. But it’s the only way to ensure that localisation isn’t just translation. It’s the practice of preserving a single user experience across different linguistic and cultural contexts.</p><h3>How does copy work in a multidimensional interactive space?</h3><p>Where and when should I use words? When is a graphic pictogram or illustration needed? When space is limited, as on a mobile device, how does this change what and how copy is used? If I have more space on a larger handheld or desk-based experience, how does this affect the choice of words? What about other languages, cultures, or needs. How does the text contribute to the accessibility of the app we’ve designed? How does this experience work for those using screen readers or other modes of interaction?</p><p>The answer to all these is very much dependent on the experience you are designing for. One thing is certain: it’s rarely useful to simply add or remove words. Most often it’s about context and picking the right words to suit the situation.</p><p>The constraints themselves teach you something about what the copy needs to do. When you’re writing copy that needs to work for someone using a screen reader, you’re forced to think differently about how words carry meaning without visual context. That rigour, writing within the constraint rather than around it, tends to make the copy work better for everyone else too.</p><h3>How do these dimensions affect what we write?</h3><p>Copy in the context of a task sits within the flow of an interaction and the hierarchy of a screen. Action-based copy sits in the present while contextual copy like navigation, headings, descriptions, or user-generated input surrounds it.</p><p>Contextual labelling copy mitigates the need for lengthy descriptive copy. A lot can be understood about an action users can take based on the experience and the contextual copy and elements that support it.</p><p>This brings us to an approach when reviewing and editing UX copy. It’s also why words aren’t just words in our products but an integral part of the designed interactive experience.</p><h3>Simplify, shorten, or delete the copy in context</h3><p>Adding more copy is rarely the answer to fixing an issue with your design but it’s often the one that even experienced designers initially reach for. In trying to shoehorn more explanation into limited space, say on a mobile screen, we can end up making things less clear.</p><p>The following approach has worked well for us. We try to simplify, shorten, or delete, and use context to drive understanding supported by the copy we write.</p><h3>Simplify and shorten</h3><p>Why use “undo last edit” when “undo” works just as well? In more complex settings we may consider “undo size”, “undo colour” and so on. It needs to be clear what can be undone, what action is performed by the affordance we’ve provided in the software we’ve designed.</p><p>“Undo my last action” as a label for an action might seem better because we are fully explaining what the button will do. But does it provide more information? In the context of writing a document, what else would we undo? What value do the additional words add?</p><h3>Delete</h3><p>Sometimes removing text is the solution. The trash can has been the symbol for deleting something in software for decades. It’s both a stand-in for the literal action of throwing something away and the act of removing some element entirely.</p><p>Combined with a warning colour like red, at least in a west European context, it reinforces the idea of removal or destruction. Deleting words either partially or entirely often simplifies an experience. Being direct when space is limited, like in a mobile screen, can improve the comprehension of that experience.</p><p>If you have the possibility of undoing that action presented after the deletion then the experience becomes learnable. Since delete and undo are common patterns in many software experiences we can rely on that familiarity. These kinds of global patterns can be useful. But they raise questions worth sitting with: what words actually need to be in your glossary and style guide? When and where do you use those guides in your workflow? How do they become tools that work whether you’re prompting AI for a first pass, writing copy yourself, or handing context to translators? The guides don’t need to be elaborate, but they do need to exist and function, to be documents that actually shape the decisions you make, not just reference material that sits unused.</p><h3>UX copywriting for the user’s context, not design or developer tools</h3><p>We design and build software with databases, visual design, and code writing tools. One of the most common patterns is to write copy that relates to those tools rather than what people understand their needs and actions to be.</p><p>Vera, an HR system, uses the phrase “Insert record” instead of “add holiday” or “request annual leave”. It comes close to breaking the experience. After exploring the interface as a user you realise they must be referring to adding some leave into the system.</p><p>As a user I want to be assured that my intention, to request annual leave, is communicated with the system that records it. As a software engineer I need the database to insert that record and display it, but display it in a way that I understand in relation to the task I am trying to complete. As a user I think in terms of the task I’m trying to complete, not what an engineer needs to do to satisfy my request.</p><p>It is a surprisingly common pattern for those drafting copy for software. As authors of UX copy we need to switch modes.</p><p>Designers and engineers need to put themselves in the shoes of people using their tools. If I use my engineering or design language to explain the function of an affordance, how can users then understand what options they have to complete the task they started?</p><p>For UX copy we want to develop a common shared language that everyone uses and that has clearly defined meaning in the context we use it. It should relate to the purpose of the software we designed, not the tools we use to create it.</p><p>To be clear, it is rarely a designer’s or engineer’s fault that this happens. Ever shorter deadlines and release cycles drive the business to rush development without doing the essential discovery processes that would provide them and the team with the feedback needed to write better UX copy.</p><h3>Coda</h3><p>Our weekly copy sessions have become something different from what we anticipated. What started as collaborative reviews of labels and microcopy has evolved into design conversations where we’re thinking through the full dimensional complexity of how words work in context. We’ve learned to spot patterns across hierarchy, interaction, and language that we might have missed working in isolation. That shared language has made it possible to explore options we wouldn’t have considered before, and to move past surface-level fixes into understanding how copy and design are inseparable.</p><p>When copy is treated as an integral part of the design process rather than something that comes after, the whole practice shifts. The multidimensional nature of UX copy becomes visible to everyone, and with it, the possibility of moving through that complexity together.</p><h3>References</h3><p>Laurel, B. (1991). Computers as Theatre. Addison-Wesley.</p><h3>Links</h3><p><a href="https://www.oreilly.com/library/view/computers-as-theatre/9780133390889/">https://www.oreilly.com/library/view/computers-as-theatre/9780133390889/</a></p><p><a href="https://www.nngroup.com/articles/content-strategy-vs-ux-writing/#:~:text=UX%20writing%20involves%20creating%20clear,guides%20people%20through%20an%20experience">https://www.nngroup.com/articles/content-strategy-vs-ux-writing/#:~:text=UX%20writing%20involves%20creating%20clear,guides%20people%20through%20an%20experience</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b0bbd6045a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-design-loop/copy-across-dimensions-building-a-collaborative-ux-writing-practice-1b0bbd6045a1">Copy Across Dimensions: Building a Collaborative UX Writing Practice</a> was originally published in <a href="https://medium.com/the-design-loop">The Design Loop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Apple’s Hidden ‘Animation Effects’ Has Restored Emotional Expression to Text Messages]]></title>
            <link>https://medium.com/the-design-loop/how-apples-hidden-animation-effects-has-restored-emotional-expression-to-text-messages-f55b0d44757d?source=rss-d6841b505998------2</link>
            <guid isPermaLink="false">https://medium.com/p/f55b0d44757d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[emotional-ux]]></category>
            <category><![CDATA[ui-animation]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Guthrie Watson]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 14:49:25 GMT</pubDate>
            <atom:updated>2025-11-05T14:49:25.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s not just animation — it’s a restoration of emotional nuance for the messages we send every day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RX85dzWhKd4ip4PDb24nyw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ym1H_y9WjyA_OiNvxL0PWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bnWJ_iSMX11M6XSjIxQY0g.jpeg" /><figcaption>The animation effects menu is almost unnoticeable but hides a small kit of reusable animations that bring new delight to your messages.</figcaption></figure><p>As a UX design lead, I’m obsessed with the details of interactions most people never notice. Those tiny details that, upon closer inspection, reveal a profound understanding of human behaviour.</p><p>I recently stumbled upon one of these details in the most mundane of places: signing off a text to my partner.</p><p>As I typed my customary string of “x’s,” something new appeared in the suggestion bar above my keyboard: the word “Bloom.” Tapping it transformed my simple kisses into a gentle, pulsing animation — each ‘x’ swelling with affection before softly receding.</p><p>This wasn’t just a cute one off effect. It was a moment of genuine insight encapsulated in a flexible new feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76PCpss1dmh5l1BDcydDfg.gif" /><figcaption>The animation effects hint is subtle but a fun way to discover this recent messages feature.</figcaption></figure><h3>Beyond Emoji: The Rise of Animated Expression</h3><p>Text messaging has been functionally static for years. Emojis added a vocabulary of emotions, and features like photos and voice notes borrowed from other mediums. But Apple’s message effects — particularly the text-specific ones like Bold, Italic, and Bloom — are different. They are native to the message itself.</p><p>What struck me was the thoughtfulness. The designers didn’t just build an animation tool; they observed that millions of people sign off with “x’s” and created a way to make that gesture more expressive. They placed the prompt in a context where it would be discovered naturally, with zero cost to ignore.</p><p>This is a masterclass in user-centric design: surfacing capability through context, not instruction.</p><h3>The Co-Authoring of Meaning: Why This is a Game-Changer</h3><p>Compare this to the full-screen effects for birthdays or New Year’s. Those are fun, but their meaning is fixed and their novelty wears off quickly. The “Bloom” effect is different because its meaning is co-authored by the writer.</p><p>The animation doesn’t exist in a vacuum. It derives its power from the words you choose.</p><ul><li>Use “Bold” on “I need this NOW” and you reinforce urgency.</li><li>Use “Bloom” on “Congratulations!” and you amplify joy.</li><li>Use “Echo” on “Are you sure…?” and you introduce doubt or playful mystery.</li></ul><p>This flexibility transforms a simple feature into a hidden gem. It allows us to reinforce an obvious intention, subvert it, or add entirely new layers of nuance. It brings back a spectrum of expressiveness that was lost when we moved from vocal inflection and body language to flat, black-and-white text.</p><h3>The Takeaway: Delight is Not Frivolous</h3><p>It’s easy to dismiss features like these as frivolous. But they aren’t. They empower us to be more creative and expressive in our daily interactions. They turn the utilitarian act of sending a text into a moment of connection and delight for both the sender and receiver.</p><p>In the quest to build products that are useful and efficient, we must never forget to leave room for surprise, nuance, and humanity. That’s the real innovation here — not the animation itself, but the space it creates for us to be more human.</p><h4>References</h4><p><a href="https://support.apple.com/en-gb/guide/iphone/iphe5c5af4d4/ios">https://support.apple.com/en-gb/guide/iphone/iphe5c5af4d4/ios</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f55b0d44757d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-design-loop/how-apples-hidden-animation-effects-has-restored-emotional-expression-to-text-messages-f55b0d44757d">How Apple’s Hidden ‘Animation Effects’ Has Restored Emotional Expression to Text Messages</a> was originally published in <a href="https://medium.com/the-design-loop">The Design Loop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>