App demo
Midsummer SoundLarkspur Live Events, Derby
Show it at the gate
The motion at the turnstile: open it, hold the number to the reader. The ticket has been on the device since it was bought and opens even when nothing gets through on site.
- In the hands of
- Visitor on a two-day ticket
- Shown on
- Android — title on the left, three system buttons below
- Replaces
- Replaces the printed ticket sheet, the paper program that turns to pulp in the first shower, and the question at the gate about whether the wristband covers both days. The two-day ticket opens even with ten thousand phones on one mast — and the 45-minute delay is there with its reason and its time, rather than as a rumor at the hoarding.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
Larkspur Live Events, Derby is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
Larkspur Live Events puts on a two-day festival. The printed ticket sheet gets forgotten or soaked, the program leaflet is out of date after the first thunderstorm, and the notices about bags, ear protection and age limits hang on a temporary fence. On top of that sits the condition that governs everything else: on a site with ten thousand people the mobile network is gone precisely when everyone is queuing at the gate.
Decisions
The ticket is held locally and opens without a signal
It is downloaded at purchase and shown afterwards without asking anything. A ticket that has to be fetched at the gate is absent at exactly the moment it is needed — and there is a queue behind it.
Every change states its reason and its time
A program item moved without comment looks like a bug in the app; the same item with the word “thunderstorm” beside it is information. An outdoor program is a plan and not a promise, and the app says so.
Offline, the app shows the state it has, with a timestamp
It does not pretend to be current. Visibly out of date is better on a festival site than a blank screen — and more honest than a program that stopped being true two hours ago.
Deliberately left outNo purchase and no readable code. The stripe pattern on the ticket is schematic: a code a turnstile would genuinely read would be a claim a demo cannot honor. And buying is a sales transaction with a payment provider, a receipt and an agency behind it — it does not belong as one more button in a visitor app.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 14
- Languages
- 4
Navigation responds, including the route from the program into a single item and back. The ticket, the reminder flow and the site information are fully rendered and inert; the four states have a view of their own.
How it would go on
Ticketing and admission control
Sales, personalization, transfer, and the scanners at the gate. Whether admission is checked online or against a list held on the scanner decides what happens when the network fails.
Editing during the event
Who enters a change, how fast it reaches the devices, and how it reaches people whose phones are receiving nothing. On the day that is a staffing question, not a technical one.
Notifications and life afterwards
Push for program changes is the reason for an app like this and the quickest way to lose it. What happens to the accounts after the weekend, and whether the app returns next year, is part of the undertaking.
An app like this for your business?
Midsummer Sound is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.