<?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 Jagadeesh on Medium]]></title>
        <description><![CDATA[Stories by Jagadeesh on Medium]]></description>
        <link>https://medium.com/@iam.hari?source=rss-a9429275e78e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VfT_YegQB4Mo7ZIz9tbgMg.jpeg</url>
            <title>Stories by Jagadeesh on Medium</title>
            <link>https://medium.com/@iam.hari?source=rss-a9429275e78e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:48:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iam.hari/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[How to make typography effortlessly right for every screen size. exactly like Apple.]]></title>
            <link>https://medium.com/@iam.hari/how-to-make-typography-effortlessly-right-for-every-screen-size-1a82ece4926d?source=rss-a9429275e78e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a82ece4926d</guid>
            <dc:creator><![CDATA[Jagadeesh]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 17:29:07 GMT</pubDate>
            <atom:updated>2026-03-05T17:31:01.528Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a moment when you’re browsing apple.com and something feels… <em>*right*</em>. Not just the products. The <em>*text*</em>. The headline on your iPhone reads like it was written for that exact screen. Open the same page on your MacBook and the same headline expands gracefully, filling the wider canvas without a single awkward gap. Shrink the browser window and it compresses back — smooth, continuous, inevitable.</p><p>This isn’t magic. It’s math. Specifically, it’s a hybrid typography system that combines two very different CSS techniques, deployed with surgical precision. After spending time reverse-engineering apple.com and rebuilding it from the ground up, here’s everything I learned.</p><h4><strong>The Question Nobody Asks (But Should)</strong></h4><p>Most articles about responsive typography will confidently tell you: <em>*”Just use `clamp()`! Problem solved!”*</em></p><p>And they’re not wrong, exactly. `clamp()` is a genuinely wonderful CSS function. But here’s the thing Apple figured out that the generic advice misses:</p><blockquote><strong>Different text has different jobs. Different jobs need different tools.</strong></blockquote><p>A 72px hero headline and a 17px body paragraph are solving completely separate problems. Treating them identically is like using the same tire pressure for a racing car and a school bus.</p><p>Apple uses two fundamentally different scaling strategies:</p><p>1. <strong>**Fluid scaling with `clamp()`**</strong> — for display text (hero, H1–H4)</p><p>2. <strong>**Discrete breakpoint stepping**</strong> — for body, caption, and label text</p><p>Let’s understand why.</p><p>— -</p><p><strong>## Part 1: The Fluid Side — CSS `clamp()` and Slope-Intercept Math</strong></p><p>`clamp()` takes three values: a minimum, a preferred, and a maximum.</p><p>```css</p><p>font-size: clamp(3rem, 1.5238vw + 2.629rem, 4rem);</p><p>```</p><p>The middle value — the <em>*preferred*</em> — is where the magic lives. It’s a linear equation in the form `y = mx + b`, where `x` is the viewport width. As the viewport grows, the font size grows proportionally, until it hits the maximum cap.</p><p>The math to derive those coefficients isn’t arbitrary. It’s slope-intercept:</p><p>```</p><p>Given: min size at 390px viewport = 48px</p><p>max size at 1440px viewport = 64px</p><p>slope = (64–48) / (1440–390)</p><p>= 16 / 1050</p><p>= 0.015238 → 1.5238vw</p><p>intercept = 48 — (0.015238 × 390)</p><p>= 48–5.943</p><p>= 42.057px → 2.629rem</p><p>Result: clamp(3rem, 1.5238vw + 2.629rem, 4rem)</p><p>```</p><p>That’s your H1: 48px on a 390px iPhone, 64px on a 1440px desktop, scaling smoothly between them. Every display heading in the system gets its own unique slope, calculated the same way.</p><p>&gt; <strong>**Why `rem` for min/max and not `px`?**</strong> Accessibility. If a user sets their browser font size to 20px for readability, `rem` values scale with that preference. `px` values ignore it entirely. Using `rem` means your system respects user zoom — a requirement under WCAG 1.4.4.</p><p>— -</p><p><strong>## Part 2: The Two Scales — Because One Ratio Can’t Serve All Viewports</strong></p><p>Here’s a subtlety that most implementations miss. Apple doesn’t interpolate between a single type scale. They interpolate between <em>*two different scales with two different ratios*</em>.</p><p>| Viewport | Scale Ratio | Character |</p><p>| — -| — -| — -|</p><p>| 390px (iPhone) | 1.200 (Minor Third) | Compact, space-efficient |</p><p>| 1440px (Desktop) | 1.250 (Major Third) | Expansive, dramatic |</p><p>Why? Because a narrow column needs a gentler hierarchy — too much contrast between heading and body looks aggressive. A wide screen has room to breathe, and a larger ratio creates the sweep you want.</p><p>Each heading step gets its own min and max derived from the two scales:</p><p>```css</p><p>/* Primitive scale tokens */</p><p>— scale-sm-4xl: 56px; /* 390px viewport, 1.200 ratio */</p><p>— scale-lg-4xl: 80px; /* 1440px viewport, 1.250 ratio */</p><p>/* Fluid token — interpolates between the two */</p><p>— fluid-hero: clamp(3.5rem, 2.2857vw + 2.943rem, 5rem);</p><p>```</p><p>This is the technique Utopia.fyi popularised: fluid interpolation between two complete modular scales. Apple arrived at the same solution independently — or perhaps inspired Utopia. Either way, it’s the right answer.</p><p>— -</p><p><strong>## Part 3: The Discrete Side — Why Body Text Never Uses `clamp()`</strong></p><p>Now here’s the counterintuitive part. All that fluid-scaling cleverness? Apple deliberately <em>*doesn’t*</em> apply it to body text.</p><p>Body text on apple.com uses hard breakpoint steps:</p><p>```css</p><p>/* Mobile first: 16px */</p><p>— text-body-size: 16px;</p><p>— text-body-line-height: 24px;</p><p>/* At 744px (iPad): snap to 17px */</p><p>@media (min-width: 744px) {</p><p>— text-body-size: 17px;</p><p>— text-body-line-height: 28px;</p><p>}</p><p>/* And that’s it. 17px all the way to 27-inch iMac. */</p><p>```</p><p>Apple caps body text at 17px regardless of how wide the screen gets. A 2560px iMac display gets the same 17px body text as an iPad.</p><p>This seems shocking until you think about it from first principles:</p><p><strong>**Reading comfort isn’t about viewport width — it’s about reading distance.**</strong> You sit roughly the same distance from your phone and your laptop. A 14px body on mobile is too small because of <em>*pixel density and physical size*</em>, not screen width. Cranking body text up to 24px on a wide monitor would be grotesque — you’d read three words per line.</p><p>There’s also a grid alignment argument. Body text needs its line heights to snap to the 4px baseline grid. `clamp()` produces irrational numbers like `17.284px` — you can’t reliably snap that to a 4px grid. Discrete values like `24px` and `28px` are always clean multiples of 4.</p><p>— -</p><p><strong>## Part 4: The Five Device Tiers</strong></p><p>The breakpoints aren’t arbitrary — they map directly to Apple’s own device lineup:</p><p>| Breakpoint | Name | Targets |</p><p>| — -| — -| — -|</p><p>| &lt; 390px | Compact | iPhone SE, older small phones |</p><p>| 390–743px | Small | iPhone 16, modern flagship iPhones |</p><p>| 744–1023px | Medium | iPad mini, iPad Air |</p><p>| 1024–1439px | Large | iPad Pro 11&quot;, MacBook Air |</p><p>| ≥ 1440px | XLarge | MacBook Pro, iMac |</p><p>This matters because you’re not designing for abstract viewport widths. You’re designing for the specific screens your users actually hold in their hands or sit in front of. Anchoring the scale to real devices gives you something to test against.</p><p>— -</p><p><strong>## Part 5: Optical Letter Spacing — The Detail Nobody Talks About</strong></p><p>Typography at scale has an optical problem: the same typeface that looks perfectly spaced at 16px looks <em>*gappy*</em> at 72px. The letters appear to drift apart. This isn’t an illusion — it’s geometry. At large sizes, the absolute spacing between glyphs becomes more visually significant relative to the stroke widths.</p><p>The fix is optical letter spacing — systematically tightening tracking as size increases:</p><p>```css</p><p>/* Small text: breathe */</p><p>— text-label-tracking: 0.03em; /* 11px: positively spaced */</p><p>— text-caption-tracking: 0.01em; /* 13px */</p><p>— text-body-tracking: 0em; /* 16–17px: neutral */</p><p>/* Display text: compress */</p><p>— text-h4-tracking: -0.02em; /* 28–33px */</p><p>— text-h3-tracking: -0.025em; /* 34–41px */</p><p>— text-h2-tracking: -0.03em; /* 40–51px */</p><p>— text-h1-tracking: -0.035em; /* 48–64px */</p><p>— text-hero-tracking: -0.04em; /* 56–80px */</p><p>```</p><p>This mirrors how SF Pro itself works. Apple’s system font actually ships in two variants — SF Pro Text (for sizes below ~20px) and SF Pro Display (for larger sizes) — with the Display variant having tighter default spacing. On the web, where we can’t use SF Pro directly, we replicate this optical correction manually through `letter-spacing`.</p><p>— -</p><p><strong>## Part 6: Line Height Strategy — The Two Regimes</strong></p><p>There’s a clean division in how line heights are set:</p><p><strong>**Body and small text: absolute pixel values.**</strong></p><p>```css</p><p>— text-body-line-height: 24px; /* 6 × 4px grid */</p><p>— text-h5-line-height: 32px; /* 8 × 4px grid */</p><p>```</p><p>This keeps them snapped to the baseline grid. The line heights are predictable integers that compose cleanly with other layout elements.</p><p><strong>**Display text: unitless ratios.**</strong></p><p>```css</p><p>— text-hero-line-height: 1.05;</p><p>— text-h1-line-height: 1.06;</p><p>— text-h2-line-height: 1.07;</p><p>```</p><p>Why? Because the alternative is absurd. If hero text is 80px and you set `line-height: 96px`, that’s fine. But if the user zooms in and hero becomes 120px, a fixed 96px line height will cause lines to overlap. A unitless ratio of 1.05 means the line height always stays proportional to the actual rendered size, no matter what.</p><p>— -</p><p><strong>## Part 7: The Three-Layer Token Architecture</strong></p><p>The whole system is organised in three tiers, and this structure is what makes it maintainable at scale:</p><p><strong>**Layer 1 — Global Constants**</strong></p><p>```json</p><p>{</p><p>“grid-unit”: { “value”: “4px”, “$type”: “dimension” },</p><p>“scale-ratio-sm”: { “value”: “1.200”, “$type”: “number” },</p><p>“scale-ratio-lg”: { “value”: “1.250”, “$type”: “number” }</p><p>}</p><p>```</p><p>Set once. Never referenced directly in components. The source of truth for the entire system.</p><p><strong>**Layer 2 — Primitive Scale Values**</strong></p><p>```json</p><p>{</p><p>“scale”: {</p><p>“small”: {</p><p>“4xl”: { “value”: “56px”, “$type”: “dimension” }</p><p>},</p><p>“large”: {</p><p>“4xl”: { “value”: “80px”, “$type”: “dimension” }</p><p>}</p><p>},</p><p>“fluid”: {</p><p>“hero”: {</p><p>“value”: “clamp(3.5rem, 2.2857vw + 2.943rem, 5rem)”,</p><p>“$type”: “dimension”</p><p>}</p><p>}</p><p>}</p><p>```</p><p>The raw mathematical outputs. Still not used directly in components — they’re the building blocks for Layer 3.</p><p><strong>**Layer 3 — Semantic Role Tokens**</strong></p><p>```json</p><p>{</p><p>“text-hero-size”: { “value”: “{fluid.hero}”, “$type”: “dimension” },</p><p>“text-body-size”: { “value”: “16px”, “$type”: “dimension” },</p><p>“text-body-line-height”: { “value”: “24px”, “$type”: “dimension” }</p><p>}</p><p>```</p><p>These are the <em>*only*</em> tokens that components should ever reference. They’re named by what they <em>*do*</em>, not what they <em>*are*</em>. ` — text-body-size` is stable even if the underlying values change.</p><p>This architecture follows the W3C Design Tokens Community Group (DTCG) format, which means it plugs directly into Tokens Studio, Style Dictionary, or Theo without conversion.</p><p>— -</p><p><strong>## Part 8: The Final CSS</strong></p><p>Putting it all together, the complete system in CSS looks like this:</p><p>```css</p><p>/* ── Fluid display tokens ─────────────────────────────── */</p><p>:root {</p><p>— fluid-hero: clamp(3.5rem, 2.2857vw + 2.943rem, 5rem);</p><p>— fluid-4xl: clamp(3rem, 1.5238vw + 2.629rem, 4rem);</p><p>— fluid-3xl: clamp(2.5rem, 1.0476vw + 2.245rem, 3.1875rem);</p><p>— fluid-2xl: clamp(2.125rem, 0.6667vw + 1.9625rem, 2.5625rem);</p><p>— fluid-xl: clamp(1.75rem, 0.4762vw + 1.634rem, 2.0625rem);</p><p>}</p><p>/* ── Semantic tokens — mobile first ──────────────────── */</p><p>:root {</p><p>/* Display: fluid */</p><p>— text-hero-size: var( — fluid-hero);</p><p>— text-hero-line-height: 1.05;</p><p>— text-hero-tracking: -0.04em;</p><p>— text-h1-size: var( — fluid-4xl);</p><p>— text-h1-line-height: 1.06;</p><p>— text-h1-tracking: -0.035em;</p><p>/* Body: discrete */</p><p>— text-body-size: 16px;</p><p>— text-body-line-height: 24px;</p><p>— text-body-tracking: 0em;</p><p>— text-caption-size: 13px;</p><p>— text-caption-line-height: 20px;</p><p>— text-caption-tracking: 0.01em;</p><p>— text-label-size: 11px;</p><p>— text-label-line-height: 16px;</p><p>— text-label-tracking: 0.03em;</p><p>}</p><p>/* ── Discrete body steps ──────────────────────────────── */</p><p>@media (min-width: 744px) {</p><p>:root {</p><p>— text-body-size: 17px;</p><p>— text-body-line-height: 28px;</p><p>— text-caption-size: 14px;</p><p>— text-label-size: 12px;</p><p>}</p><p>}</p><p>```</p><p>That’s it. No JavaScript. No runtime calculations. The browser does the math.</p><p>— -</p><p><strong>## Part 9: What a Live Type Meter Reveals</strong></p><p>One of the most instructive things you can build alongside a system like this is a <em>*live type meter*</em> — a tool that reads `getComputedStyle(element).fontSize` in real time and displays the actual computed pixel value for every role as you resize the browser.</p><p>```javascript</p><p>function getComputedPx(el) {</p><p>return Math.round(</p><p>parseFloat(getComputedStyle(el).fontSize)</p><p>);</p><p>}</p><p>// Create invisible probe elements for each role</p><p>const roles = [‘hero’, ‘h1’, ‘h2’, ‘body’, ‘caption’, ‘label’];</p><p>const probes = {};</p><p>roles.forEach(role =&gt; {</p><p>const el = document.createElement(‘span’);</p><p>el.className = `text-${role}`;</p><p>document.body.appendChild(el);</p><p>probes[role] = el;</p><p>});</p><p>// Read sizes on every resize</p><p>window.addEventListener(‘resize’, () =&gt; {</p><p>roles.forEach(role =&gt; {</p><p>const size = getComputedPx(probes[role]);</p><p>document.getElementById(`sz-${role}`).textContent = size;</p><p>});</p><p>});</p><p>```</p><p>What you see when you drag the browser edge is instructive: the hero and heading values change <em>*continuously*</em> — 48, 49, 50, 51… — while body text stays locked at 16 until the browser crosses 744px, at which point it <em>*snaps*</em> to 17. The discrete nature of the body scaling becomes viscerally obvious. You can feel the system’s intentionality.</p><p>— -</p><p><strong>## The Key Insight, One More Time</strong></p><p>The most important thing this project revealed isn’t any individual technique. It’s the <em>*philosophy*</em>:</p><p><strong>**Apple doesn’t use `clamp()` everywhere because they shouldn’t.**</strong> They use it where it creates genuine value — marketing text that needs to fill space dramatically. They deliberately <em>*avoid*</em> it where it would cause problems — reading text where comfort and grid alignment matter more than smooth transitions.</p><p>Most CSS tutorials present `clamp()` as an upgrade from breakpoints. Apple’s implementation suggests they’re not in competition. They’re complementary tools for complementary problems:</p><p>- <strong>**Display hierarchy**</strong> → fluid, dramatic, viewport-responsive</p><p>- <strong>**Reading comfort**</strong> → discrete, predictable, grid-snapped</p><p>The elegance isn’t in the CSS tricks. It’s in knowing which trick to reach for.</p><p>— -</p><p><strong>## Further Reading</strong></p><p>- [Utopia.fyi](https://utopia.fyi/) — the best fluid type calculator, built on the same slope-intercept math</p><p>- [Every Layout](https://every-layout.dev/) — CSS composition patterns that pair well with a token-based type system</p><p>- [W3C Design Tokens Community Group](https://www.w3.org/community/design-tokens/) — the emerging standard for token file formats</p><p>- [WCAG 1.4.4](https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html) — why using `rem` for clamp min/max isn’t just good practice, it’s an accessibility requirement</p><p>— -</p><p><em>*The complete system — `typography.css`, `tokens.json`, and interactive demo pages — was built iteratively over a working session. The live demo includes a type meter, bar chart comparison, breakpoint timeline, and in-context editorial layout. Open the demo in a browser and drag the edge to see every concept in this article made visible.*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a82ece4926d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First Meditation.]]></title>
            <link>https://medium.com/@iam.hari/the-first-meditation-91cf8e2308bb?source=rss-a9429275e78e------2</link>
            <guid isPermaLink="false">https://medium.com/p/91cf8e2308bb</guid>
            <dc:creator><![CDATA[Jagadeesh]]></dc:creator>
            <pubDate>Thu, 11 Apr 2024 06:53:40 GMT</pubDate>
            <atom:updated>2024-04-11T06:53:40.811Z</atom:updated>
            <content:encoded><![CDATA[<p>So this happened while I was studying in school; class seven. It was a Friday and the last session of that day. Fridays used to bring an extra energy level for most us boys in the class. Ha, the joy of the weekends; still continues while working in Cognizant. ☺<br>Fridays were special in a different way back then. As school kids our main adventures were cycle riding, cricket (from morning to evening!), plunging into the nearby beautiful river in search of the well rounded pebbles. No Facebook, no Internet, no Television (believe me!). Mango trees looked like Mt.Everest for us. And we climbed many. The only thing perhaps differentiated us from monkeys during the weekends was perhaps, we had to do some homework. So it is natural that may be I developed a monkey mind.</p><p>Let me go back to that Friday. The last session was for the drawing class. Our drawing teacher was well known for his brilliant oil paintings, a true born-talent who could make photo-realistic pictures with a charcoal pencil. A perfectionist from whom I have learned a lot. He was also very strict and kind at the same time. Like most school teachers were.</p><p>All of us in the class were expecting to finish some drawing exercises and then take a leap into our weekend freedom. But then our teacher, after taking his seat, told us to close our drawing books, In fact he told us to pack our bags and just take a paper and pencil out. We were confused and some of us thought he will let us leave the class little early. The already buzzing class room got little restless and a bit noisy.</p><p>And he told this.</p><p>“Let’s do something different today. Sit silently for 3 minutes observing your whatever thoughts you think. Then write down all the thoughts from the first thought which came to your mind to the last one on the sheet of paper in front of you.”</p><p>There was a total outcry in the class. We were constantly told to read, to write, to solve, to answer and there by to think. But no one ever told us to just observe our thoughts. Our teacher gave the signal to begin the ‘silently sitting’ session.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91cf8e2308bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mindset of a UX Designer. (Part 1)]]></title>
            <link>https://medium.com/@iam.hari/mindset-of-a-ux-designer-part-1-eb08af408e34?source=rss-a9429275e78e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb08af408e34</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[skills-development]]></category>
            <dc:creator><![CDATA[Jagadeesh]]></dc:creator>
            <pubDate>Sat, 17 Jun 2023 13:09:39 GMT</pubDate>
            <atom:updated>2024-04-11T07:09:53.833Z</atom:updated>
            <content:encoded><![CDATA[<p>Lessons from a Practitioner who worked as a Product Manager, UX Manager/Designer, Business Analyst. I have also worked as a founding team member of an organization which helped startups to secure funding from Government Agencies during the early period of startup culture in India.</p><h3>Mindset before Skillset</h3><p>Developing the right mindset is the most foundational step which should be taken before one develop the skill sets. Not being aware of the mindset as a practitioner could result in you following the methods and applying the skills without much awareness. This could potentially create a very difficult career journey for you.</p><h3>On Empathy</h3><p>In today’s rapidly evolving digital landscape, user experience (UX) design has become a critical aspect of product development. As technology continues to shape our lives the role of UX designers becomes increasingly significant in ensuring user satisfaction and engagement. While there are various skills that contribute to a successful UX designer, one skill stands out as the most vital: <strong>empathy</strong>. In this article, I will write why <strong>empathy</strong> is the cornerstone of UX design and how it influences the design process.</p><h3>Importance of Empathy</h3><h4><strong>1. Helps in understanding User Needs</strong></h4><p>Empathy is the ability to understand and share the feelings and experiences of others. For UX designers, empathy is essential for gaining insight into users’ needs, desires, and pain points. By putting themselves in the shoes of the users, designers can develop a deep understanding of their target audience and create products that truly meet their requirements.</p><p>To build empathy, UX designers conduct user research, engage in usability testing, and analyze user feedback. By actively listening to users and observing their behaviors, designers can identify their motivations, frustrations, and goals. This empathetic approach enables designers to craft user experiences that are tailored to the users’ unique context, resulting in products that resonate with their intended audience.</p><blockquote>Being Empathetic is not another point in the job description. It is a personality trait.</blockquote><blockquote><strong>The most important aspect of “being empathetic” is to be naturally empathetic. Be observant about the feelings, emotions, the possible worries, anticipations, anxieties, and life goals user may carry in their head. It should be your goal to make their Life Simple. The greatest beneficiary of being empathetic is </strong>you yourself. So make it a habit.</blockquote><h4><strong>2. Empathy enhances User Engagement</strong></h4><p>Empathy plays a crucial role in enhancing user engagement. <br>By understanding users’ emotions, designers can create interfaces that evoke positive feelings and establish a strong emotional connection. When users feel understood, valued, and supported, they are more likely to engage with a product and remain loyal to the brand.</p><p>Through empathetic design, UX designers can anticipate and address potential roadblocks, streamline processes, and create intuitive interfaces. By reducing cognitive load and friction, designers can provide users with seamless experiences that encourage interaction and long-term engagement. This empathetic approach not only benefits the end-users but also helps businesses achieve their goals by fostering customer satisfaction and loyalty.</p><figure><img alt="UX Design, Empathy, UX design skills" src="https://cdn-images-1.medium.com/max/1024/1*Ry92YhL6MX2y6a_d9TX1eQ.png" /><figcaption>Think about the potential challenges an employee of a coffee bar might go through while attending a long queue of customers on a Monday morning.</figcaption></figure><h4><strong>3. Promoting Inclusive Design</strong></h4><p>Empathy is also instrumental in promoting inclusive design. A UX designer with a strong sense of empathy acknowledges and accommodates the diverse range of users’ backgrounds, abilities, and preferences. By considering the needs of different user groups, including those with disabilities or language barriers, designers can create products that are accessible to all.</p><p>An empathetic approach to UX design ensures that the product’s features, interactions, and content are inclusive and usable for a wide range of users. This commitment to inclusivity empowers individuals and makes technology more accessible, contributing to a more equitable and inclusive digital environment.</p><h4><strong>4. Collaboration and Multi-disciplinary Communication</strong></h4><p>Empathy is not limited to understanding users alone. It is also crucial for fostering effective collaboration and communication within multidisciplinary teams. UX designers need to empathize with stakeholders, developers, and other team members to bridge the gap between different perspectives and priorities.</p><p>By empathizing with team members, UX designers can build stronger relationships, foster trust, and create an environment that encourages open and constructive dialogue. This empathetic collaboration leads to better decision-making, improved problem-solving, and ultimately, more cohesive and successful design outcomes.</p><h4><strong>Conclusion</strong></h4><p>Empathy is the most important skill a UX designer can possess. By understanding users’ needs, enhancing user engagement, promoting inclusive design, and facilitating effective collaboration, empathy drives the entire design process. UX designers who embrace empathy are better equipped to create products that genuinely resonate with users, deliver delightful experiences, and contribute to the overall success of businesses. In an ever-evolving digital landscape, empathy remains the compass that guides UX designers toward designing products that truly make a difference in users’ lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb08af408e34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Typeface Designer’s Perspective on the recent PM Modi’s certificate.]]></title>
            <link>https://medium.com/@iam.hari/pm-modis-certificate-a-designer-s-perspective-8039c4f933e9?source=rss-a9429275e78e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8039c4f933e9</guid>
            <category><![CDATA[type-design]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jagadeesh]]></dc:creator>
            <pubDate>Sun, 07 May 2023 11:37:28 GMT</pubDate>
            <atom:updated>2024-04-11T06:50:58.243Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A Design issue with AAP’s argument against PM’s degree Certificate.</strong></p><p><strong>Note:</strong> <br>This post is not politically motivated. Let’s look at the matter from the perspective of a typeface designer.</p><p>The argument made here is that the certificate given has a typing mistake, which reads “Gujarat Unibersity” instead of “Gujarat University,” and therefore is not an original one. The letter that helped them make this lame argument is “v,” appearing as “b.” Design practitioners who are familiar with the topic of type design would instantly recognize that this font belongs to the Gothic style, which probably emerged during the mid-century.</p><p>You can use Google Lens (lens.google.com) to recognize the disputed word as printed on the certificate. Google clearly recognized the word correctly as “Gujarat University” and not as “Unibersity.”</p><p>There is another way to double-check this. Open the link below, which will help you recognize the font directly from the certificate.</p><p><a href="https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.myfonts.com%2Fpages%2Fwhatthefont%2Fresult%3Ffbclid%3DIwAR1S7Vn-fgQ4EBhT08ZR3qSsdnnm0NjGq3UIGagd-z_n7GZ8AAD8FzRy7To&amp;h=AT07uEA5GtRDV5rFJoQObTg6C2BxS_W6uvI0gJSvLdIsDReba7ElbyYUjFTo1041xeOXO0eXC6I7EO1IJcEfsntm91SNEQl1VlBVKtV7cAeJ8wGWRid2Oz4u4nqyhcWpg6aR-ME&amp;__tn__=-UK-R&amp;c[0]=AT3bb2eraOOBVvClp7AQY_rzJyD4Alq-b84HewUKMZsILeTwaJej-owrUW24SU034krSsZDd18czlb_am39S_OMhrjNDkfZPl5KUuArpoYXxZx-n6k2lReuCcANsjfvFI6nsaNsXF6N6hIq39grFQO_DZ4Ka6EaU-qGiuj34_5iMMgZayrAWSg">https://www.myfonts.com/pages/whatthefont/result</a> . This list includes several fonts that were designed at different times, all of which are based on the mid-century German type family known as Black Letters.</p><p>Now that the disputed word has been recognized, you can type ‘Gujarat University’ or any other word from the certificate title in the link below and see for yourself.</p><p><a href="https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.myfonts.com%2Fproducts%2Fregular-lincoln-text-pro-171263%3Ffbclid%3DIwAR0tmKkoBu8Jpudw3XDOEieEGQQstwmGtcdcY3NqMyveahyp1GCJ1gMyPzY&amp;h=AT0yQrug1vcLTKS4Tq2q7HndAnFv9He1Js8n4xSgk4VfmW1Gd8EvJd6w-THL3GD6RsVrdmInnFka05Y3L8eKUylgZgY7fmKGmCUDFx_rjybRa2ETcQDNyf4CvGbdVk_rDLWrQx4&amp;__tn__=-UK-R&amp;c[0]=AT3bb2eraOOBVvClp7AQY_rzJyD4Alq-b84HewUKMZsILeTwaJej-owrUW24SU034krSsZDd18czlb_am39S_OMhrjNDkfZPl5KUuArpoYXxZx-n6k2lReuCcANsjfvFI6nsaNsXF6N6hIq39grFQO_DZ4Ka6EaU-qGiuj34_5iMMgZayrAWSg">https://www.myfonts.com/.../regular-lincoln-text-pro-171263</a></p><p>Regarding the argument that the font used in the certificate was not available at the time when the PM received it, it’s important to note that fonts and type families are two different things. The Black Letter type family has been in existence since the 11th or 12th century, and many fonts in varying styles have been based on this type family over the years. Therefore, this argument doesn’t hold any ground at all. A font can be created at any time based on a type family that has been around for centuries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FGnt0GIqYpiNtpYKcvmSDQ.jpeg" /></figure><p>Trivia: Some of the first books (including the Holy book Bible) ever printed by Gutenberg in Germany were using the same type family called Black Letters. The logo of The New York Times is a variant font from this type family as well. It’s important to take typeface seriously because it can have a significant impact on how a text is perceived. Neglecting the importance of typeface could lead to unfavorable consequences.</p><figure><img alt="Typedesign" src="https://cdn-images-1.medium.com/max/32/0*6p0FKMZ3fSWyDSk3.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8039c4f933e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>