<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shivraj Jadeja</title>
    <description>The latest articles on DEV Community by Shivraj Jadeja (@shivraj_jadeja).</description>
    <link>https://dev.to/shivraj_jadeja</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4134726%2Fa983e833-4107-41f9-94e5-088886b93199.png</url>
      <title>DEV Community: Shivraj Jadeja</title>
      <link>https://dev.to/shivraj_jadeja</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shivraj_jadeja"/>
    <language>en</language>
    <item>
      <title>Who Is the Customer? It Might Not Be Who Uses the Product</title>
      <dc:creator>Shivraj Jadeja</dc:creator>
      <pubDate>Mon, 21 Sep 2026 00:57:14 +0000</pubDate>
      <link>https://dev.to/shivraj_jadeja/who-is-the-customer-it-might-not-be-who-uses-the-product-4phi</link>
      <guid>https://dev.to/shivraj_jadeja/who-is-the-customer-it-might-not-be-who-uses-the-product-4phi</guid>
      <description>&lt;p&gt;One idea that stood out to me from The Sneaky Economics of Ticketmaster was that the customer is not always the most obvious person.&lt;/p&gt;

&lt;p&gt;Ticketmaster grew by focusing heavily on venues, not just the people buying tickets. That made me think about my own idea around improving collaboration and merge conflicts in game development.&lt;/p&gt;

&lt;p&gt;The possible customers could include student game developers, team leads, instructors, and small indie studios. For now, I would focus on student game-development teams because they directly experience the problem and are easy for me to speak with and learn from.&lt;/p&gt;

&lt;p&gt;The biggest takeaway for me is that the user, customer, and payer can all be different people and identifying that early on can change how a solution is designed.&lt;/p&gt;

&lt;p&gt;Media: The Sneaky Economics of Ticketmaster&lt;br&gt;
&lt;a href="https://thehustle.co/the-sneaky-economics-of-ticketmaster" rel="noopener noreferrer"&gt;https://thehustle.co/the-sneaky-economics-of-ticketmaster&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>product</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
