By late 2026, the most useful mobile lessons are less about headline market size and more about execution. The store is crowded, and acquisition costs can make retention especially important, and players notice poor performance, fragile saves, bad onboarding, and aggressive monetisation immediately.
Mobile is one of our core areas. David's previous work on RuneScape Mobile at Jagex, alongside our current mobile and cross-platform projects, means we spend a lot of time dealing with the unglamorous parts that determine whether a mobile build is actually shippable: performance, platform SDKs, input, content delivery, saves, analytics, and device variation.
This is our late-2026 review of lessons from our development work and the considerations we would take into a mobile project in 2027. It is not a statistical report of the whole mobile market; broader trends and our predictions should be read separately from our project experience.
Market Reality: Retention Before Scale
For a small or mid-sized studio, the practical change is that distribution cannot be treated as somebody else's problem. Even a technically strong game can struggle if onboarding is weak, store positioning is unclear, or players churn before they reach the part of the game that makes it special.
What this means for development:
- Instrument the first session. Know where players stop, which permissions or account steps cause friction, and how long it takes to reach the core loop.
- Treat performance as retention work. Crashes, thermal throttling, long loads, and hitching are not just engineering defects; they are reasons to leave.
- Build content and configuration for iteration. Live tuning is much cheaper when values, events, and content do not require a new client build for every change.
- Segment before generalising. Device tier, acquisition source, country, version, and player type can behave very differently. A single blended retention number can hide the real problem.
Key Takeaway: Acquisition gets a player to install. The product still has to earn the second session.
The Unity Ecosystem in 2026
Unity 6 Is the New Standard
Unity 6, released in late 2024, has now had over a year of production use. For mobile development, the most significant changes are:
- GPU Resident Drawer: A rendering optimisation that reduces CPU overhead for draw calls. In internal testing we observed frame-time improvements in some object-heavy Android scenes. We have not published controlled benchmark figures, and results depend on scene and device.
- Improved URP (Universal Render Pipeline): Better mobile shader support, more efficient post-processing, and simplified setup for mobile-first projects.
- Connected-game tooling: Unity's ecosystem for services, transport, authentication, and backend integrations continues to improve. We choose networking and backend technology per project rather than treating one package as the default.
- Addressables improvements: Better memory management for asset loading on mobile, reducing the risk of out-of-memory crashes on constrained devices.
The Unity Pricing Dust Has Settled
The Runtime Fee that Unity announced in 2023, and that caused so much concern, was cancelled in September 2024. For project budgeting, we now treat engine licensing as a conventional tooling cost and verify the current Unity plan thresholds at the point of scoping rather than baking a price into a long-lived article. The bigger decision for us remains technical fit: team experience, target platforms, existing code, rendering needs, and the surrounding SDK ecosystem.
Alternatives Worth Watching
While Unity remains our engine of choice for mobile game development, the competitive landscape has evolved:
- Godot continues to gain traction for 2D mobile games. Its open-source model and lightweight runtime make it attractive for smaller projects, though its 3D capabilities and mobile optimisation tooling still lag behind Unity.
- Unreal Engine 5 has improved its mobile support, but the engine's overhead makes it impractical for most mobile titles. We would only recommend it for mobile projects with high-end visual ambitions and generous hardware minimum specs.
- Custom engines remain relevant for studios with very specific performance requirements (e.g., hypercasual games where a 5MB APK size matters).
Key Takeaway: Unity 6 is a strong baseline for new Unity mobile work, but an existing project should migrate because the benefits justify the risk - not simply because a newer version exists. Profile first, especially if the project depends on older plugins or custom rendering.
Monetisation: What Is Working in 2026
Hybrid Monetisation Is Common - But Not Automatic
Many mobile games combine more than one revenue stream, but that does not mean every project should copy the same stack. A monetisation model has to fit the audience, session length, content cadence, and the type of value the game can keep delivering:
- Rewarded video ads as the base revenue layer (available to all players)
- Battle passes / season passes where the game has enough ongoing content to support them
- Cosmetic IAPs for engaged players who want to express identity
- Subscription models for the most dedicated players (ad removal + premium currency + exclusive content)
Different business models call for different combinations, and the outcome should be tested rather than assumed. When we partnered with Mojo Games on Pocket Factory, we took responsibility for integrating both ad mediation and in-app purchases, building a monetisation system that served casual browsers (who generated ad revenue) and engaged players (who purchased premium content).
Where Subscriptions Might Fit
Subscriptions are one option in some mobile business models, but require continuing value and careful testing. Apple and Google both provide native subscription support with trial periods and grace periods. Each store only knows about its own subscriptions, so letting a player who subscribed on iOS keep the benefits on Android needs your own account system or a third-party service. The appeal for developers is predictable monthly revenue that is less susceptible to the volatility of one-off IAP purchases.
Depending on the game, subscriptions might include:
- Ad removal (the most universally valued benefit)
- A monthly premium currency stipend
- Early access to new content
- Exclusive cosmetics
The key is offering ongoing value that fits the audience. Whether ad removal alone is attractive enough depends on the game and its players, so conversion and retention should be tested rather than assumed.
Privacy Changes Continue to Reshape UA
Privacy changes such as Apple's App Tracking Transparency framework remain part of mobile acquisition planning:
- Deterministic attribution is largely gone. Studios can no longer track individual users across apps with the precision they once could.
- Platform attribution APIs provide aggregated or privacy-preserving signals rather than the old assumption of unrestricted user-level tracking.
- Contextual advertising and creative-driven UA have become more important. The quality of your ad creative now matters more than the precision of your targeting.
- Organic and community-driven acquisition is more valuable than ever, making content marketing, social media presence, and community building genuine competitive advantages.
These constraints make it important to test creative quality, store positioning and the experience players get after installing. They do not guarantee better results for any particular game.
Emerging Platforms and Technologies
Mobile Hardware Is Plateauing (And That Is Good)
Mobile hardware keeps improving, but the gap between devices your players own is still wide enough to matter. For developers, that means:
- Potential to reach more devices when the game has been optimised and tested across a sensible hardware range
- Opportunities for better performance on newer devices, without assuming the same improvement everywhere
- An ongoing need for device-specific testing, because memory, GPU capability and operating-system versions still vary
That said, we still recommend building with a tiered quality system as standard practice. The low end of the Android market still includes devices with 3GB RAM and older GPUs that will struggle with unoptimised content.
Foldables and Tablets: Still Niche, Still Important
Foldables are a useful reminder that mobile UI cannot assume one fixed aspect ratio or viewport. Supporting layout changes cleanly - including resizing during fold/unfold where applicable - is a good test of whether the UI architecture is genuinely responsive.
Tablets remain an important platform for educational games. Classroom learning often happens on shared iPads or Android tablets, so an educational app such as Vocab Builder, which David built for The Language Conservancy as a freelance contractor, has to work as well on a tablet as on a phone.
AI-Assisted Development: Practical, Not Revolutionary
AI tools have become a practical part of the mobile game development workflow, but the reality is more measured than the hype suggests:
- AI-assisted coding (GitHub Copilot, Claude) genuinely accelerates boilerplate code and shader writing, but requires experienced developers to review and correct output
- AI art generation is useful for concepting and placeholder assets but rarely produces production-quality game art without significant manual refinement
- AI-powered QA tools that identify visual regressions and suggest test cases are genuinely valuable and save real time
- AI-driven game design (procedural content, dynamic difficulty) is the most mature and impactful application, and something we have been implementing in Unity long before the current AI wave (our Empires Rise project used procedural map generation with modified Perlin Noise years ago)
Key Takeaway: AI tools are best understood as productivity multipliers for experienced developers, not replacements for development expertise. Any time saving should be measured in the actual workflow, with code and output reviewed by experienced developers.
What We Are Seeing in Our Own Projects
Domi Online: MMORPG Architecture at Indie Scale
Our previous work on Domi Online, a PC MMORPG, showed what a small team can take on. Building a full MMORPG with scalable architecture - 64-bit infinite progression, FishNet networking, lean AWS hosting - has given us deep insight into the real-world constraints of ambitious multiplayer projects, insight that carries over directly to mobile multiplayer architecture. One lesson from that work is that early architectural choices can have a lasting effect on server costs. All four closed alpha stress tests, with up to 500 players, ran on a single AWS EC2 server, and network messages were kept lean so that 64-bit progression did not inflate bandwidth costs.
Educational Games: Matching Delivery to the Audience
We have received enquiries about interactive learning from educational organisations, although our own enquiry history is not evidence of an industry-wide growth rate. Vocab Builder for The Language Conservancy showed that even niche educational games benefit from mobile-first design. The right delivery method depends on the learners, devices, connectivity and maintenance needs. A browser-based experience may be preferable to an installed app in some settings.
Porting Remains a Strong Market
Studios continue to approach us for porting work, and the demand profile has shifted. A few years ago, most enquiries were Flash-to-HTML5 rescue missions. Now, we see more requests for:
- PC indie games being brought to mobile for broader reach
- Older Unity games being upgraded to Unity 6 with modern mobile optimisation
- Cross-save, account systems, and broader cross-platform support being added to previously single-platform titles
David's previous experience working on RuneScape Mobile at Jagex remains one of the most relevant credentials in these conversations. The technical lessons from that project - documented in our porting case study - apply directly to modern porting challenges.
Predictions for 2027
These are five possibilities we think are worth watching in 2027, not established outcomes or forecasts backed by market-wide data:
1. Subscription Bundles Will Grow
We expect more studios to experiment with "mega-bundle" subscriptions that provide benefits across multiple games from the same publisher. This is already common on console (Xbox Game Pass, PS Plus) and is starting to appear on mobile.
2. Cross-Platform Support May Matter to More Projects
For some audiences, continuing a game between mobile and PC may be a useful feature. Where that is a genuine requirement, planning accounts, saves and interfaces early is usually easier than retrofitting them. It will not be necessary for every mobile game.
3. Ad Creative Quality Will Differentiate
With targeting precision limited by privacy regulations, the quality and authenticity of ad creatives will become the primary differentiator in paid UA. Studios that invest in genuine gameplay footage and honest creative will outperform those relying on misleading "fake gameplay" ads.
4. Indie Studios Will Consolidate Around Fewer, Better Games
The volume play - launching many low-quality titles and seeing what sticks - is increasingly uneconomic given rising CPI and App Store review standards. We expect indie studios to focus on fewer titles with deeper LiveOps investment, treating each game as a long-term asset rather than a disposable experiment.
5. Educational and Serious Games May Create Opportunities
We see potential for educational and serious games where commissioners have a clear learning need and a workable budget. That is an opportunity we are interested in, not evidence that overall investment will rise. The strongest projects are the ones where the game mechanic genuinely supports the learning objective rather than being added as decoration.
The Bottom Line
The lesson we are taking out of 2026 is that mobile development is less forgiving of weak fundamentals. Performance, onboarding, save reliability, content delivery, and respectful monetisation are not polish items; they shape whether the game gets a chance to retain an audience.
For studios considering a mobile project, the fundamentals remain the same: build a game that runs well on the devices your players actually own, monetise in a way that respects their time, and invest in keeping them engaged after launch.
If you are planning a mobile project and want to discuss the technical approach, our mobile game development services page outlines how we work. For a detailed breakdown of what a mobile game costs to build, our game development cost estimator provides transparent budgeting guidance.
