How to Use Unity: A Beginner's Guide to 2D, 3D, C#, and Mobile Games
Key Takeaways
- Unity is free for beginners and supports both 2D and 3D game development with a single project setup.
- You can write C# scripts to control game logic, physics, and player input without needing a full programming background.
- Mobile deployment requires a few extra steps like optimizing graphics and testing on real devices, but Unity handles most of the heavy lifting.
- Start with a simple 2D game to learn the basics before diving into 3D or complex mechanics.
---
What You Need to Get Started
Before we jump in, download Unity Hub from unity.com. It’s the launcher that manages your Unity versions and projects. I recommend using Unity 2022.3 LTS (Long Term Support) because it’s stable and has the most tutorials available. You’ll also need a code editor—Visual Studio Community (free) or VS Code with the C# extension works great.
When installing, check the boxes for:
- Android Build Support (if you plan to deploy to mobile)
- iOS Build Support (requires a Mac for final builds)
- Windows/Mac/Linux Build Support
Don’t worry about the WebGL or other modules unless you need them later.
---
Setting Up Your First Project
Open Unity Hub, click New Project, and choose 2D Core (for 2D) or 3D Core (for 3D). Give it a name like "MyFirstGame" and pick a folder. Unity will create a default scene with a camera and directional light (for 3D) or just a camera (for 2D).
Pro tip: Start with a 2D project even if you eventually want 3D. The concepts are easier to grasp, and you can switch to 3D later. I’ve seen too many beginners get overwhelmed by 3D rotations and cameras on day one.
---
The Unity Interface (in 5 Minutes)
When the project loads, you’ll see:
- Scene view (center): Where you drag and drop objects.
- Game view (next to Scene): What the player sees.
- Hierarchy (left): List of all objects in the scene.
- Inspector (right): Properties of the selected object.
- Project window (bottom): All your files (scripts, art, sounds).
Try this: Right-click in the Hierarchy, select 2D Object > Sprite, and choose a square or circle. Then in the Inspector, change its color or scale. You just placed your first game object.
---
Writing Your First C# Script
Scripts control behavior. In the Project window, right-click and choose Create > C# Script. Name it `PlayerMovement` (no spaces). Double-click to open it in your code editor.
Here’s a simple script to move a 2D player left and right:
```csharp
using UnityEngine;
public class PlayerMovement : MonoBehaviour
{
public float speed = 5f; // Adjustable in the Inspector
void Update()
{
float moveX = Input.GetAxis("Horizontal"); // A/D or arrow keys
transform.Translate(new Vector3(moveX, 0, 0) * speed * Time.deltaTime);
}
}
```
Save the script, go back to Unity, and drag it onto your sprite in the Hierarchy. Press Play. Use A and D keys to move. That’s it—you’ve coded movement.
Why `Time.deltaTime`? It makes movement frame-rate independent. Without it, your player would move faster on a 144 Hz monitor than on a 60 Hz one. Test it yourself: remove `Time.deltaTime` and see the difference.
---
Building a Simple 2D Game (Step by Step)
Let’s make a basic collector game. You’ll need:
- A player sprite (use the square from earlier).
- A coin sprite (create a circle, color it yellow).
- A script to collect coins.
1. Create the coin: In the Hierarchy, right-click 2D Object > Sprites > Circle. Name it "Coin". Scale it down to 0.5 in the Inspector.
2. Add a Collider: With the Coin selected, click Add Component > Box Collider 2D. Check Is Trigger so it doesn’t block the player.
3. Write a collection script: Create a new C# script called `CoinPickup`:
```csharp
using UnityEngine;
public class CoinPickup : MonoBehaviour
{
private void OnTriggerEnter2D(Collider2D other)
{
if (other.CompareTag("Player"))
{
Destroy(gameObject);
Debug.Log("Coin collected!");
}
}
}
```
4. Tag the player: Select your player sprite, and in the Inspector, set the Tag dropdown to "Player" (or create a new tag).
5. Attach the script: Drag `CoinPickup` onto the Coin.
6. Test: Press Play and walk into the coin. It disappears and prints a message in the Console.
You’ve just made a game loop! Add a score counter next—it’s just a variable and a UI text element.
---
Moving to 3D (Without Panic)
Switching to 3D is mostly about perspective. Create a new 3D project and add a Cube (GameObject > 3D Object > Cube). Add a Sphere and a Directional Light. The same C# script works for 3D if you change the movement axis. For example:
```csharp
transform.Translate(new Vector3(moveX, 0, 0) * speed * Time.deltaTime);
```
Still works. For 3D, you might also use `Input.GetAxis("Vertical")` for forward/backward movement.
Key difference: 3D uses Z-axis for depth. 2D uses X and Y only (Z is ignored). If your 3D objects look wrong, check the camera’s position—set it to (0, 1, -10) for a good starting view.
---
Deploying to Mobile (Android & iOS)
Building for mobile is where Unity shines. Here’s the checklist:
For Android:
- In File > Build Settings, switch platform to Android (Unity will install necessary modules).
- Go to Player Settings > Other Settings and set Minimum API Level to 21 (Android 5.0).
- Enable Auto Graphics API and set Texture Compression to ASTC.
- Connect your phone via USB, enable Developer Options and USB Debugging, then click Build and Run.
For iOS (Mac only):
- Switch platform to iOS.
- In Player Settings, set Target minimum iOS Version to 13.0.
- Build, then open the generated Xcode project, connect your iPhone, and click Play in Xcode.
Mobile optimization tips:
- Use Mobile Shaders (in Materials, select Shader > Mobile > Unlit).
- Keep polygon counts under 10,000 for a simple game.
- Test on a mid-range phone (like a 2019 Galaxy A50) to see real performance.
I once shipped a game that ran at 60 FPS on my high-end phone but dropped to 20 FPS on a Pixel 3. The culprit? Too many real-time lights. Use baked lighting for static objects.
---
Comparison: 2D vs 3D for Beginners
| Aspect | 2D | 3D |
| -------- | ---- | ---- |
| Learning curve | Gentle—no rotation headaches | Steeper—need to manage Z-axis, cameras, and lighting |
| Art requirements | Simple sprites, pixel art okay | Needs 3D models (Blender required) or asset store |
| Performance | Runs on almost any device | Requires decent GPU for complex scenes |
| Best first project | Platformer, puzzle, top-down RPG | Simple runner, static diorama |
My take: Start 2D. You’ll learn scripting, physics, and UI faster. Then graduate to 3D once you’re comfortable with the editor.
---
FAQ
Q: Do I need to know programming to use Unity?
A: Not at first. You can build simple games with visual scripting (Unity’s Bolt or Playmaker assets) that work like flowcharts. But to do anything custom, you’ll need basic C#. Start with the script above—it’s only 6 lines.
Q: Why does my game look blurry on mobile?
A: You probably didn’t set the texture type to Sprite (2D and UI) in the Inspector, or your camera’s orthographic size is too small. For 2D mobile games, set the camera size to match your screen height (e.g., 5 for a 1080p screen with a 400-pixel sprite).
Q: How do I make a game without buying assets?
A: Unity’s standard assets (free from the Asset Store) include basic characters, environments, and sounds. Or use placeholder shapes (cubes, spheres, sprites) and replace them later. I built my first game entirely with colored squares—it was ugly but functional.
---
Final Advice
Unity is deep but forgiving. The best way to learn is to build something small today. Don’t plan a massive RPG for your first project—make a 5-minute platformer or a coin collector. You’ll hit bugs, scripts will error, and objects will fly off screen. That’s normal. Fix one thing at a time, use Google (add “Unity” to every search), and keep the Console window open.
Happy building.