<?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 Dilys Lim on Medium]]></title>
        <description><![CDATA[Stories by Dilys Lim on Medium]]></description>
        <link>https://medium.com/@limdilys?source=rss-fec01c10eb8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pLSdDWEwJibJJFfQaIsrXg@2x.jpeg</url>
            <title>Stories by Dilys Lim on Medium</title>
            <link>https://medium.com/@limdilys?source=rss-fec01c10eb8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@limdilys/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[Designing the unseen: Introducing motion design and haptics in a Design System]]></title>
            <link>https://medium.com/singtel-experience-design/designing-the-unseen-introducing-motion-design-and-haptics-in-a-design-system-6994d51d8d06?source=rss-fec01c10eb8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6994d51d8d06</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[motion-design]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[haptics]]></category>
            <dc:creator><![CDATA[Dilys Lim]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 04:00:42 GMT</pubDate>
            <atom:updated>2026-03-11T04:00:42.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o2S4ALmAXqR1g_PxjS1yLw.png" /></figure><p>Design systems are often discussed in terms of visible elements like colour, typography, spacing, and components. But as our product scaled, it became clear that some of the most impactful parts of the experience were missing.</p><p>Motion design, micro-interactions, and haptics were largely absent from the system. Not because they weren’t valuable, but because they’re <em>hard to see, harder to spec, and easy to ignore</em>. And when something isn’t tangible, it’s often forgotten.</p><p>The result was a product that functioned well, but didn’t always feel complete.</p><h3><strong>The issue with the existing design system</strong></h3><p>Without shared guidance for motion and haptics, decisions were made locally. Over time, the product developed inconsistencies, with some success states animated while others remained static.</p><p>From a design system perspective, this revealed a scalability and governance gap in how interaction feedback was defined and scaled.</p><h3><strong>Defining the role</strong></h3><p>Before designing tokens or patterns, we aligned on the role motion should play at a system level. Motion needed to be scalable, functional, and communicative. Motion should exist to guide attention, and clarify outcomes. Haptics followed the same principle. They were treated as feedback, not embellishment.</p><h3>Creating motion tokens for scale</h3><p>To make motion reusable and predictable, it had to be tokenised.</p><p>Rather than offering unlimited durations and easing curves, we intentionally constrained choices early to reduce decision fatigue as the system scaled.</p><p>For motion tokens, I’ve defined three easing types:<br>• Standard<br>• Emphasis standard<br>• Emphasis decelerate</p><p>As for duration, it has two tiers:<br>• Short (used for small utility-focused transitions)<br>• Long (used for expressive transitions)</p><p>These combinations were tested on high-frequency components, such as card interaction, card morph, swiping interaction, and state transition.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fddiillyyss%2Fembed%2Fpreview%2FqENMOGj%3Fdefault-tabs%3Dhtml%252Cresult%26height%3D600%26host%3Dhttps%253A%252F%252Fcodepen.io%26slug-hash%3DqENMOGj&amp;display_name=CodePen&amp;url=https%3A%2F%2Fcodepen.io%2Fddiillyyss%2Fpen%2FqENMOGj&amp;image=https%3A%2F%2Fshots.codepen.io%2Fusername%2Fpen%2FqENMOGj-512.jpg%3Fversion%3D1770367626&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/b10f64e8965a4593e88337eea7d0e2cc/href">https://medium.com/media/b10f64e8965a4593e88337eea7d0e2cc/href</a></iframe><p>Using Framer and Figma, I explored variations, tested them in context, and eliminated options that felt redundant or ambiguous. The focus was on predictability. When motion behaves consistently, users don’t need to relearn the interface.</p><h3>Mapping haptics to intent, not components</h3><p>Haptics introduced a different challenge: they’re invisible.</p><p>Before defining usage, we needed to understand what haptics were actually available on iOS and Android. I worked with developers to document native haptic options and housed them directly in the design library so designers could feel them on real devices.</p><p>The bigger question wasn’t which haptic to use, but what haptics should be tied to. I explored applying haptics to all buttons, but this quickly felt overwhelming and meaningless.</p><p>In conclusion, haptics should be scenario-based rather than component-based. They should be tied to intent, such as confirming high-stakes actions, completing purchase flows, and affirming irreversible decisions.</p><p>If everything vibrates, nothing feels important.</p><h3>Applying motion meaningfully</h3><p>Once the foundations were in place, motion could be applied more intentionally through patterns like confirmation states, alerts, loaders, and progress indicators, as well as micro-interactions such as animated icons triggered by user actions.</p><figure><img alt="Alert, success, and pending status icons animate when a task is completed, with haptic feedback to reinforce the action." src="https://cdn-images-1.medium.com/max/400/1*68E9CqUTAJP5RvBBMRGuYA@2x.gif" /><figcaption>Alert, success, and pending icons animate upon task completion with haptic feedback.</figcaption></figure><figure><img alt="Animated icons used in the app’s bottom navigation, showing the transition from inactive to active state when tapped." src="https://cdn-images-1.medium.com/max/300/1*r52Wfr6gLkm7FSQWV3QFoA@2x.gif" /><figcaption>Bottom navigation icons animate when tapped to indicate the active state.</figcaption></figure><h3>Current status: concept to implementation</h3><p>At the time of writing, this motion and haptics system has not yet been built. Implementation discussions with engineering are ongoing.</p><p>The work currently exists as:<br>• Defined principles<br>• Motion tokens<br>• Interaction patterns<br>• Prototypes and documentation</p><h3>Closing thoughts</h3><p>Motion and haptics are often overlooked because they don’t show up in static mockups. But when treated as system primitives, they become powerful tools for coherence and usability.</p><p>Designing the unseen isn’t about adding more. It’s about ensuring every signal has meaning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6994d51d8d06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/singtel-experience-design/designing-the-unseen-introducing-motion-design-and-haptics-in-a-design-system-6994d51d8d06">Designing the unseen: Introducing motion design and haptics in a Design System</a> was originally published in <a href="https://medium.com/singtel-experience-design">Experience Design @ Singtel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>