<p>Open-source contribution has an onboarding problem.</p>
<p>I wanted to contribute. I really did. I opened GitHub, searched “good first issue,” and got 500 results. Half were stale. A quarter were in repos nobody’s heard of. The rest blurred together into an undifferentiated wall of text. I closed the tab and went back to my day job.</p>
<p>This happened more than once. The intent was always there, but the experience of getting started was actively demotivating.</p>
<h3>The problem isn’t the issue quality - it’s the presentation</h3>
<p>The issues are there. Thousands of them. Good ones, too. But the interface for finding them is a flat list with no sense of priority, no sense of excitement, and no sense of progress. It’s a job board for free work.</p>
<p>I kept thinking: this is a solved problem in other domains. Dating apps don’t show you 500 matches. Game stores don’t show you 500 games. They curate. They surface. They make the first choice feel meaningful.</p>
<p>What if finding an open-source issue felt like that?</p>
<h3>The idea: card-based discovery</h3>
<p>I built GitFable (<a href="https://gitfable.app" target="_blank" rel="noopener nofollow">https://gitfable.app</a>). Instead of browsing issues, you draw them. Each draw reveals a real GitHub issue with a rarity tier - common, rare, epic, or legendary. The rarity is weighted by the repo’s star count, recent activity, and issue quality. 40% common, 30% rare, 20% epic, 10% legendary.</p>
<p>When you draw an issue and it looks interesting, you bookmark it it into a quest log. The quest log holds up to 5 active issues at a time. This isn’t arbitrary - it’s designed to enforce focus. The #1 reason people don’t follow through on “good first issues” is they bookmark 20 and forget about all of them. Five is enough to be engaged, few enough to actually complete.</p>
<p>When your PR gets merged, you earn XP. There’s a streak system. There are badges. The usual gamification loop. But here’s the thing I want to be honest about - the gamification isn’t the point. The point is that the moment of - opening a card, seeing the rarity reveal, feeling a small surge of excitement - is *what gets you to to actually start the contributink. The rest is retention.</p>
<h3>What I learned</h3>
<p><strong>Gamification that enforces behavior &gt; gamification that decorates.</strong> A 5-slot quest limit changes how people engage. A daily draw budget creates scarcity. Rarity tiers create genuine surprise. These aren’t bolted-on badges - they’re structural to how the app works. If you’re going to gamify something, make the game mechanics <em>be</em> the product, not a layer on top of it.</p>
<p><strong>The best onboarding is the one people actually start.</strong> Every design decision in GitFable optimizes for the first 30 seconds. Can you find an issue in 30 seconds? Yes - draw a card. Can you understand what to do next? Yes - it’s bookmarked in your quest log with a clear next step. Can you see progress? Yes - XP, levels, streaks.</p>
<p><strong>Build what scratches your own itch.</strong> I built this because <em>I</em> couldn’t get started with open source. Every feature exists because it solved a specific friction point in my own workflow. That’s a better filter for feature requests than “wouldn’t it be cool if…”</p>
<h3>Try it</h3>
<p>GitFable is live. The issue pool is seeded from real GitHub repos with “good first issue” labels. If you’ve been meaning to contribute to open source but keep closing the tab, give it a try.</p>
<p>Link: <a href="https://gitfable.app/" target="_blank" rel="noopener nofollow">https://gitfable.app/</a></p>


Nishant Gajjar

Finding good first issues on GitHub is overwhelming and demotivating due to poor discoverability. GitFable addresses this by turning issue discovery into a card-draw mechanic with rarity tiers (common to legendary), weighted by repo stars, activity, and issue quality. A 5-slot quest log enforces focus, and XP/streaks provide retention. The core insight is that gamification works best when the mechanics are structural to the product rather than decorative add-ons, and that optimizing the first 30 seconds of onboarding is what actually gets contributors started.