know.2nth.ai Tech Game Engines Unity
tech · Game Engines · Unity

The engine that runs on every phone.

Unity is the C#-based, cross-platform engine that dominates mobile games and powers a huge share of AR/VR, indie and mid-tier titles. Its strengths are reach (deploy to more platforms than anything else), the largest asset store in the industry, and a gentle on-ramp via C#. Its weakness in 2026 is trust: the 2023 "Runtime Fee" episode shook the community before being reversed. This is the engine, its mobile-first sweet spot, the honest licensing history, and exactly when to pick it over Unreal or Godot.

Mobile-dominant C# · Unity 6 Largest asset store AR / VR Licensing history

The breadth engine, built on C#.

Unity is a cross-platform real-time engine that has, for over a decade, been the default for mobile games and a leading choice for AR/VR, 2D, and mid-tier 3D titles. Where Unreal optimises for top-end visual fidelity, Unity optimises for reach and approachability: it deploys to more platforms than any rival, its C# scripting is friendlier than C++, and its Asset Store is the largest marketplace of ready-made art, tools and systems in the industry.

The current line is Unity 6, a consolidation release after a turbulent few years. You'll also see Unity beyond games — "Unity Industry" targets automotive, manufacturing and simulation — though games remain the heart of it. A vast catalogue of well-known titles runs on Unity: Pokémon GO, Genshin Impact, Among Us, Hollow Knight, Cuphead, Monument Valley, Hearthstone.

It belongs on this tree as the pragmatic middle of the three engines: not the fidelity ceiling (Unreal) and not the free-and-owned floor (Godot), but the broad, mobile-strong, ecosystem-rich default that a huge share of working studios actually use.

Why "asset store" is a real strategic advantage

Unity's marketplace means a small team can buy a character controller, a dialogue system, a shader pack or a complete art set for a few dollars instead of building from scratch. For lean studios on a deadline, that catalogue is often the deciding factor — it turns months of work into an afternoon's shopping. Neither Unreal nor Godot matches its depth.

GameObjects, components, and C# scripts.

Unity's model is the entity-component pattern. A GameObject is a container that does nothing on its own; you attach components to it — a renderer, a collider, a rigidbody, your own scripts — and the combination is what behaves. Scenes hold GameObjects; prefabs are reusable, pre-configured GameObjects you stamp out repeatedly.

You write behaviour in C#, as components that inherit MonoBehaviour and hook into the engine's lifecycle (Start, Update, and so on). It's a comfortable, well-documented language with the full .NET tooling behind it:

// A Unity component: move the GameObject each frame
using UnityEngine;

public class Mover : MonoBehaviour {
    public float speed = 5f;

    void Update() {
        float x = Input.GetAxis("Horizontal");
        transform.Translate(Vector3.right * x * speed * Time.deltaTime);
    }
}

The AI layer: Muse and Sentis

Unity ships two AI products worth knowing. Unity Muse is an AI assistant for content creation — generating textures, sprites and behaviours inside the editor. Unity Sentis runs neural networks inside your game at runtime, on the player's device — on-device inference for smart NPCs, vision or audio features without a server round-trip. Both are first-party, unlike the agent/MCP tooling, which is community-built (next section's note).

Where Unity is the obvious pick.

Reach and ecosystem are the through-line. Unity wins where you need to ship to many platforms — especially mobile — with a small team and a deadline.

Dominant

Mobile games

The default for iOS and Android games — a large share of the mobile store runs on Unity. Reach + tooling + asset store.

Strong

AR / VR / XR

A leading engine for headsets and AR — mature XR toolkits and broad device support across the immersive landscape.

Broad

Indie & mid-tier

2D and 3D titles across PC and console. The biggest community and the most learning material of any engine.

Beyond games

Industry & sim

Unity Industry for automotive, manufacturing, training and simulation — real-time 3D outside entertainment.

The Runtime Fee — what happened, and where it landed.

You can't honestly cover Unity in 2026 without this. The episode genuinely damaged trust, and understanding it is part of choosing the engine with eyes open.

What happened. In September 2023 Unity announced a "Runtime Fee" — a charge levied per install of a game once it passed revenue and install thresholds. It blindsided developers: a fee tied to installs (not revenue) could, in edge cases, cost more than a game earned, and it was announced as a change to terms many had already shipped under. The backlash was severe — studios publicly threatened to leave, and many migrated to Godot.

Where it landed. Unity walked the policy back under pressure; CEO John Riccitiello departed soon after; and in September 2024, under new leadership (Matt Bromberg), Unity cancelled the Runtime Fee entirely and returned to a conventional seat-based subscription. The tiers today: Personal (free below a revenue cap), Pro, and Enterprise — priced per seat, no per-install charge.

The lesson that outlives the reversal

The fee is gone, and Unity 6 is a stable, capable engine on normal subscription terms again. But the durable takeaway is structural: a vendor can change the terms of a tool you've already built on. That's not a reason to avoid Unity — it's a reason to read the licence, watch renewals, and understand why the owned alternative (Godot, MIT) carries a premium of trust. Confirm the current tiers and revenue caps on Unity's pricing page before you model a budget.

Reach for Unity when. Look elsewhere when.

Reach for Unity when

  • Mobile is your primary platform
  • You need the widest cross-platform reach from one codebase
  • AR / VR / XR is the project
  • The asset store would save you serious build time
  • Your team knows (or wants) C# and .NET
  • You want the biggest community and learning resources

The agent angle — honest version

Unlike Unreal 5.8's first-party embedded MCP server, Unity's agent surface today is community-built: third-party Unity MCP servers on GitHub let an agent drive the editor, but they aren't official or bundled. Unity's own AI investments are Muse (in-editor assistant) and Sentis (on-device runtime inference) rather than an MCP server. If agent-driving the editor via a standard protocol is a hard requirement, Unreal is currently ahead; for Unity, treat MCP as community software and vet it.

The pragmatic engine for SA mobile.

South Africa is a mobile-first market, and most local commercial game-dev and a lot of AR/VR work runs on Unity. Its reach and asset store fit lean SA studios — with the licensing history a real thing to weigh.

Mobile · where the local market is

For SA studios building for local audiences, Android-first development is the reality, and Unity is the strongest tool for shipping a single codebase to Android and iOS. The asset store also stretches a small budget — buying a system beats building it when the team is three people and the deadline is real.

Skills · C# transfers

Unity's C# is the same language as a lot of SA enterprise and Microsoft-stack development, so the talent pool overlaps. A developer from a .NET background can move into Unity faster than into Unreal's C++ — a practical advantage for hiring and cross-training locally.

The honest caution · FX cost & trust

Unity's paid tiers are USD-billed per seat, which is FX exposure for rand budgets — though the free Personal tier covers a lot of small-studio work. And weigh the trust history: the Runtime Fee is cancelled, but if predictability matters more than reach for your project, Godot's zero-cost ownership is the alternative sitting right next door in this sub-hub.

Where Unity links in the tree.

Primary sources.

Unity's official site, documentation and pricing. Licensing has changed more than once — always confirm the current tiers and revenue caps on Unity's own pricing page. Last reviewed 2026-06-18.