ARView vs RealityView (iOS, iPadOS)

Question

Created Dec ’24

Replies 2

Boosts 0

Participants 2

I have been digging through the docs and the developer videos, and I have noticed a mention to RealityView having som potential limitations with anchors and world tracking. However, I haven’t been able to locate my answers.

Does anyone know (or point me to) if RealityView supports everything ARView does, and if not what are the difference?

I was fooling around with RealityView today with a simple plane anchor, and the stability of that anchor didn’t seem to be as steady as I recall ARView being In the past on iPhone.

I’m trying to determine if I should be rolling over into RealityView or stay with ARView on this little educational project. I would imagine the answer is to go RealityView, but I want to make sure I’m not setting myself up for failure based on any current limitations For anchors and world data.

Answered by lijiaxu in 819614022

RealityView, a high-level framework specifically designed for visionOS, can also be utilized on iOS. However, RealityView offers a simpler and more aligned approach to visionOS.

While ARView may present some challenges and is not compatible with visionOS, it still holds advantages for iOS app development. Notably, ARView provides access to functions that are exclusive to it, such as face tracking, body tracking, geotracking with anchor placement based on latitude and longitude, object detection, app clip code detection, and video frame post-processing.

In summary, for iOS app development, I recommend utilizing ARView due to its broader content support. However, if you intend to develop visionOS apps, RealityView is the preferred choice.

At the same time, you can also refer to here

Boost

Answer 1

lijiaxu OP

Jan ’25

Accepted Answer

RealityView, a high-level framework specifically designed for visionOS, can also be utilized on iOS. However, RealityView offers a simpler and more aligned approach to visionOS.

While ARView may present some challenges and is not compatible with visionOS, it still holds advantages for iOS app development. Notably, ARView provides access to functions that are exclusive to it, such as face tracking, body tracking, geotracking with anchor placement based on latitude and longitude, object detection, app clip code detection, and video frame post-processing.

In summary, for iOS app development, I recommend utilizing ARView due to its broader content support. However, if you intend to develop visionOS apps, RealityView is the preferred choice.

At the same time, you can also refer to here

1

Answer 2

notpit OP

Jan ’25

@lijiaxu Thank you for your input. Definitely, ARView for now on iOS and iPadOS.

In the project I was working on, I had decided to abandon RealityView. The question was still lingering in my mind, but you have answered it here. I think I was worried about missing out on the latest realism/rendering features, but I don't think there are any missing in ARView at this point.

Perhaps, it was wishful thinking on my part that things like persistent data would become automated in the background with a simple boolean control. That said, with VisionOS that appears to be the direction, and that is exciting. that was the primary functionality I was after.

To correct or update my original note: When using RealityView, after applying the anchor to a specific surface type, such as floor or table, the tracking was much improved and matched what I am familiar with in ARView.

1