<?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: Dialo Sall</title>
    <description>The latest articles on DEV Community by Dialo Sall (@dialosall).</description>
    <link>https://dev.to/dialosall</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%2F3999543%2F045a0dbd-89fe-49c2-a1b2-f010f578315c.png</url>
      <title>DEV Community: Dialo Sall</title>
      <link>https://dev.to/dialosall</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dialosall"/>
    <language>en</language>
    <item>
      <title>I Built a Puzzle Game to make Graph Coloring Easier to Understand</title>
      <dc:creator>Dialo Sall</dc:creator>
      <pubDate>Tue, 23 Jun 2026 23:51:25 +0000</pubDate>
      <link>https://dev.to/dialosall/i-built-a-puzzle-game-to-make-graph-coloring-easier-to-understand-ada</link>
      <guid>https://dev.to/dialosall/i-built-a-puzzle-game-to-make-graph-coloring-easier-to-understand-ada</guid>
      <description>&lt;p&gt;I recently built &lt;strong&gt;3Color Simulator&lt;/strong&gt;, a browser-based puzzle game based on the graph 3-coloring problem.&lt;/p&gt;

&lt;p&gt;The idea is simple: players are given a graph and have to color every vertex using only three colors. The challenge is that no two connected vertices can share the same color.&lt;/p&gt;

&lt;p&gt;You can try it here: &lt;a href="https://3color.vercel.app/" rel="noopener noreferrer"&gt;https://3color.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I built it
&lt;/h2&gt;

&lt;p&gt;I’m a Computer Science student, and I’ve always been interested in algorithms, graph theory, and problems like P vs NP.&lt;/p&gt;

&lt;p&gt;Graph coloring is one of those topics that can feel abstract when you first learn it. You might see a diagram in a textbook, but it is not always obvious why the problem is interesting or why it becomes difficult as graphs get more complex.&lt;/p&gt;

&lt;p&gt;So I wanted to turn the concept into something people could actually play.&lt;/p&gt;

&lt;p&gt;Instead of only reading about 3-coloring, players can click through the problem, make mistakes, see conflicts, and gradually understand the rule visually.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the app does
&lt;/h2&gt;

&lt;p&gt;The current version includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Level-based graph coloring puzzles&lt;/li&gt;
&lt;li&gt;Locked progression through levels&lt;/li&gt;
&lt;li&gt;Conflict detection when connected vertices share a color&lt;/li&gt;
&lt;li&gt;Move tracking&lt;/li&gt;
&lt;li&gt;Timer tracking&lt;/li&gt;
&lt;li&gt;A custom graph mode for generating new puzzles&lt;/li&gt;
&lt;li&gt;Mobile-friendly gameplay&lt;/li&gt;
&lt;li&gt;Clearer instructions for non-CS players&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing I learned after sharing the first version is that not everyone immediately knows what “3-coloring a graph” means, even if they understand the rules once they start playing.&lt;/p&gt;

&lt;p&gt;That pushed me to improve the instructions and make the game feel less like a CS assignment and more like a puzzle.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech stack
&lt;/h2&gt;

&lt;p&gt;I built the project with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React&lt;/li&gt;
&lt;li&gt;Vite&lt;/li&gt;
&lt;li&gt;JavaScript&lt;/li&gt;
&lt;li&gt;CSS&lt;/li&gt;
&lt;li&gt;localStorage&lt;/li&gt;
&lt;li&gt;Vercel for deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The core logic is based on graph data structures. Each level stores vertices and edges, and the app checks whether any connected vertices have the same color.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;This project taught me a lot about turning a computer science concept into an interactive experience.&lt;/p&gt;

&lt;p&gt;The technical side was important, but the bigger lesson was UX.&lt;/p&gt;

&lt;p&gt;A feature can work correctly and still confuse users. After people tried the site, I realized I needed to make the goal, rules, and completion state much more obvious.&lt;/p&gt;

&lt;p&gt;I also learned how much small details matter in a game-like project: mobile layout, button placement, level flow, feedback messages, and whether players know they succeeded.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I want to add next
&lt;/h2&gt;

&lt;p&gt;Some future ideas I’m considering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;More levels&lt;/li&gt;
&lt;li&gt;Daily puzzles&lt;/li&gt;
&lt;li&gt;A level editor where players can create their own graphs&lt;/li&gt;
&lt;li&gt;Shareable puzzle results&lt;/li&gt;
&lt;li&gt;Better completion animations&lt;/li&gt;
&lt;li&gt;More advanced graph generation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Eventually, I’d like users to be able to create and submit their own 3-colorable puzzles, but only after they solve them first. That way, every submitted puzzle has a valid solution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Feedback welcome
&lt;/h2&gt;

&lt;p&gt;I’d love feedback on two things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Is the concept clear if you are not already familiar with graph coloring?&lt;/li&gt;
&lt;li&gt;Does the game feel engaging enough to keep playing after the first few levels?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Project link: &lt;a href="https://dev.tourl"&gt;https://3color.vercel.app/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>react</category>
      <category>algorithms</category>
      <category>computerscience</category>
    </item>
  </channel>
</rss>
