Source metadata
- Type: Official Unity e-book
- Maintainer: Unity
- Date on source page: 2024-11-11
- Primary URL: Optimize performance for mobile, XR, and web games
Key takeaways
- Unity recommends URP as the default render pipeline for mobile, XR, and web projects because of its performance-oriented defaults and flexibility.
- Profiling is framed as an early and continuous activity, especially on target devices.
- The guide explicitly recommends ScriptableObjects for some shared/static data to reduce per-object overhead.
- Animation, UI, and rendering features are treated as performance trade-offs that must be chosen in the context of the target platform.
Notable claims
- Performance is the result of several connected design choices, not just late-stage micro-optimisation.
- Render pipeline choice is itself a production decision with downstream consequences.
- Shared data assets can help performance as well as maintainability.
Relevance
This source primarily informs:
It also supports:
- unity-scriptableobjects
- unity-pixel-art-pipeline
- unity-lod-groups
- unity-urp-lighting-and-render-features
Open questions raised
- Which platform-specific constraints are worth surfacing as dedicated pages versus staying inside broader optimisation guidance?
- How much should the vault privilege URP in teaching when Built-In and HDRP still exist?