YRQR
Book a demo

Mobile-first pilot

Phone camera first. Native pilots in parallel.

YRQR v1 works through QR scans, mobile web capture, and the web dashboard, with native iOS and Android companion builds available to pilots through TestFlight and Google Play Internal Testing.

Pilot scope: public App Store and Google Play release is not promised for v1. Campaigns are sold with mobile web capture as the fallback and native pilot builds where the pilot needs companion-app behaviour.
iPhone camera detecting a YRQR QR code at a mapped location

Cards in use on the app page

The participant experience is built from clear, reusable cards.

These are the cards participants carry with them in the companion app: scan state, rewards, campaign progress, and the closed-loop summary.

S

Camera or app

Scan card

The first card explains the campaign, confirms the QR has been detected, and routes the participant into the right branded flow.

R

Wallet

Reward card

Rewards remain visible after the scan, including status, expiry, terms, and the campaign brand that issued them.

P

Multi-stop journeys

Progress card

Trails, discovery sets, and clue-based campaigns can show completed stops, next actions, and unlock state.

S

Closed loop

Summary card

When the operator publishes back, participants see what was heard and what is being considered next.

Camera is fine for…

  • One-off scans with a short prompt
  • Anonymous participation
  • Pop-up activations and quick consultations
  • Anywhere the participant relationship ends at the scan

The app helps when…

  • Campaigns have multiple stops or progress
  • Participants want a wallet of rewards
  • Closed-loop summaries are part of the operator's promise
  • Participants return to the same campaign or operator over time

Brand customisation

Your brand, from scan to summary.

YRQR resolves a complete brand experience at runtime. Every participant-facing surface uses the operator's brand, not YRQR's. The same is true whether a participant uses their phone camera or the YRQR companion app: one experience, one brand.

Configurable per organisation and per campaign. Logo, colours, copy, language, prompt tone. Co-branding for sponsor + venue activations.

Landing screen

Capture screen

Reward wallet

Closed-loop summary

The QR sticker and its landing screen

The page a participant arrives at after scanning.

The QR unlock screen

The screen that progresses a participant through clues, stages, or stops.

The capture screen

Voice, text, photo, or video response, in the operator's brand.

Rewards and wallet cards

The reward the participant takes away, branded as the operator's, not YRQR's.

Closed-loop summaries

What the participant sees when the operator publishes back.

Privacy posture

Anonymous-first. Camera-controlled.

Rewards and summaries are tied to the participant journey, not sold as advertising inventory. Location checks are campaign-controlled and can be disabled for indoor placements.

Read the full privacy approach

Native Pilot Builds

TestFlight and Google Play Internal Testing builds stay in step with the web product for pilot customers. Public App Store and Google Play releases remain post-pilot scope.

Scoping a campaign first? Explore campaign types.