<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Art-Direction on Birdor Blog</title>
		<link>https://blog.birdor.com/tags/art-direction/</link>
		<description>Recent content in Art-Direction on Birdor Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 15 Jan 2026 10:55:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.birdor.com/tags/art-direction/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Cuphead Product Case Study: How Studio MDHR Turned Hand-Drawn Production Risk Into A Global Brand</title>
				<link>https://blog.birdor.com/cuphead-handcrafted-risk-product-case-study/</link>
				<pubDate>Thu, 15 Jan 2026 10:55:00 +0800</pubDate>
				<guid>https://blog.birdor.com/cuphead-handcrafted-risk-product-case-study/</guid>
				<description>&lt;p&gt;Cuphead is a product case, not just a success story.&lt;/p&gt;&#xA;&lt;p&gt;The easiest mistake is to reduce it to genre. hand-animated boss-rush run-and-gun game is only the container. The product question is why this specific game created trust, memory, and continued demand. Studio MDHR did not merely ship a collection of systems. The developer shaped a repeatable promise that players could understand, test, share, and return to.&lt;/p&gt;&#xA;&lt;p&gt;This article studies Cuphead as a product: first-minute proof, core loop, positioning, production risk, community behavior, monetization, update strategy, and practical operator lessons. The point is not to imitate the theme. The point is to understand how the product holds together.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
