How would you approach optimizing materials for mobile platforms?

• A. Use URP Lit or simpler shaders, minimize texture sizes and channels, reduce real-time lights, bake lighting where possible, and limit costly shader features.
• B. Always use high-resolution textures and complex shaders.
• C. Enable global illumination in real-time for all assets.
• D. Disable all lighting to maximize FPS.

Answer: (A)

Optimizing materials for mobile centers on keeping shaders simple, textures small, and lighting costs low so the GPU can render smoothly within memory and performance limits. Using URP Lit or simpler shaders ensures the material uses a lightweight, mobile-friendly shading model that still looks good under real-time lighting without overwhelming the device. Keeping texture sizes small and the number of color channels down reduces memory usage and texture fetch time, which directly impacts frame rate and battery life.

Reducing real-time lights matters because each active light adds shading calculations per pixel. Baking lighting wherever possible shifts those calculations to precomputed data, letting the runtime render faster while still delivering convincing illumination. Limiting costly shader features—such as complex parallax mapping, tessellation, or high-frequency post-processing—prevents the shader from generating a heavy instruction load on mobile GPUs.

Other approaches that try to use high-resolution textures and complex shaders, enable real-time global illumination for everything, or disable lighting entirely tend to hurt visual quality or feasibility on mobile. The goal is to balance visual fidelity with performance, and the described approach achieves that by keeping material work lightweight and predictable for mobile hardware.