Optimize Unity applications on Android using Neon intrinsics
Introduction
Set up
Arm Neon and the Unity Burst compiler
The sample project
The plain (unoptimized) code
The optimizations
Collecting performance data
Analyzing the performance data
Profiling best practice
Summary
Appendix
Next Steps
Optimize Unity applications on Android using Neon intrinsics
Who is this for?
Developers interested in leveraging the Unity Machine Learning Agents toolkit on Arm devices.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Use Arm Neon intrinsics in your Unity C# scripts
- Optimize your code
- Collect and compare performance data using the Unity Profiler and Analyzer tools
Prerequisites
Before starting, you'll need the following prerequisites:
- Basic knowledge of Unity and C#
- Recent Android device, such as a mobile phone or tablet
- Desktop computer capable of running Unity
- Unity version compatible with Unity Burst compiler 1.5 or later
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll optimize Unity collision detection for Android by comparing Plain, Burst, and hand-written Arm Neon implementations. First, you’ll set up Unity and the collision sample, review character-wall and character-character detection, and apply Burst and Neon changes. You’ll build and profile each mode on your Android device, then use Unity Profile Analyzer to compare the captured data and follow profiling practices.