<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rajat Agarwal &#8211; DesignWhine</title>
	<atom:link href="https://www.designwhine.com/author/rajatagarwal2409/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.designwhine.com</link>
	<description>Tech Through A Design Lens</description>
	<lastBuildDate>Sat, 07 Nov 2026 11:12:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://www.designwhine.com/wp-content/uploads/2024/08/cropped-DW-author-initials-50x50.jpg</url>
	<title>Rajat Agarwal &#8211; DesignWhine</title>
	<link>https://www.designwhine.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How Transsion Won Africa’s Smartphone Market by Designing for Where People Actually Live</title>
		<link>https://www.designwhine.com/transsion-africa-smartphone-design/</link>
					<comments>https://www.designwhine.com/transsion-africa-smartphone-design/#comments</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Wed, 07 Oct 2026 10:30:00 +0000</pubDate>
				<category><![CDATA[Product & UX]]></category>
		<category><![CDATA[Africa]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[user-centered design]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=17979</guid>

					<description><![CDATA[<p>Transsion’s Tecno, Infinix and itel held 47% of African smartphone shipments in Q1 2026. Its advantage was not just price, but designing around networks, power, skin tone, device limits and repair as product requirements.</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/transsion-africa-smartphone-design/">How Transsion Won Africa’s Smartphone Market by Designing for Where People Actually Live</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/transsion-africa-smartphone-design/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>OpenAI GPT-6 Astra Can Use Software Like a Human. What Does That Mean for UX?</title>
		<link>https://www.designwhine.com/openai-gpt-6-astra-computer-use-ux-interface-design/</link>
					<comments>https://www.designwhine.com/openai-gpt-6-astra-computer-use-ux-interface-design/#comments</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Mon, 07 Sep 2026 09:37:48 +0000</pubDate>
				<category><![CDATA[News & Analysis]]></category>
		<category><![CDATA[AI & Tech]]></category>
		<category><![CDATA[Product & UX]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[chatgpt]]></category>
		<category><![CDATA[Emerging Tech]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[Product Design]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=17035</guid>

					<description><![CDATA[<p>OpenAI’s GPT-6 Astra pushes computer and browser use forward, letting AI agents operate software more like people. For product and UX teams, that turns the interface itself into a new machine-access layer.</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/openai-gpt-6-astra-computer-use-ux-interface-design/">OpenAI GPT-6 Astra Can Use Software Like a Human. What Does That Mean for UX?</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/openai-gpt-6-astra-computer-use-ux-interface-design/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Why Do We Only Empathize When It&#8217;s Profitable?</title>
		<link>https://www.designwhine.com/why-do-we-only-empathize-when-its-profitable/</link>
					<comments>https://www.designwhine.com/why-do-we-only-empathize-when-its-profitable/#comments</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Wed, 24 Sep 2025 16:00:13 +0000</pubDate>
				<category><![CDATA[The DesignWhine Philosophy]]></category>
		<category><![CDATA[user-centered design]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=15092</guid>

					<description><![CDATA[<p>I&#8217;ve been designing digital products for fifteen years now, and lately I&#8217;m wondering if we&#8217;ve all been complicit in a massive lie. We talk endlessly about &#8220;user empathy&#8221; and &#8220;don&#8217;t make me think&#8221; philosophies, yet the world is full of confusing interfaces that nobody seems to care about fixing. Why? Let me start with something [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/why-do-we-only-empathize-when-its-profitable/">Why Do We Only Empathize When It&#8217;s Profitable?</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/why-do-we-only-empathize-when-its-profitable/feed/</wfw:commentRss>
			<slash:comments>10</slash:comments>
		
		
			</item>
		<item>
		<title>Human in the Loop: Last Ditch Effort for Us to Stay Relevant?</title>
		<link>https://www.designwhine.com/human-in-the-loop-critical-analysis/</link>
					<comments>https://www.designwhine.com/human-in-the-loop-critical-analysis/#respond</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Sun, 20 Jul 2025 15:25:24 +0000</pubDate>
				<category><![CDATA[The DesignWhine Philosophy]]></category>
		<category><![CDATA[DesignWhine Magazine Issue #17]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=14368</guid>

					<description><![CDATA[<p>There&#8217;s a certain pathos to watching an industry invent increasingly elaborate ways to convince itself it&#8217;s still needed. Enter &#8220;Human in the Loop,&#8221; or HITL as the acronym-obsessed tech world has christened it. This latest buzzword represents what may be Silicon Valley&#8217;s most audacious act of self-preservation: convincing us that artificial intelligence systems require human [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/human-in-the-loop-critical-analysis/">Human in the Loop: Last Ditch Effort for Us to Stay Relevant?</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/human-in-the-loop-critical-analysis/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How Long Does It Take to Build a Design System? A Practical Estimation Model</title>
		<link>https://www.designwhine.com/how-to-estimate-creating-a-design-system-in-hours/</link>
					<comments>https://www.designwhine.com/how-to-estimate-creating-a-design-system-in-hours/#respond</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Sun, 20 Oct 2024 11:40:15 +0000</pubDate>
				<category><![CDATA[Product & UX]]></category>
		<category><![CDATA[Design System]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=13121</guid>

					<description><![CDATA[<p>Design-system estimates become misleading when teams quote months without defining scope. This guide breaks the work into auditable effort ranges for foundations, tokens, components, documentation, code alignment, governance and adoption so teams can build a defensible estimate.</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/how-to-estimate-creating-a-design-system-in-hours/">How Long Does It Take to Build a Design System? A Practical Estimation Model</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/how-to-estimate-creating-a-design-system-in-hours/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ChatGPT Texts You First: Impressive or Concerning?</title>
		<link>https://www.designwhine.com/chatgpt-texts-you-first/</link>
					<comments>https://www.designwhine.com/chatgpt-texts-you-first/#comments</comments>
		
		<dc:creator><![CDATA[Rajat Agarwal]]></dc:creator>
		<pubDate>Thu, 19 Sep 2024 06:09:28 +0000</pubDate>
				<category><![CDATA[The DesignWhine Philosophy]]></category>
		<category><![CDATA[Emerging Tech]]></category>
		<guid isPermaLink="false">https://www.designwhine.com/?p=13034</guid>

					<description><![CDATA[<p>When ChatGPT texts you first, it becomes a bit difficult to decide whether it is impressive, creepy, or a bit too risky. On September 15th, 2024, a Reddit user named SentuBill posted a screenshot that quickly went viral, sparking a wave of curiosity and debate. In the screenshot, OpenAI’s ChatGPT appeared to initiate a conversation [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.designwhine.com/chatgpt-texts-you-first/">ChatGPT Texts You First: Impressive or Concerning?</a> appeared first on <a rel="nofollow" href="https://www.designwhine.com">DesignWhine</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.designwhine.com/chatgpt-texts-you-first/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
	</channel>
</rss>
