Public web flow in detail
Event audiences are messier than app-store logic assumes. Some attendees will not install anything for a two-hour session; some, like members of the public at a festival, were never going to. Public web flows exist for them. A QR code on a slide opens a browser page where the visitor votes or answers a poll; a ticket link opens checkout; a public leaderboard can be shown to a wider crowd; a revocable post link lets a single photo or reel be viewed outside the app. These pages run on the same engine as the app, so their data is not a separate silo. A public vote and an in-app vote add to the same tally, and results can appear on a venue screen in real time. Because there is no sign-in, duplicate protection and consent wording need deliberate design, and organisers can revoke links when a post should no longer be public.
How Sociana uses it
Public web flows are one surface of the platform and include ticket checkout, no-login polls, no-login voting, public leaderboards and public post links, all reading from the same engine.
Example
A partners meet displayed a QR on the plenary screen so partners without the app could still vote in live polls.
