Research & field notes
Playonder event editions and browser-product pilots
A clear record of earlier event attendances, browser tests and the Singapore trail in preparation, without mixing them into an unsupported outcome claim.
Vladimir Fedorov · Published 26 October 2026
Three stages of the product, not one success metric
Playonder’s public product record distinguishes earlier event editions, later browser-product tests and a trail still in preparation. The purpose of this page is to make those stages clear. It is not an announcement of a newly completed event or a claim of a measured learning, retention or revenue effect.
| Stage | Published evidence | How to interpret it |
|---|---|---|
| Earlier event editions | Two events, around 1,800 attendances in total; the larger event around 1,500. | Historical attendance figures for earlier versions, not unique users, paid customers or current capacity. |
| Browser-product tests | Seoul, Dubai and Berkeley are named on the public product site. | Product tests and pilots, not automatically commercial customer rollouts. |
| Singapore heritage trail | Cultural Quest: Choa Chu Kang, with HDFX, described as in preparation. | Not presented as a completed deployment or a new attendance result. |
What the browser edition demonstrates
The published Dubai test screenshots show a route with camera, pose, view-matching, compass and voice missions. The organiser tools include a route editor, recognition training from photos, team progress and results. Computer vision runs on the device; speech features are a separate part of the system.
A test of a mission type establishes what was exercised in that context. It does not establish that every device, route or event size will work without preparation.
Inspect the public examples
The event video and browser links are examples associated with the published product history. They may represent different editions; they are not a promise that every feature or route is available unchanged.
What a new case should establish
For a new organiser pilot, agree the route, edition, audience, date, success criteria and what can be published. Record what ran and what did not. Outcomes such as attendance, completed missions and organiser feedback should be reported only when those observations are available, not inferred from screenshots.
Plan your pilot
Tell us about your audience, location, intended date and route. We will scope the next step with you.