Epic Games Store on Android: One Publisher's Build Notes

JoyBits was one of the first twenty third-party studios live on Epic Games Store Mobile when it launched on Android in late January, and the studio's own account of that experience, reported this week by GameWorld Observer, is a rare first-hand look at what publishing on an alternative Android store actually costs a team before the platform has matured. The premium titles went live in early February. The founder describes the process as effectively a blindfolded build: no ability to preview a store listing, no way to test a build as downloaded from the platform itself, because those tools simply didn't exist yet during the Early Adopters phase Epic ran the launch through. That's worth sitting with. Anyone weighing a store outside Google Play should assume the same gap exists on any new alternative platform, not only this one.

What JoyBits actually had to work without

The specific missing pieces matter more than the general complaint. A studio submitting to Epic Games Store on Android in this window couldn't see how its store page would render to a real user, and couldn't download and run its own build the way a player would; Google Play and the Apple App Store have offered both basics for years. That forced JoyBits into a submit-and-hope posture: ship the build, wait for it to go live, then discover any rendering or packaging or store-page problem after the fact rather than before. For a studio with JoyBits' history, that risk tolerance is closer to a specialism than an accident: first titles on Amazon's Kindle E-Ink store in 2011; the Amazon Android store in 2012; Windows Phone and Windows 8 storefronts after that. The studio describes alternative channels as a meaningful part of its earnings from the outset rather than an experimental side bet, which is precisely why it stood ready to be an early mover here at all.

Why the studio still thinks it is worth it

Despite the missing tooling, JoyBits' founder frames the platform's business model as one where an average game can earn noticeably more than on the standard mobile stores, where paid-version titles had little chance of finding an audience by 2025. That is the studio's own claim, not an independently verified figure, and readers should treat it that way: a founder's assessment of early results on a new channel, not a benchmark another studio should expect to replicate. It's still a meaningful data point. It suggests Epic's mobile storefront is proving a viable home specifically for paid and premium pricing models that have struggled inside Google Play's overwhelmingly free-to-play ecosystem. JoyBits has kept expanding on the strength of that early read, working with partner studios (Azur Games, ABI Global, Unico Studio among them), with plans for dozens more releases in the following months, and running a free giveaway of Doodle Kingdom through Epic's promotional program that generated notable coverage on its own.

What a studio should actually check before following

The JoyBits account is encouraging but incomplete, and treating it as a template requires filling in gaps the coverage doesn't close. Before committing engineering time to a new Android storefront on the strength of one studio's early notes, confirm the following independently rather than assuming they match:

• Whether the store's attribution and analytics tooling has matured since this account, since a platform's willingness to fix its Early Adopter gaps quickly is a better predictor of long-term viability than its initial launch state.
• Whether the paid-pricing advantage JoyBits describes applies specifically to premium and paid-version titles, which is where the studio's own catalogue sits, rather than to a free-to-play title relying on IAP and ad monetisation.
• What the actual review and submission cadence looks like now versus at launch, since a blind submission process during an Early Adopters phase is a normal, temporary state for any new platform rather than a permanent structural feature.
• How the store handles updates and patches post-launch, since the inability to preview a build pre-submission is a different problem from the inability to iterate quickly once live.

What this means beyond one studio's catalogue

JoyBits is a small studio specialised in paid and premium pricing, built over more than a decade around exactly this risk profile. A larger free-to-play publisher weighing whether to follow onto Epic Games Store on Android shouldn't read this account as a general endorsement so much as evidence that the platform can work for the right kind of catalogue under the right kind of operational tolerance. Live ops, frequent updates, real-time monetisation tuning: a free-to-play title depending on those would feel the tooling gaps described here far more acutely than a premium title shipped largely as a finished product, since the update and patch cadence for a live-service game is exactly where a blind, preview-less submission process creates the most operational risk. That distinction matters more than the headline story of "an alternative Android store is viable now", because viability clearly varies by the kind of game and the kind of studio attempting it.

The wider signal for Android distribution

This account lands against a backdrop where alternative Android app stores are no longer hypothetical, following the Epic v Google injunction requiring Google to open Play to rival storefronts and catalogue access. JoyBits' experience is a useful corrective to any assumption that "alternative store" means a lesser-tooled clone of Google Play. It's closer to a genuinely different distribution environment, with its own economics and its own audience, and, at least in this early window, its own operational rough edges that a studio has to be willing to absorb before the tooling catches up. Studios that treat every new distribution surface as requiring the same build discipline as a mature app store will miss the early-mover advantage; studios that treat any new surface as risk-free will get burned by exactly the kind of blind submission JoyBits describes. The realistic posture sits between those. It starts with checking the store's current tooling state directly rather than assuming this account still describes it months later.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Android Developer Verification and Your Build Pipeline
• Aptoide antitrust lawsuit: a second Android store war