Supported devices and platforms
This article details the devices, operating systems, hardware requirements supported by the 3D object tracking feature, and its compatibility when used with motion tracking and custom cameras. It helps developers evaluate project feasibility and prepare the software and hardware environment in advance.
Supported devices and platforms
As a cross-platform AR SDK, EasyAR Sense provides broad operating system and hardware support for the 3D object tracking feature.
Operating systems and version requirements
| Device type | Operating system version | Notes |
|---|---|---|
| PC | • Windows 7 and above • macOS Catalina 10.15 and above |
Windows N/KN editions require Media Feature Pack for camera use |
| Mobile/Tablet | • Android 5.0 and above • iOS 12.0 and above |
Includes HarmonyOS 1.x-4.x |
| XR headset | • Android • visionOS 2.0 and above |
Detailed supported devices and system requirements: Headset support |
CPU architecture support
| Operating system | Supported CPU architectures |
|---|---|
| Windows | x86, x86_64 |
| macOS | x86_64, arm64 (Apple Silicon) |
| Android | armv7a, arm64-v8a |
| iOS | arm64 |
Hardware requirements
The 3D object tracking feature requires a camera with no additional sensors needed. Compared to other AR features (e.g., surface tracking), it has lower hardware dependencies and is suitable for almost all devices.
Compatibility notes
- Future Android/iOS versions
EasyAR Sense typically doesn't rely heavily on system APIs, so newly released Android/iOS versions are generally supported immediately. - 64-bit architecture requirement
Since 2019, Google Play Store requires new apps to support 64-bit; major app stores in China have also enforced this. EasyAR provides binaries for botharmv7aandarm64-v8a.
Device support for motion fusion
Motion Fusion combines 3D object tracking with device motion tracking to enhance tracking stability or enable more complex AR interactions. While 3D object tracking itself doesn't require motion sensors, enabling Motion Fusion requires:
Motion fusion hardware requirements
- Required sensors: Accelerometer and gyroscope
- Applicable scenarios: Maintain virtual object pose persistence using motion data when the target object moves out of the camera's field of view, ensuring stable and continuous tracking
Platform support
- iOS: Devices supporting ARKit.
- Android: Devices supporting ARCore/AR Engine/EasyAR Motion Tracker.
- Windows/macOS: Typically lack built-in sensors; require external devices or forgo Motion Fusion.
Notes
- 3D object tracking and Motion Fusion can be used independently. Object tracking alone requires no additional sensors.
- For specific device lists and performance requirements for Motion Fusion, see: Motion tracking supported devices.
Support for custom cameras
In specific scenarios (e.g., custom resolution/frame rate needs, external video stream input), developers may require custom cameras. EasyAR's 3D object tracking supports integration with custom cameras.
Refer to Custom camera for foundational knowledge. Currently, we support custom camera integration on Unity and native platforms.
Implementation methods and notes
We provide dedicated pages for different platforms.
When using custom cameras, always note these key limitations:
- Custom cameras must ensure frame formats (e.g., YUV/RGB) match EasyAR input requirements.
- Increases development complexity and may impact performance; recommended only when standard solutions are insufficient.
- Requires handling camera permissions, lifecycle management, and frame synchronization independently.
Best practice recommendations
The 3D object tracking feature has relatively lenient hardware and platform requirements, needing only a camera to operate, making it suitable for most mobile and desktop systems. Developers should focus on Android 64-bit packaging specifications and verify device support when Motion Fusion is needed. While custom cameras are feasible, they are recommended only when standard solutions cannot meet requirements.