Platform-specific settings in Unity - Deep Dive

Overview - Platform-specific settings

What is it?

Platform-specific settings in Unity are configurations that let you customize how your game or app behaves on different devices or operating systems. These settings allow you to change graphics quality, input methods, screen resolutions, and other features depending on whether the game runs on Windows, iOS, Android, or consoles. This helps ensure the best experience for users on each platform. Without these settings, your game might not work well or look right on some devices.

Why it matters

Different devices have different capabilities and requirements. Platform-specific settings solve the problem of one-size-fits-all by letting developers tailor the game to each platform’s strengths and limits. Without this, games could run poorly, crash, or have confusing controls on some devices, frustrating players and hurting your reputation.

Where it fits

Before learning platform-specific settings, you should understand Unity basics like scenes, assets, and build processes. After mastering these settings, you can explore platform-specific scripting, optimization techniques, and publishing workflows to app stores or consoles.

Mental Model

Core Idea

Platform-specific settings let you customize your Unity project’s behavior and appearance so it fits perfectly on each device or operating system.

Think of it like...

It’s like packing different clothes for a trip depending on the weather and culture of each country you visit, instead of wearing the same outfit everywhere.

┌───────────────────────────────┐
│        Unity Project           │
├─────────────┬─────────────────┤
│ Common Code │ Platform Settings│
│             │ ┌─────────────┐ │
│             │ │ Windows     │ │
│             │ │ iOS         │ │
│             │ │ Android     │ │
│             │ │ Consoles    │ │
│             │ └─────────────┘ │
└─────────────┴─────────────────┘

Build-Up - 7 Steps

1

Foundation

Understanding Unity Build Targets

Concept: Learn what build targets are and how Unity uses them to create platform-specific versions of your project.

In Unity, a build target is the platform you want your game to run on, like Windows, Android, or iOS. When you choose a build target, Unity prepares your project to work on that platform by compiling code and assets accordingly. You select the build target in the Build Settings window.

Result

You can create different versions of your game optimized for each platform.

Knowing build targets is essential because all platform-specific settings depend on which platform you are building for.

2

Foundation

Locating Platform-specific Settings in Unity

Concept: Discover where to find and change platform-specific settings inside the Unity Editor.

Unity groups platform-specific settings mainly in the Player Settings window. You open it from Edit > Project Settings > Player. Here, tabs for each platform let you adjust settings like resolution, graphics APIs, and permissions. Some settings also appear in Build Settings or Quality Settings.

Result

You know exactly where to go to customize your project for each platform.

Familiarity with the Unity Editor layout speeds up your workflow and prevents confusion when adjusting platform options.

3

Intermediate

Customizing Graphics and Resolution per Platform

🤔Before reading on: Do you think all platforms should use the same graphics quality settings? Commit to yes or no.

Concept: Learn how to set different graphics quality and screen resolutions for each platform to match device capabilities.

In Player Settings, you can specify default screen resolutions and supported orientations for mobile platforms. Quality Settings allow you to create multiple quality levels (like Low, Medium, High) and assign different defaults per platform. For example, you might use lower quality on mobile to save battery and higher quality on PC for better visuals.

Result

Your game looks good and runs smoothly on each device by using appropriate graphics and resolution settings.

Understanding that each platform has unique hardware helps you optimize performance and user experience.

4

Intermediate

Managing Platform-specific Permissions and Features

🤔Before reading on: Do you think all platforms require the same permissions and features? Commit to yes or no.

Concept: Explore how to enable or disable platform-specific features like camera access, GPS, or notifications.

Mobile platforms often require explicit permissions for features like camera or location. In Player Settings under the platform tab, you can declare these permissions. You can also enable platform-specific SDKs or plugins only for certain platforms. For example, enabling Game Center on iOS but not on Android.

Result

Your app requests only necessary permissions and uses features correctly on each platform.

Knowing how to manage permissions prevents app rejections and improves user trust.

5

Intermediate

Using Platform-dependent Compilation in Scripts

🤔Before reading on: Can you write code that runs only on one platform inside the same project? Commit to yes or no.

Concept: Learn how to write code that compiles and runs only on specific platforms using preprocessor directives.

Unity lets you use special tags like #if UNITY_IOS or #if UNITY_ANDROID in your C# scripts. Code inside these blocks runs only when building for that platform. This helps you handle platform-specific APIs or behaviors without separate projects.

Result

Your code adapts automatically to each platform, reducing errors and duplication.

Understanding platform-dependent compilation lets you maintain one codebase for multiple platforms efficiently.

6

Advanced

Optimizing Build Size and Performance per Platform

🤔Before reading on: Do you think all assets should be included in every platform build? Commit to yes or no.

Concept: Discover how to exclude or include assets and plugins selectively to reduce build size and improve performance.

Unity allows you to mark assets or plugins as compatible only with certain platforms. For example, you can exclude high-resolution textures from mobile builds or disable desktop-only plugins on consoles. This reduces build size and load times. You can also adjust scripting backend and API compatibility per platform for better performance.

Result

Your builds are smaller and faster, tailored to each platform’s needs.

Knowing how to manage assets and plugins per platform prevents bloated builds and wasted resources.

7

Expert

Handling Platform-specific Settings in Continuous Integration

🤔Before reading on: Can platform-specific settings be automated in build pipelines? Commit to yes or no.

Concept: Learn how to automate platform-specific builds and settings using scripts and CI/CD tools.

In professional projects, you use build automation tools like Unity Cloud Build or custom scripts to create platform builds automatically. These scripts can modify Player Settings or use command-line arguments to switch platforms and apply settings. This ensures consistent builds and saves time. You can also integrate platform-specific tests to catch issues early.

Result

Your team produces reliable platform builds quickly and consistently without manual steps.

Understanding automation of platform settings is key to scaling development and reducing human error.

Under the Hood

Unity stores platform-specific settings in serialized project files and applies them during the build process. When you select a build target, Unity merges common project data with platform-specific overrides. The build pipeline compiles scripts with platform-dependent directives and packages assets marked for that platform. This layered approach ensures the final build matches the target device’s requirements.

Why designed this way?

Unity’s design balances flexibility and simplicity by centralizing settings but allowing per-platform overrides. This avoids duplicating entire projects for each platform, saving developer time and reducing errors. Alternatives like separate projects per platform were more complex and error-prone, so Unity chose a unified project with conditional settings.

┌───────────────────────────────┐
│       Unity Project Files      │
├─────────────┬─────────────────┤
│ Common Data │ Platform Data   │
│ (Scenes,   │ (Overrides for  │
│ Assets,    │ Windows, iOS,   │
│ Scripts)   │ Android, etc.)  │
└─────┬───────┴───────┬─────────┘
      │               │
      ▼               ▼
┌───────────────────────────────┐
│       Build Pipeline           │
│ - Merges data                │
│ - Compiles scripts           │
│ - Packages assets            │
└─────────────┬─────────────────┘
              │
              ▼
      Platform-specific Build Output

Myth Busters - 4 Common Misconceptions

Quick: Do you think platform-specific settings automatically fix all compatibility issues? Commit to yes or no.

Common Belief: Platform-specific settings alone guarantee the game will run perfectly on all devices.

Reality: Settings help but do not fix all issues; platform-specific bugs or hardware limits still require testing and code adjustments.

Why it matters: Relying only on settings can lead to crashes or poor performance if you skip real testing and debugging on each platform.

Quick: Do you think you must create separate Unity projects for each platform? Commit to yes or no.

Common Belief: You need a different Unity project for every platform to handle their differences.

Reality: Unity supports one project with platform-specific settings and conditional code to handle all platforms.

Why it matters: Creating multiple projects wastes time and causes synchronization problems.

Quick: Do you think all platform-specific settings are found in one place? Commit to yes or no.

Common Belief: All platform-specific settings are located only in Player Settings.

Reality: Settings are spread across Player Settings, Build Settings, Quality Settings, and sometimes scripts or plugins.

Why it matters: Missing where to configure a setting can cause confusion and bugs.

Quick: Do you think platform-dependent compilation slows down your game? Commit to yes or no.

Common Belief: Using #if directives for platform code makes the game slower at runtime.

Reality: Platform-dependent compilation removes unused code at compile time, so it does not affect runtime speed.

Why it matters: Misunderstanding this may cause developers to avoid a powerful tool for managing platform differences.

Expert Zone

1

Some platform-specific settings only apply when using certain scripting backends or API levels, so knowing these dependencies avoids wasted effort.

2

Changing platform settings can trigger asset re-imports or script recompilation, which can slow down iteration if done carelessly.

3

Plugins and native libraries often require manual configuration per platform beyond Unity’s settings, demanding careful version and compatibility management.

When NOT to use

Platform-specific settings are not a substitute for writing portable, cross-platform code. When targeting many platforms with similar capabilities, focus on shared code and use settings sparingly. For very different platforms, consider separate projects or modules. Also, for rapid prototyping, avoid over-customizing settings early to keep development simple.

Production Patterns

In professional projects, teams use platform-specific settings combined with automated build pipelines and testing farms. They maintain shared codebases with conditional compilation and use asset bundles or addressables to deliver platform-optimized content. Continuous integration systems switch build targets and apply settings automatically to produce consistent releases.

Connections

Conditional Compilation

Platform-specific settings build on conditional compilation to customize code per platform.

Understanding conditional compilation helps you write flexible code that adapts to platform differences without multiple projects.

Continuous Integration / Continuous Deployment (CI/CD)

Platform-specific settings are integrated into CI/CD pipelines to automate multi-platform builds.

Knowing how settings fit into CI/CD helps scale development and maintain quality across platforms.

Product Localization

Both platform-specific settings and localization customize the product experience based on user context.

Recognizing this connection helps developers think broadly about tailoring apps for diverse users and devices.

Common Pitfalls

#1 Forgetting to switch the build target before adjusting platform settings.

Wrong approach:

Changing iOS settings while the build target is set to Android, expecting iOS build to reflect changes.

Correct approach:

Switch the build target to iOS in Build Settings before modifying iOS-specific Player Settings.

Root cause:

Misunderstanding that platform settings apply only to the currently selected build target.

#2 Using platform-dependent compilation incorrectly by nesting incompatible directives.

Wrong approach:

#if UNITY_IOS
// iOS code
#if UNITY_ANDROID
// Android code
#endif
#endif

Correct approach:

#if UNITY_IOS
// iOS code
#endif
#if UNITY_ANDROID
// Android code
#endif

Root cause:

Confusing nested directives causes code to be excluded unexpectedly.

#3 Including all high-resolution textures and plugins in every platform build.

Wrong approach:

Marking all assets as compatible with all platforms, leading to large build sizes.

Correct approach:

Set asset import settings and plugin compatibility to include only needed platforms.

Root cause:

Not understanding how to exclude unnecessary assets per platform.

Key Takeaways

Platform-specific settings in Unity let you tailor your game’s behavior and appearance for each device or operating system.

These settings are found mainly in Player Settings, Build Settings, and Quality Settings, and can be combined with platform-dependent code.

Using platform-specific settings improves performance, user experience, and compliance with platform requirements.

Automation of platform-specific builds and settings is essential for professional, scalable development.

Misunderstanding or neglecting platform-specific settings can cause bugs, poor performance, and wasted resources.