Unity Explained: The Engine Behind Half the Games You Play

Unity is a game engine, which means it handles the hard, shared parts of making a game: drawing 3D and 2D graphics, playing sound, detecting collisions, and running physics, so developers can focus on the game itself. It is used for mobile games, indie titles, virtual reality experiences, and even non-game projects like architectural visualisations and training simulations. If you have played a game on a phone in the last decade, there is a good chance Unity was behind it.

A Unity project is built from scenes, and a scene is built from GameObjects. A GameObject is an empty container, and it only does something once you attach components to it. A sprite renderer draws it, a rigidbody gives it physics, a collider lets it bump into things, and a script tells it how to behave. This component approach keeps things flexible: the same GameObject can be a player, an enemy, or a moving platform, just by changing which components it carries.

Scripts in Unity are written in C#. Here is a simple movement script, the kind of first script almost every Unity beginner writes. Attach it to a player character and it will move with the arrow keys or WASD.

using UnityEngine;

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

    void Update()
    {
        float horizontal = Input.GetAxis("Horizontal");
        float vertical = Input.GetAxis("Vertical");

        Vector3 movement = new Vector3(horizontal, 0f, vertical);
        transform.Translate(movement * speed * Time.deltaTime);
    }
}

Read it line by line. The script inherits from MonoBehaviour, which is Unity's base class for anything attached to a GameObject. The speed field is public, so it shows up in the Unity editor and a designer can tune it without touching code. Update runs once per frame. Input.GetAxis reads the player's input as a smooth value between -1 and 1, so holding right gives 1 and holding left gives -1. Those two values become a direction vector, and transform.Translate moves the object along it. Multiplying by Time.deltaTime is the detail beginners most often miss: it makes movement depend on real time, not on frame rate, so the character moves at the same speed on a fast computer and a slow phone.

That editor plus code combination is Unity's real strength. Artists can arrange a level visually, drag in models and sounds, and test the game by pressing Play, while programmers write scripts for behaviour. A small team can prototype an idea in a weekend, which is why Unity dominates game jams and indie development.

The honest trade

Unity trades deep control for speed of development. A custom engine gives a large studio exact control over performance and rendering, while Unity adds overhead and its own way of doing things, which can fight you on unusual projects. Its pricing and terms have also changed over the years, which made some studios nervous about building a business on it. For most small and mid-size teams, though, the trade is worth it: a huge asset store, tutorials for almost every problem, and one codebase that builds to phones, consoles, PCs, and the web.

Make something tiny, then finish it

The best way to learn Unity is not a huge dream project. Build one complete tiny game: a character that moves, something to collect, and a score that goes up. You will touch scenes, components, scripts, and builds in one sitting, and you will end up with a finished game instead of a half built epic.