Does Your AR Game Actually Need LiDAR?

Does Your AR Game Actually Need LiDAR?

If you are building AR on iOS, this question shows up early: should the game require a device with a LiDAR sensor?

It is an easy question to answer badly. LiDAR is the most visible piece of AR hardware Apple ships, so it is tempting to treat it as the thing that makes AR work.

It is not. Most of what makes AR feel solid comes from software that already runs on every supported iPhone. LiDAR makes some of that faster and some of it better, but it is an upgrade, not the foundation.

Here is how I think about it after shipping AR Hide and Seek, which does require it.

What you already get without LiDAR

Before adding a hardware requirement, it is worth being precise about what a standard iPhone camera already handles.

• Motion tracking. The app knows where the phone is and how it is moving through the room, in real time.
• Plane detection. Floors, tables and walls get found and tracked, so virtual objects can sit on real surfaces instead of floating.
• Lighting estimation. Virtual objects can be lit to roughly match the room, which is a surprisingly large part of why AR looks convincing.
• Anchors that hold. Place something, walk away, come back, and it is still where you left it.

That is the bulk of a working AR game. If your gameplay is "put a thing on a surface and interact with it," you probably do not need LiDAR at all.

What LiDAR actually adds

LiDAR measures distance directly instead of inferring it from the camera image. Three practical consequences:

• Speed. Surfaces are found almost immediately. Without it, you usually need the player to pan the phone around for a few seconds first, which is a real onboarding cost in a game.
• Real geometry instead of flat planes. A camera-only session tends to understand the world as a set of flat surfaces at various heights. With LiDAR you get something much closer to the actual shape of the room.
• Low light. Camera-based tracking depends on visible detail in the image. Depth measurement does not, so a dim room degrades far more gracefully.

The middle point is the one that matters for gameplay. If your game needs virtual objects to respect real furniture, or needs to know that a doorway is a gap rather than a wall, that is where LiDAR stops being cosmetic.

What requiring it costs you

Every hardware requirement is a filter on who can play.

LiDAR ships on iPhone Pro models, not on the standard iPhone that most people carry. "Requires LiDAR" means a meaningful share of the people who find your App Store page cannot install it.

So the trade is straightforward to state, even if it is uncomfortable to make: how much does the LiDAR version improve the experience, and is that worth the players you lose?

One thing worth checking before you assume the cost is high: how many devices does a session actually need? A game where every player brings their own phone multiplies the requirement across the whole group. A game that runs on one device only has to clear the bar once.

How I decided for AR Hide and Seek

AR Hide and Seek is built around real rooms. The hiders physically hide somewhere in the space. The seeker looks for them through an iPhone, and the phone fills that space with virtual obstacles that make a familiar room harder to read.

The whole design depends on those obstacles feeling like they belong in the room. A crate should sit on the floor and a barrier should line up with an actual wall. With only flat-plane approximations, objects drift, clip through furniture, or hover slightly off the ground, and the moment that happens the illusion is gone and the room is just a room again.

So LiDAR earned its place. It is not decoration on top of the game; it is the reason the core mechanic works.

The cost was also smaller than it first looked, because the game is local multiplayer on a single device. Two to five players share one phone, passed between rounds. Only the seeker's device runs the AR session, so exactly one phone in the group needs LiDAR, not five. That made a requirement I would have hesitated over in a networked game much easier to accept.

What I would push back on is requiring it by default. If I had added LiDAR because it was available rather than because the core loop depended on it, that would have been a bad trade dressed up as a technical one.

A short checklist

When you are deciding, it usually comes down to a few questions:

• Does the gameplay depend on knowing the real shape of the room, or just on finding a flat surface?
• Would the camera-only version be genuinely worse, or only slower to start?
• How many devices does one session need? One, or one per player?
• Can you ship a fallback mode that stands on its own, rather than a degraded apology?
• Are you requiring it for a gameplay reason, or because the demo looked impressive?

If the honest answer is "it is nicer with LiDAR," treat it as an enhancement: use the sensor when it is there, and let everyone else play.

If the answer is "the game does not work without it," require it, say so clearly on your store page, and accept the smaller audience on purpose.

Final thought

LiDAR is a very good sensor solving a fairly narrow problem. It does not make AR work, because software already does that. It makes AR understand rooms properly.

Decide based on whether your game needs to understand rooms, not on whether the hardware exists.

If you are curious about the other side of AR hardware, and what the camera and location data are actually used for, I wrote about that in How AR Games Use Your Camera and Location. The short answer for my own game lives in the FAQ.