Table of Contents

Device and platform support

This article details the devices, operating systems, hardware requirements supported by the planar image tracking feature, and related support when combined 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 planar image tracking feature.

Operating system and version requirements

Device type Operating system version Remarks
PC • Windows 7 and above
• macOS Catalina 10.15 and above
Windows N/KN editions require Media Feature Pack installation for camera usage
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

Planar image tracking 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 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 Chinese app stores also enforce this. EasyAR provides binaries for both armv7a and arm64-v8a.

Device support for motion fusion

Motion Fusion combines planar image tracking with device motion tracking to enhance tracking stability or enable more complex AR interactions. While planar image 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 continuity using device motion data when the target image moves out of the current camera 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.
Tip

Motion Fusion is natively supported on EasyAR-compatible XR headset devices.

Notes

  • Planar image tracking and Motion Fusion can be used independently. Image recognition alone requires no additional sensors.
  • For specific device models and performance requirements for Motion Fusion, refer to: Motion tracking supported devices.

Custom camera support

In specific scenarios (e.g., custom resolution/frame rate needs, external video stream integration), developers may require custom cameras. EasyAR's planar image tracking supports integration with custom cameras.

You can build understanding through Custom camera. 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:

  • 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.

Best practice recommendations

Planar image tracking has relatively low 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.