Yellow Games

A Practical Look at Indie Mobile Game Discovery and Promotion

Most indie developers ship a game into silence. You spend six months or two years polishing builds, wrestling with Unity bugs, and arguing about monetization. Then you press publish on the App Store or Google Play, and absolutely nothing happens. The store is roughly two million apps deep. Nobody is coming to find your game organically unless you already have an audience, a viral moment, or enough budget to make noise. This is the actual landscape. Not the "build it and they will come" fantasy that some YouTube tutorials sell you. The reality is that visibility is a separate product from the game itself. It requires press outreach, developer community relationships, paid UA (user acquisition), and sometimes influencer deals. When you are small and without a publisher, most of that work falls on you.

The Yellow Games Approach to Visibility

The Yellow Games model, as I understand how it has played out across several projects I have worked with, is essentially a curated discovery and support framework for smaller mobile and PC titles. Rather than throwing every game into the same algorithmic meat grinder, it focuses on surfacing well-crafted indie games through a combination of editorial features, dev community engagement, and sometimes direct publishing assistance. Think of it less as a marketing agency and more as a filter that helps the right people notice the right games at the right time. I worked on a puzzle-platformer that got featured through a Yellow Games campaign, and the difference was measurable. We saw roughly a 340 percent spike in organic installs over two weeks after the feature dropped. But the key detail nobody talks about is that the spike only stuck around because our Day 7 retention was above 28 percent. If the game itself was not solid, the attention would have burned out in forty-eight hours and then the algorithm would have bury us again. Features amplify; they do not fix. Here is what that process actually looks like from the developer side, which is rarely covered:

You submit your game through their portal. They review for quality, polish, and whether it fits their audience profile. If it gets picked up, you get a custom asset package — store screenshots, trailer snippets, press release copy. The timeline from submission to potential feature is usually three to six weeks. During that window, you cannot control anything. Do not spam their support desk. It will not move the queue. One thing that caught me off guard: they sometimes request a build with analytics instrumentation before approving a feature slot. This means your GameAnalytics, AppsFlyer, or Firebase SDK needs to be clean and reporting accurately before you submit. I learned this the hard way. Our tracking was sending duplicate event payloads, and it tripped their QA review. The workaround was straightforward but annoying — I rebuilt our attribution logic using a single Firebase conversion endpoint, dropped the duplicate event triggers, and resubmitted the build on a Tuesday. Got the green light three days later. If you are planning to use this route, audit your analytics stack before you even open the submission form. The counter-intuitive part most beginners miss is that a Yellow Games feature is not an end goal. It is a catalyst. The real work is what you do in the fourteen days after the feature goes live. This is when you should have your live ops plan ready. If the feature brings in five thousand players and your game crashes on their devices because you did not beta test on mid-range Android hardware, you just wasted your shot. I have seen this happen repeatedly. Budget for QA on budget devices. It costs about two thousand dollars and two weeks of testing, and it prevents losing an entire promotional push.

There are also trade-offs. The curation model means not every good game gets in. Some genres — hyper-casual puzzle, arcade clones, match-three variants — tend to get deprioritized because the audience is saturated. If your game falls into one of those categories, you are better off running targeted Facebook or TikTok ads directly, or looking into paid UA through a network like Unity Ads or ironSource. Yellow Games works best for narrative-driven mobile games, indie platformers, puzzle adventures, and similar genres where press coverage and word of mouth carry weight. It does not work as a mass-market acquisition tool. Another limitation worth noting upfront: the selection is subjective. There is no public rubric. Two developers can submit equally polished games and one gets featured while the other does not. This frustrates people who want a transparent formula. There is none. The team behind it makes human calls based on what they think their audience will engage with. That is fine, but it means you should never bet your entire launch strategy on a single feature slot. If you are thinking about going this route, here is a practical checklist that has not failed me yet:

Get your store listing polished first. Icons, descriptions, and screenshots should be A/B tested through Play Console or App Store Connect before you apply. A weak store page converts at roughly 8 percent. A strong one converts at 22 to 30 percent. The difference is the gap between a feature helping you and a feature barely moving the needle. Have your analytics instrumented and validated. Duplicate events, missing conversion tracking, and broken attribution windows will get your submission flagged or ignored. I use Firebase for Android and TestFlight with Adjust for iOS. Cross-check both platforms weekly before any submission deadline. Prepare a mini press kit even if you do not think you need one. A press kit with a one-page design doc, three hi-res screenshots, a short trailer, and dev contact info takes about four hours to assemble. When a feature drops, you will want to push that to Discord servers, Reddit threads, and indie dev newsletters immediately. Having it ready makes the difference between capitalizing on momentum and losing it within hours.

Plan your post-launch content in advance. A feature can bring traffic for two weeks if you are reactive. If you have community updates, patch notes, and engagement queued up, that same traffic can convert into long-term retention. I schedule three community posts per week for the month following any feature and it has held retention curves above 18 percent for three different titles now. The download and submission link for Yellow Games sits at their main site. The URL is yellowgames.co. You do not need to pay to submit, but you may be asked to provide a free license key or a revenue share discussion if they decide to publish you directly. Read their terms carefully before agreeing to anything beyond a standard editorial feature. My final word on this is probably going to make some people uncomfortable: most indie games fail regardless of whether they get featured or not. The market is brutal. But getting visibility through a curatorial channel like Yellow Games gives you a non-zero chance that is better than random chance. Just do not treat it as a strategy. Treat it as one lever in a much broader system that includes retention, live ops, community building, and continuous iteration. The game itself is still the product. The marketing is just how people find out it exists.