Summary - Build & deploy

Reinforce build & deploy usage with a summary task.

Build and Deploy ecosystem summary

The game deployment workflow begins with scene and platform selection in Build Settings, followed by identity configuration in Player Settings. While PC and Steam rely on 64-bit standalone builds and Steamworks, Android requires AAB packaging and a Keystore digital signature.

// Complete deployment pipeline:
// 1. Scenes and Target (Build Settings)
// 2. Identity and Icon (Player Settings)
// 3. Platform Signing and Store Delivery

For iOS, projects are exported to Xcode on a Mac to finish TestFlight and App Store releases.

Exercise Prepare deployment summary

Generate the output "Yayin: Android (AAB) v2.1.0 - Hazir" using targetOS, buildType, and ver via Console.WriteLine.

Show example solution

using System;

class DeploymentSummary
{
    static void Main()
    {
        string targetOS = "Android";
        string buildType = "AAB";
        string ver = "2.1.0";
        Console.WriteLine($"Yayin: {targetOS} ({buildType}) v{ver} - Hazir");
    }
}

Test yourself

In a cross-platform project, which target requires Xcode on a Mac instead of outputting a direct device binary?
- Windows (Standalone x86_64)
- Android (Google Play AAB)
- Linux (Standalone)
- iOS (Apple App Store / TestFlight)
Show answer

iOS (Apple App Store / TestFlight) — The iOS target requires the Xcode IDE running on a Mac due to Apple compilation and code signing mandates.

Read version number

// Calisan uygulamanin surum bilgisini alir
string currentVersion = Application.____;

Show answer

// Calisan uygulamanin surum bilgisini alir
string currentVersion = Application.version;

Deployment tools mapping

Build Settings

Scene list and target platform setup
Player Settings

Package, company, and version settings
Keystore

Certificate signing Android builds
Xcode

Compiles iOS and submits to App Store

Next lesson: What is ECS?

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies