Course Preview

Unity Fundamentals

Unity is commercial software for building interactive 3D and 2D applications, most often video games, that run on phones, consoles, desktop computers, and web browsers. Instead of writing a renderer, a physics engine, and platform export tools from scratch, a team builds scenes out of reusable objects and scripts inside one visual editor, and Unity turns that project into a working app for the chosen target devices.

itSoftware engineering | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic - Unity Fundamentals

Unity is a commercial editor for building real-time games and apps, and it has been around since a small team wheeled it onto a stage at Apple's developer conference in 2005. Two decades later it still does roughly the same job: you build a Scene out of GameObjects, and a GameObject is nothing until you staple capabilities onto it.

Those capabilities are components. A GameObject with no components is an empty box with a location in space, which it keeps track of through a Transform, the one component every GameObject gets whether it asked for one or not. Add a renderer and it becomes visible. Add a Rigidbody and gravity starts caring about it. Add a script and it starts doing whatever you told it to do, which is either the best or worst part of game development depending on how that script was written.

Scripts are C# classes called MonoBehaviours, and Unity calls a handful of their methods in a fixed order every single frame: Awake, then Start, then a loop of FixedUpdate, Update, and LateUpdate for as long as the object lives. This looks tidy right up until you notice the one gap in the promise: Unity never guarantees which GameObject's Awake runs first. Most projects never hit this. The ones that do usually built an invisible dependency between two scripts and got away with it for months, which is the engine's way of teaching patience.

Build a thing once, and you will probably want five more just like it with small differences. That is what a Prefab is for: a saved, reusable GameObject template that every placed copy stays connected to, so fixing one enemy's health bar fixes all forty of them instantly.

Rendering comes with a decision attached: pick the Universal Render Pipeline for broad reach, the High Definition pipeline for a hungrier graphics budget, or the old Built-in pipeline, which Unity itself has already marked for retirement. Choosing Built-in for a new project today is a bit like buying a flip phone because the display model looked familiar.

The one surprise worth carrying out of this course happened off-screen, in the licensing fine print. In 2023 Unity tried charging a fee per game install, developers revolted within days, and a year later Unity canceled the entire idea and went back to its ordinary per-seat subscription. If a sentence in your head still says "Unity charges you per install," that sentence has been out of date since Unity canceled the fee, and deserves to be updated.

None of this requires a verdict on whether Unity is the right engine for your project. It requires knowing what you are actually choosing: a component-based engine with paywalled, read-only source access and one of the largest asset marketplaces in the business, running on licensing terms a company can and did change once already. The Cheatsheet has the exact lifecycle order and the render pipeline table. The Reference tab has Unity's own documentation for everything this page only summarized.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Game Developercore

Sources