itch.io

Really well put — the psychological difference between “claim” and “submit” is real and I hadn’t framed it that way before.

Worth mentioning that the dev upload feature wasn’t something I designed in isolation. It came directly from feedback from indie devs who asked for it. So while the claim model solves one population, there’s another population that actively wants to own and manage their listing from day one. Both are real.

A few honest constraints on the itch.io crawling path: itch.io’s API is developer-only (your own sales, download keys) there’s no public catalog API to browse or ingest games the way IGDB provides for mainstream titles. So coverage would require a scraper, which is technically possible but would likely violate their Terms of Service, and is the kind of thing that gets you banned or ignored if you ever try to reach out for a partnership later. That’s also why direct dev uploads are cleaner for now; I control the relationship, and devs get a dedicated section in Discover. And a crawler would undercut exactly what makes the upload flow valuable: a dev who submits their game gets immediate visibility, their own dedicated page, and a section built specifically for dev-submitted games. That’s something a crawler can never replicate.

On the claim model specifically, you’re right that it removes the self-promotion barrier, but it does hand control of the listing to someone who never asked for it. Platforms like Steam and GOG go the opposite direction and require devs to own their page from day one. There’s a reason for that: devs who care about how their game is presented want to control it, and an auto-generated page can misrepresent them before they even know it exists. The opt-out you mentioned is the minimum but the first impression problem is real.

On the claim model from an engineering perspective, I love the idea and “your game is already listed, do you want to claim it” is a much better pitch than a submission form. The challenge is verification: how does someone prove they own the game? Without that, a bad actor creates an account and starts claiming and editing games they don’t own. Discogs works because music ownership is verifiable through external signals like label credits, artist profiles, release history. A game dev claiming their itch.io page needs a similar anchor, probably proving ownership of the itch.io or Steam URL. That’s solvable but not trivial. IGDB is actually a closer comparison than Discogs here since it’s a community-maintained database where anyone can edit, and it works because games have enough external reference points to catch bad edits. The difference is IGDB has a large active community to self-correct and is not just indie oriented. At this scale, every claim needs manual review, which brings back the bottleneck the claim model was supposed to remove. Worth building toward but the verification layer has to come before the claim flow, not after.

On the psychological barrier, you’re right that claiming feels different from submitting. But I’d push back slightly: some friction isn’t always bad. A dev who puts zero effort into visibility is also likely to put zero effort into responding to players, updating the game, or engaging with their community. The platform works better when devs are at least a little invested. The goal isn’t to remove all effort, it’s to make the effort feel worthwhile. If a dev sees that listing their game here drives real traffic and real players, the motivation follows. That’s the bet. And players notice. Gamers genuinely respond to devs who show up who post updates, respond to feedback, engage with their community. Some of the most beloved indie games probably aren’t the most polished ones, they’re the ones where the dev was visibly present. That engagement is part of the product, and it starts with being findable.

The deeper issue with “never market” devs is motivation, not friction. Even a claim flow requires them to care enough to act. Some won’t, and that’s genuinely hard to solve without something pulling them in: visibility, downloads, a reason to show up. That’s what the dedicated dev-uploaded section is trying to build toward: if a dev sees real traffic coming from a listing, that’s the motivation to engage.

On Bombercup, I don’t have a crawler yet so I can’t pull it in automatically, but I’d genuinely love to have it on the platform. It sounds like exactly the kind of game that deserves more eyes. A few options: I can add it manually as admin, or you can upload it yourself through the dev upload flow. It has its own dedicated section for dev-submitted games. Either way works, happy to do whichever is easier for you.

On your cold-start challenge, it’s a fair test and I want to answer it honestly. Multiple moods are supported simultaneously so chaotic, competitive, and nostalgic working together isn’t a problem. On comparative search: it partially works. Searching “atmospheric horror” or “action arena” works because the system searches across tags, genres, themes and descriptions so descriptive language maps reasonably well. Where it breaks down is truly comparative language: “games like Bomberman but faster” or “something like this but shorter and more relaxing” — the system has no way to parse that kind of relational intent yet. That’s a bigger challenge and an unsolved one. On mood inference: moods are currently generated at ingest time and in the case of dev uploads the dev defines them directly. The longer term direction is player-driven: after playing a game, players log how it made them feel, which over time builds a much richer and more accurate signal than anything inferred from text alone. That’s harder to game, harder to hallucinate, and closer to how people actually talk about games. Not there yet, but that’s where i am thinking on going.

I genuinely appreciate the thoughtfulness here. This kind of feedback is rare and it does shape how I think about what to build next. That said, every feature decision sits at the intersection of what different people want, and those people don’t always agree. The upload flow came from devs who asked for exactly that. The claim model is a valid alternative that solves a different problem. Both represent real perspectives, and neither one alone defines the right direction. I’m one person navigating a lot of competing needs, and the honest answer is that no single conversation settles these questions but conversations like this one move them forward. So thank you.