Skip to content
Fyndi docs
Polski

AR view#

The AR view — named character's eyes in the app — is the image from the phone camera, on which the 3D models of finds and routes stand anchored in a real place in the city, not on the map.

Requirements: ARCore is needed#

ConditionDetails
A phone with ARCorerequired — Google Play Services for AR is needed; the app checks them when you open the AR view
Consentscamera and precise location
Placeopen space with visible buildings — anchoring uses geospatial coverage

The AR view only works on a phone with ARCore. Without it the app starts normally and you keep playing with the map, routes and finds — the explanatory screen (e.g. “This phone does not support AR”) shows up only after tapping the camera, with Check again, Help and Back to the map buttons. There is no substitute AR view. The full list of requirements (system version, ARCore, camera, location, place) and the steps for that screen are collected on the Device requirements page.

How to start#

  1. Open the AR view with one of two buttons — both lead to the same screen: the camera tile in the top right corner of the map (“Camera — character's eyes (AR view)”) or Open AR on the find card with a 3D model (Finds).
  2. Look around slowly: “Show the surroundings to the camera — look left, right, up and down”.
  3. Wait until “Improving position accuracy…” disappears — the models stand when the position is certain.
  4. The status says how many metres you are from the nearest model and in which direction.
  5. Within 12 m Collect the find appears. Tapping it collects the find and returns to the map.
  6. Exit: the map tile or the system back button — the map comes back in the same place.
Entering the AR view from the camera tile on the map and the first seconds of position calibration — frames from the app will arrive with the next documentation update (describes version 0.357.3).

Quality indicator in the top left corner#

The AR view watches three things at once: position, geospatial coverage (VPS) and the phone's heading. It shows only what has a problem — a state that is fine leaves no icon behind, and when everything works the indicator does not appear at all.

IconWhat it showsWhen it lights up
the “my location” controlposition accuracy from GPSyellow — weak position; red — no location consent or location turned off in the system; grey — no position yet
the globegeospatial coverage (VPS)yellow — no coverage; grey — the check has not come back yet
the compass needlethe heading the phone is facingyellow — heading uncertain; grey — no heading

Tapping these icons does nothing — this is an indicator, not a button. A screen reader reads the full description of each state (“Heading: uncertain”), because colour alone tells it nothing.

Driving to the target: beeping, vibration and glow#

  • Beeping — the closer to the target, the more frequent it is (from a dozen or so seconds at the edge of the range to about two seconds at the target) and the louder. In headphones you hear the side it comes from.
  • Vibration and glow — a twitch accompanies every beep, and on the edge of the frame a glow shines from the side the target is on; when the target is behind you, it settles on the bottom edge.

Guidance concerns finds and route starts — route stops in the middle of a route do not beep. A point pointed at with a finger on the mini-map always guides, even when the automatic would stay silent.

Sound and vibration you turn off with tiles in the AR view. The setting is remembered: you turn them off once and after returning to the map, after entering AR again, and even after an app restart they are still off. The same switch works in the camera view — one setting for both views.

Route guidance: dots on the ground#

When you walk to the route start (Navigate) or run a route, the AR view shows the way as dots on the ground — no arrows and no text in the middle of the screen.

  • At most 5 dots, spaced about 3 m apart along the path you really walk — on a bend they follow the pavement instead of cutting straight to the target.
  • A passed dot disappears and a new one appears at the end — you walk in a “window” of five dots and there are never six.
  • The nearest dot is bigger and gently pulses (1.6 s cycle) — that is the one you are walking to now; the rest show what comes next. Dots lie flat on the ground: a ring with a lighter centre.
  • Dots appear by themselves, right after you enter AR — as soon as the phone catches the ground. You do not have to touch anything in the HUD. If the router has no path for a moment, the app guides you with dots in a straight line to the target and returns to the pavement path as soon as it arrives.
  • Route preview (the route card alone, without Navigate) draws no dots — nobody is walking then.
  • After you arrive, the hint at the bottom says “you are there”, and once a stop is completed guidance moves to the next stop of the route on its own.

Mini-map in the AR view#

At the bottom of the screen you have a full-width mini-map: your character, the guided target and the other points.

  • It starts folded — you see just the Map handle; the unfolding is remembered between entries.
  • Moving it — drag with your finger; the map stays where you leave it, and tapping your figure restores the “behind the player” view, at your real position.
  • Tapping the map turns on guidance to the selected point — a ring pulses around the target, and +/− zooms in and out.
  • The guidance trail has the colour of the target: find — gold, route — turquoise, collected — grey.
  • The map rotates with the direction of your movement: after a few metres of walking it aligns with the direction you are going, and while you stand it stands still, so it does not shake in your hand.

When anchoring will not work#

  • The models only stand with a good position. If you see “Improving position accuracy…” for a long time, walk a few metres away and show the camera other buildings.

Chest test mode#

The debug panel (the text button at the bottom of the screen) now has exactly one button: Place a chest in front of you. Tapping it turns the test mode on and places the chest right away — the whole AR HUD disappears and that same button stays at the bottom.

  • The chest stands about 2.2 m in front of you, upright on the floor (its base touches the floor and you see the front with the keyhole — not just the lid) and it covers nothing: there is no dark card and no full-screen overlay, only a small pill at the top (Test chest · 2.2 m with X) and one Open the chest button at the bottom. For a few seconds you see the hint “Walk around the chest” — it disappears on its own.
  • You can walk all the way around the chest (full 360°) and look at every side before you open it. The keys panel appears only on request: tap Open the chest or the chest itself in the frame — a bottom panel with the keys slides in (never taller than 40% of the screen) and the chest with the key/lid animation stays visible above it. Then Open the chest in the panel → key animation → lid → result card → Done. No walking to a chest and no internet.
  • The chest stays where you placed it: you can step a metre aside or tilt and roll your phone — the model does not lie down and does not follow the phone.
  • The panel header shows the preview distance (2.2 m away), not 0 m — the model really stands 2.2 m in front of the camera, even though you are standing still.
  • Done returns to the “placed” state — the chest stays in your room, open, and you get the full frame and the button back. X removes the chest and brings back Place a chest in front of you; placing again puts a new chest.
  • The numbers are fixed: keys always 10, coins always 100. Your account, your keys and the chests on the map stay untouched — that is why the result card says “Test result — numbers do not come from the server.” and Balance shows 0.
  • The test can be repeated in a loop. Back without a placed chest ends AR and returns to the map.
  • Leaving the mode = leaving the AR view (there is no separate exit button — on purpose, because only one button is supposed to stay on screen).

What to do when AR will not start#

SymptomWhat to do
The card “To enter AR mode I need the camera and location.”tap Grant permissions and allow the camera and location (GPS and location accuracy); Close returns to the map
The camera tile opens nothingthe ARCore check has a time limit — wait a moment and tap again
A message about a failed AR startclose other apps that use the camera and install or update Google Play Services for AR
Models do not stand on the groundleave the room and look around at the buildings; after a fresh entry give the app a few seconds

What we do not show with a screenshot and why#

Frames from the AR view come only from the phone — and for now we do not have them. The emulator on our server does not have Google Play Services for AR, so ARCore does not start on it at all: tapping the camera shows the “This phone does not support AR” screen, so an emulator screenshot cannot show the AR view. That is why in place of a frame there is a “frame in preparation” placeholder; the photos from the phone will come with the next documentation update.

Double rewards for AR actions#

Actions performed in augmented reality pay twice as much as the same actions on the map:

AR actionCoinsEXP
Completing a route stop2 × rate (10 instead of 5)2 × rate (50 instead of 25)
Collecting a find2 × rate (20 instead of 10), daily cap 1002 × rate (80 instead of 40), daily cap 320
Opening a chest2 × the chest's coins—

The daily cap of that action scales with the rate, so AR does not hit the limit faster than regular collecting. Route completion, the first-route-of-the-day bonus, distance and bot gifts are not multiplied. The server pays 2× only when the request carries your position and you are within range (1.5 × radius) — without coordinates the AR action is refused. A repeated request never pays twice.


Documented for app version 0.357.3 (updated 2026-11-12).

Machine translation — the Polish version prevails.

App version: 0.357.3 API version: 0.73.0

docs.fyndi.app · 2026-11-12