<?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"><channel><title><![CDATA[Boss Lab Devlog]]></title><description><![CDATA[Boss Lab Devlog]]></description><link>https://bosslabdevlog.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 18:09:54 GMT</lastBuildDate><atom:link href="https://bosslabdevlog.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Async Arena PvP without real-time servers: our approach]]></title><description><![CDATA[Boss Lab is a free Android game where you build a boss from 60+ parts, upgrade it, and watch it fight through 100 stages. Alongside that, we have an…]]></description><link>https://bosslabdevlog.hashnode.dev/async-arena-pvp-without-real-time-servers-our-approach</link><guid isPermaLink="true">https://bosslabdevlog.hashnode.dev/async-arena-pvp-without-real-time-servers-our-approach</guid><dc:creator><![CDATA[Boss Lab Studio]]></dc:creator><pubDate>Wed, 04 Nov 2026 18:37:15 GMT</pubDate><content:encoded><![CDATA[<p>Boss Lab is a free Android game where you build a boss from 60+ parts, upgrade it, and watch it fight through 100 stages. Alongside that, we have an asynchronous Arena PvP mode. This post explains, at a high level, why we chose asynchronous PvP over real-time, and how that shaped the design. We're keeping it general on purpose.</p>
<h2>The problem with real-time PvP for a small team</h2>
<p>Real-time multiplayer asks a lot: players need to be online at the same time, you need infrastructure that stays responsive, and matchmaking has to find opponents quickly or players wait around. For a small studio shipping a mobile game, that is a heavy commitment, and an empty lobby feels bad.</p>
<h2>Asynchronous PvP fits a build-and-watch game</h2>
<p>In Boss Lab, the player's skill is in the build. Battles are automatic, so nobody needs to press buttons at a precise moment. That makes asynchronous PvP a natural fit: your boss fights another player's boss even when that player is offline. You don't wait for anyone, and your build can be challenged while you're away.</p>
<h2>What this means for the design</h2>
<ul>
<li><strong>The build is the thing that fights.</strong> Because a build is a list of parts and upgrades, it is a compact thing to share between players.</li>
<li><strong>Fights should be readable.</strong> Since you aren't controlling the fight, you need to understand why you won or lost, so you can adjust your build.</li>
<li><strong>Fairness matters.</strong> We want matchups to feel reasonable, and this is an area we keep tuning based on how players actually play.</li>
<li><strong>No forced ads.</strong> We don't interrupt a battle to push a video.</li>
</ul>
<h2>Trade-offs we accept</h2>
<p>Asynchronous play isn't free of downsides. You don't get the live tension of facing a person in real time, and opponents are snapshots of builds rather than people reacting to you. We think that's a fair trade for a game about building and tinkering, but it is a trade-off, and it won't suit every genre.</p>
<p>We also won't claim we've perfected matchmaking or balance. They are ongoing work, and player feedback is the main thing that guides us.</p>
<h2>A note on how the game is made</h2>
<p>Boss Lab is built with Phaser, and the art and audio are AI-assisted. We'd rather be upfront about that.</p>
<h2>Try it</h2>
<p>Boss Lab is free on Google Play: <a href="https://play.google.com/store/apps/details?id=com.bosslab.game&amp;utm_source=hashnode">Boss Lab on Google Play</a>. More at <a href="https://www.bosslab.xyz/">bosslab.xyz</a>.</p>
<p>If you have built asynchronous multiplayer for your own game, we'd love to hear what you learned.</p>
]]></content:encoded></item><item><title><![CDATA[Building a Boss-Building Battler for Android with Phaser]]></title><description><![CDATA[We're Boss Lab Studio, a small team, and we just released our first Android game: a boss-building battler. You assemble a boss from more than 60 modular…]]></description><link>https://bosslabdevlog.hashnode.dev/building-a-boss-building-battler-for-android-with-phaser</link><guid isPermaLink="true">https://bosslabdevlog.hashnode.dev/building-a-boss-building-battler-for-android-with-phaser</guid><category><![CDATA[Android]]></category><category><![CDATA[GameDev]]></category><category><![CDATA[phaser]]></category><category><![CDATA[JavaScript]]></category><dc:creator><![CDATA[Boss Lab Studio]]></dc:creator><pubDate>Wed, 04 Nov 2026 12:58:25 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6aeb2b1376e939142a6ad7b2/ffac34fa-3f78-43c1-8bbd-5e3fc6a639c1.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>We're Boss Lab Studio, a small team, and we just released our first Android game: a boss-building battler. You assemble a boss from more than 60 modular parts, upgrade it, and then watch it auto-battle its way through 100 stages. There's also an asynchronous Arena PvP mode, where your build fights other players' builds even when they're offline. This post is a plain look at how we made it and what we'd do again.</p>
<h2>Why Phaser</h2>
<p>We wanted to move fast and iterate on a game whose core is mostly data and rules rather than twitch physics. Phaser let us do that in a language we already knew, with a quick feedback loop in the browser. Rendering sprites, tweens, particles and UI layers were all well covered, so we spent our time on the game itself instead of on an engine. It isn't perfect, and mobile performance needs constant attention, but for a 2D game like ours it was a sensible, pragmatic choice.</p>
<h2>Designing modular parts and stats</h2>
<p>The whole game rests on the idea that every part should feel meaningfully different. With 60+ parts, it would be easy to end up with a pile of near-duplicates, so we tried to give each part a clear role, a visible look and a trade-off. A heavy part might add durability but slow the boss down; a flashy one might hit hard but leave you exposed.</p>
<p>We kept stats simple on purpose. If a player can't guess roughly what a part does by looking at it, the system is too complicated. Parts combine in ways we didn't always predict, and watching players find odd builds was one of the best parts of development. Balancing is ongoing, and we still tweak things as we see how people play.</p>
<h2>Making auto-battles readable on a small screen</h2>
<p>Auto-battles are only fun if you can understand why you won or lost. On a phone screen, a lot happens at once, so we leaned on a few principles: strong silhouettes, clear hit feedback, restrained effects, and numbers that appear only when they matter. We cut a lot of visual noise that looked great in a trailer but made the fight impossible to follow.</p>
<p>The goal is that after a battle you can say, "my boss lost because its left side was weak," and then go fix it in the builder. That loop, build, watch, learn, rebuild, is the heart of the game.</p>
<h2>Packaging a web game for Android</h2>
<p>Shipping a web game as an Android app has its own set of chores. We wrapped the game so it could run as a native app and be distributed through Google Play. Most of our effort went into the unglamorous things: handling different screen sizes and aspect ratios, making touch controls comfortable, managing memory on lower-end devices, saving progress reliably, and testing on real hardware rather than trusting the desktop browser. Plan time for this. It always takes longer than you expect.</p>
<h2>Keeping monetization fair</h2>
<p>We wanted a game we'd be comfortable playing ourselves. That means in-app purchases are optional, and there are no forced ads. We don't want to interrupt a battle or block progress to push a video on anyone. Whether we've struck the right balance is something we'll keep watching, and player feedback matters a lot here.</p>
<h2>A note on AI-assisted art and audio</h2>
<p>In the interest of being upfront: the art and audio in the game are AI-assisted. We use these tools as part of our workflow, and we'd rather say so openly than have anyone wonder. Design, systems, code and balancing are done by us.</p>
<h2>What's next</h2>
<p>We're still improving the game, tuning parts, and listening to players, especially on Arena PvP, where real builds from real people keep surprising us. If you're working on a Phaser game, or thinking about taking a web game to Android, we're happy to compare notes in the comments.</p>
<p>It's free on Google Play, and we'd love your feedback: <a href="https://play.google.com/store/apps/details?id=com.bosslab.game&amp;utm_source=hashnode">https://play.google.com/store/apps/details?id=com.bosslab.game&amp;utm_source=hashnode</a></p>
]]></content:encoded></item></channel></rss>