Device and platform support
This article describes in detail the devices, operating systems, hardware requirements, and related support when using planar image tracking together with motion tracking and custom cameras, helping developers evaluate project feasibility and prepare software and hardware environments in advance.
Supported devices and platforms
As a cross-platform AR SDK, EasyAR Sense provides broad operating system and hardware support for planar image tracking.
Operating system and version requirements
| Device type | Operating system version | Notes |
|---|---|---|
| PC | • Windows 7 and later • macOS Catalina 10.15 and later |
N/KN editions of Windows need Media Feature Pack installed to use the camera |
| Phone/tablet | • Android 5.0 and later • iOS 12.0 and later |
Includes HarmonyOS 1.x-4.x |
| XR headset | • Android • visionOS 2.0 and later |
For detailed supported devices and system requirements, see 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
Planar image tracking requires a camera and has no extra sensor requirements. Compared with other AR features such as surface tracking, this feature has low hardware dependency and applies to almost all devices.
Compatibility notes
- Future Android/iOS versions
EasyAR Sense usually does not depend on many system APIs, so newly released Android/iOS versions can generally be supported immediately. - 64-bit architecture requirement
Since 2019, Google Play Store has required newly submitted apps to support 64-bit; mainstream app stores in China have also enforced this requirement. EasyAR provides botharmv7aandarm64-v8abinaries.
Device support for motion fusion
Motion Fusion means combining planar image tracking with device motion tracking to improve tracking stability or implement more complex AR interactions. Although planar image tracking itself does not strictly require motion sensors, the following conditions must be met if Motion Fusion is enabled:
Motion Fusion hardware requirements
- Required sensors: accelerometer and gyroscope
- Applicable scenario: When the target image leaves the current camera view, device motion data is used to maintain virtual object pose continuity and keep stable, continuous tracking
Platform support
- iOS: Devices that support ARKit.
- Android: Devices that support ARCore/AR Engine/EasyAR Motion Tracker.
- Windows/macOS: Usually have no built-in sensors, so external devices are required or Motion Fusion must be abandoned.
Tip
For XR headset devices supported by EasyAR, Motion Fusion is naturally supported.
Notes
- Planar image tracking and Motion Fusion can be used independently. If only image recognition is required, no extra sensors are needed.
- For the specific device list and performance requirements of Motion Fusion, see motion tracking supported devices.
Custom camera support
In some special scenarios, such as specific resolution/frame rate requirements or external video stream input, developers may need a custom camera. EasyAR planar image tracking supports use together with custom cameras.
You can refer to custom camera to understand custom cameras. Currently, we support custom camera integration on Unity and native platforms.
Implementation methods and notes
We provide corresponding topic pages for different platforms.
When using a custom camera, always pay attention to the following key limitations:
- The custom camera must ensure that the frame format, such as YUV/RGB, matches EasyAR input requirements.
- It increases development complexity and may affect performance, so it is recommended only when the standard solution cannot meet requirements.
- You need to handle camera permissions, lifecycle management, and frame synchronization yourself.
Best practice suggestions
Planar image tracking has relatively relaxed hardware and platform requirements and can run with only a camera, making it suitable for most mobile devices and desktop systems. Developers need to pay attention to Android 64-bit packaging requirements and check device support when Motion Fusion is needed. Custom cameras are feasible, but are recommended only when the standard solution cannot meet requirements.