Unity is a development environment for building interactive two-dimensional and three-dimensional projects. A project holds scenes, scripts, imported art, audio and configuration, while the Unity Editor turns those parts into a running game or application. Unity does not remove the need for programming, asset preparation or testing on the target device; it places those jobs inside one project structure.
Hub chooses the editor
Unity Hub manages projects, editor installations, accounts and licenses. Several editor releases can exist on the same computer, and the Hub records which one should open each project. This matters because a project can upgrade its serialized data when opened in a newer editor.
Opening a production project with the wrong release can trigger package updates or asset reimport work before the mistake becomes obvious. A separate project copy or version-control branch should precede an editor upgrade. Unity also advises against opening the same project in two editor instances because both can write project data.
Modules enable targets
The base editor is only part of an installation. Android, iOS, Web and desktop targets use separate support modules, and some targets also need external SDKs or platform tools. The Hub can add modules later when the editor was originally installed through it.
A project may run inside the editor even when its target module is absent. The failure appears when the user changes the build target or starts a build. Installing every module consumes substantial disk space, so the useful choice is the actual delivery platform rather than every checkbox.
Scenes divide the project
A scene can hold a level, menu or another runnable arrangement of objects. Scenes are assets inside the project and can be loaded separately or together. Multi-scene editing helps keep lighting, interface and world sections apart without forcing the complete project into one hierarchy.
Scene separation also creates ownership problems. Two people editing the same serialized scene can produce a difficult merge, and an unsaved scene can be discarded when another scene opens. Reusable objects belong in prefabs or other shared assets when several scenes need the same controlled content.
Packages change dependencies
The Package Manager installs editor tools, runtime libraries and related asset collections. It can add a package by registry entry, local path or Git address, and it records dependencies in the project. Built-in packages can also be enabled or disabled.
A package update is a code change, not ordinary decoration. It can alter an API, import settings or the behavior of a scene that already worked. Experimental packages carry a warning for the same reason. Keeping the manifest and lock data in version control makes a dependency change visible and lets the team reproduce the same project state.
Assets need originals
Unity imports textures, models, audio and other source files into an internal cache. The generated import data can be rebuilt, but the original source asset and its metadata file belong in the project backup. Copying only the cache does not preserve a reliable project.
Moving an asset outside the editor can separate it from its metadata and make Unity assign a new identity. References in scenes or prefabs may then break even though a file with the same name still exists. Renaming and moving through the Project window keeps the paired metadata under Unity’s control.
Builds need real devices
Play Mode runs the project inside the editor for quick iteration. A final build uses the selected platform module, player settings, graphics backend and packaging rules. Its input, permissions and performance can differ from Play Mode.
A successful build is therefore not the final test. Mobile memory limits, controller mappings, display scaling and store requirements appear only on the target environment. Unity can create the package, but signing credentials, platform accounts and device testing remain separate production responsibilities.
