On March 1, 2026, a game called Color Blaze Shooter disappeared from both the App Store and Google Play. It had been live for roughly a month. In that time, it pulled in an estimated $20 million, split evenly between in-app purchases and ad revenue.
The game was, by all accounts, a near-identical copy of
Pixel Flow!
, one of the biggest mobile game breakouts in recent memory. Same mechanics, same visual style, same core
loop. Just a different name and a different developer.
That developer was Amobear, a Vietnamese studio that's been around since 2013. The removal wasn't quiet. It sparked a wave of industry discussion about what it actually takes to get a clone pulled, who has the power to make it happen, and whether this changes anything going forward.
What Pixel Flow is, and why everyone wants a piece of it
If you haven't played
Pixel Flow!, the concept is deceptively simple. You've got a grid of colored pixel blocks forming an image. Below
the grid sits a conveyor belt with a row of shooters, each assigned a color. Tap a shooter, it fires at
blocks of its own color, and when it runs out of ammo, it moves to a waiting slot. Clear all the blocks,
complete the picture, advance to the next level.
Simple to explain. Hard to master. The game's real depth comes from sequencing and timing: which shooter to send when, how to manage limited conveyor slots, and a "slinging" mechanic that lets skilled players chain actions to temporarily exceed capacity limits. It's fully deterministic, so when you fail, it's because you made the wrong choices, not because the game screwed you with RNG.
That design philosophy hit hard. Pixel Flow launched in August 2025, built by Istanbul-based Loom Games, a studio of about 20 people founded by Kübra Gündoğan and Emre Çelik. The two had previously run Crescive Games, where they'd shipped over 120 titles across six years. They knew how to move fast.
Within four months of launch, Pixel Flow was generating over $500,000 in daily revenue, roughly $300K+ from IAP and another 30-40% from ads. Close to a million daily active users. Around 200,000 downloads per day. An annual run rate approaching $180 million.
Those aren't "nice indie hit" numbers. That's top-20 US grossing territory.
The billion-dollar acquisition
In February 2026, Scopely, the company behind MONOPOLY GO! and Pokémon GO, announced a definitive agreement to acquire a majority stake in Loom Games. The valuation: over $1 billion, structured as a multi-year performance-based deal.
Let that sink in. A studio founded just one year earlier, with about 20 people, on a single game, hitting unicorn status. Tim O'Brien, Scopely's Chief Revenue Officer, called it "some of the strongest engagement metrics we've seen in mobile over the past year."
For context: Loom Games had only just closed a seed round from Arcadia Gaming Partners and e2vc in January 2026. A month later, they had a billion-dollar acquirer.
This backdrop matters because it completely changes who's playing defense against copycats. Pixel Flow didn't just become a hit game. It became a Scopely-backed hit game. And Scopely has lawyers.
Enter Color Blaze Shooter
Sometime in early 2026, Color Blaze Shooter appeared on both the App Store and Google Play. Developer: Amobear, operating as AVN Globalis. The studio has roots in Vietnam's mobile ecosystem going back over a decade, with a portfolio spanning games and utility apps.
The game didn't just borrow ideas from Pixel Flow. Multiple industry observers described it as a 1-to-1 copy: identical mechanics, matching visual aesthetic, the same core gameplay loop. The kind of clone that doesn't even try to hide its origins.
And it worked. Before removal, Color Blaze Shooter reportedly generated $20 million in total revenue: $10 million from in-app purchases, $10 million from ads. In roughly four weeks. That's not a rounding error. That's a serious business built on someone else's design, operating at scale, with real ad spend behind it.
$20 million in a month from a clone. That number alone explains why game cloning isn't going anywhere, regardless of how many guidelines the app stores update.
What actually got it removed
Here's where it gets interesting, because the industry conversation around this removal got heated fast. App store removals for copycat games are rare. Not because clones are rare (they're everywhere), but because getting a game pulled is genuinely hard to do.
As several commenters on Felix Braberg's LinkedIn post about the removal pointed out, app stores typically encourage private dispute resolution first. Getting a game removed usually requires demonstrating something concrete: code duplication, stolen assets, trademark infringement. Just having similar gameplay often isn't enough, because "similar gameplay" describes half the games on the store.
Victor Zaletov, a mobile industry professional, noted that removal typically requires proof of code or asset theft, not just mechanical similarity. Luca Contato questioned whether this represents genuine enforcement evolution or simply reflects the legal muscle that comes with Scopely's backing.
That's the real question. Would Color Blaze Shooter have been pulled if Pixel Flow were still an independent 20-person studio in Istanbul? Or did Scopely's acquisition, finalized just weeks before the removal, provide the legal infrastructure needed to make it happen?
We don't know for certain. But the timing is hard to ignore.
Apple's new guidelines, and why they might not change much
The Color Blaze Shooter removal also happened against the backdrop of Apple's updated App Store Review Guidelines, published in November 2025. The key addition was rule 4.1(c):
"You cannot use another developer's icon, brand, or product name in your app's icon or name, without approval from the developer."
Apple already had rules about creative originality (4.1a) and app impersonation (4.1b), but 4.1(c) was more specific. It targeted the surface-level copying that makes clones discoverable: the icon design, the naming convention, the visual branding that tricks users into downloading the wrong app.
The timing wasn't random. Apple had just dealt with a flood of fake Sora 2 apps following OpenAI's launch, and the updated guidelines were partly a response to that embarrassment. They also started enforcing trademark-adjacent removals more aggressively. Games using "Flow" in their titles started getting flagged: Yarn Flow, for instance, had to rename itself to Yarn Loop: Knit Puzzle.
But here's the thing about guidelines: they're only as strong as the enforcement behind them. Apple and Google still can't practically review every submission for mechanical similarity. They don't have the tooling or the incentive. Both stores make money from every app that monetizes, including clones. The economic incentive to remove a game generating $20 million in a month simply isn't as clear as you'd think.
What tends to work is legal pressure from the original developer. That's always been true, and the Color Blaze Shooter situation doesn't change the dynamic. It just confirms it with very large dollar signs attached.
The economics of cloning (and why it won't stop)
Let's be honest about what happened here. A clone operated for four weeks and made $20 million. Even accounting for ad spend and development costs, that's enormously profitable. The clone developer walked away with substantial revenue. The removal was an inconvenience, not a catastrophe.
That's the problem.
As long as the expected value of cloning stays positive, studios will keep doing it. The math is simple: build fast, monetize aggressively, extract revenue before enforcement catches up. Some clones last weeks. Others last months. A few last years. The downside is capped at removal; there's no meaningful financial penalty from the platforms.
Pixel Flow, for its part, has already attracted what the industry calls a "clone wave." Deconstructor of Fun's deep dive on the game noted that a Vietnamese studio (likely Amobear under a different listing) had a nearly identical game reaching $140,000 per day with a heavily US-skewed revenue mix. Color Blaze Shooter was the most visible clone, but it wasn't the only one. And it won't be the last.
The Deconstructor of Fun piece put it best: "the category works" and "it's easy to copy." Those two facts, side by side, tell you everything about why this keeps happening.
What this means for smaller studios
The uncomfortable takeaway? If you build something that works in mobile, you should expect copycats. You can't prevent cloning. You can only manage the response.
For studios with corporate backing and legal budgets, the path is clear: file takedowns, leverage trademark law, pressure the platforms. It's slow and annoying, but it works, especially if you've registered trademarks early and documented your IP thoroughly.
For indie studios and small teams, it's much harder. The platforms offer dispute mechanisms, but they're slow, bureaucratic, and biased toward encouraging "private resolution," which really means: sort it out yourselves. Most small studios don't have the resources for a sustained legal fight, particularly against a clone developer in a different jurisdiction.
The practical playbook, if you're building something with real traction:
- Register trademarks early. Don't wait until you're at scale. File as soon as the game shows signs of product-market fit.
- Document everything. Screenshots, design docs, commit history. The more evidence you can show of original creation, the faster a takedown request moves.
- Move fast on disputes. Every week a clone stays live, it's eating your UA budget and confusing your potential players.
- Build what's hard to copy. Cloners replicate mechanics. They struggle with depth: content cadence, live ops, community, meta-game layers. The more your game's value depends on things beyond the core loop, the less damage a clone can do.
What this doesn't change
Color Blaze Shooter getting removed is good news for Loom Games and Scopely. It's a signal that enforcement can work when you've got the resources to push it. But it doesn't fundamentally change the clone economy.
There are hundreds of Pixel Flow-inspired games still on both stores. Most of them are different enough to avoid removal. Some aren't. The ones that cross the line will get pulled eventually, if the original developer pushes hard enough. The ones that stay in the gray area will keep monetizing.
That's just how mobile works. It's always been this way. The numbers are bigger now, the cycles are faster, and the stakes are higher with billion-dollar acquisitions in the mix. But the underlying mechanics of the clone economy haven't changed.
Build something great, and the market will copy it. The question isn't whether it'll happen. It's whether you've built enough depth, speed, and scale to stay ahead of the copies.
Loom Games built something that hit $500K a day. They moved fast enough to land a billion-dollar deal before the copycats could catch up. That's not luck. That's execution.
The copycats made $20 million on borrowed design. Then it was over.
Execution wins. Every time.