Lumo

Prixwerkz presents

Cinema,
wherever
you are.

One booking platform. Eight markets. Eight currencies.

Working demo August 2026 Press → or scroll

01

The problem

Cinema is global. Its ticketing isn’t.

Most booking platforms are built around a single country — one currency, one language, one set of habits baked into the product. Opening a second market means forking the codebase and maintaining two of everything.

Lumo inverts that. The market is a property of the venue, not of the software. Adding a city is a data change, not a release.

02

What we built

One platform, running eight markets at once.

Every venue in the demo carries its own city, currency and timezone. The interface, the prices and the tickets follow the venue the customer chose — not a global default.

8Venues across five continents

24Screens configured

8Currencies, natively formatted

6Interface languages

Lumo home screen showing the featured film and the Now Showing rail

03

Footprint

The estate, and what a standard seat costs in it.

Venue	City	Currency	Standard seat
Lumo Leicester Square	London	GBP	£14.00
Lumo SoHo	New York	USD	$16.00
Lumo Shibuya	Tokyo	JPY	¥1,800
Lumo Bastille	Paris	EUR	12,00 €
Lumo Downtown	Dubai	AED	AED 45.00
Lumo Marina Bay	Singapore	SGD	$15.00
Lumo Bandra	Mumbai	INR	₹250
Lumo Paulista	São Paulo	BRL	R$ 35,00

04

Money

A price is quoted once, in the currency it was sold in.

Amounts are held in the venue’s own currency and never converted at display time. Tokyo drops its decimals because yen has none; Paris puts the symbol after the number; Mumbai groups digits the Indian way. That is one formatting function, not eight code paths.

Lumo Shibuya screen list: IMAX ¥1,800, Premium Recliner ¥3,200, Screen 3 ¥2,400 per seat — Lumo Shibuya — screens priced in yen, decimals dropped

Deliberately, there is no FX engine. Converting between markets is a pricing decision for the operator, not a rounding artefact of the interface.

05

The journey

Four steps from browsing to a ticket in hand.

01

Find a film

Live catalogue with posters, ratings, runtimes and trailers.

02

Pick venue and time

Filtered by city, priced in that venue’s currency.

03

Choose seats

Standard, premium and recliner tiers, priced per seat.

04

Collect the ticket

QR code, seats, venue address and showtime on one card.

Seat selection for Lumo Shibuya with three seats chosen and a running total in yen — Seat selection · Tokyo · ¥750 running total

Issued ticket with QR code, seats, venue address and the amount paid in yen — The issued ticket · paid in yen, kept in yen

06

Beyond the transaction

See the room before you commit to the seat.

Lumo runs a 3D layer in the browser — no app to install, no headset required. It turns a seat number into something a customer can actually judge.

360° trailers

Trailers played inside a virtual auditorium rather than a rectangle on a page.

Venue tours

Walk the foyer and the screens before booking — useful for premium tiers.

Shared lobby

A social space where an audience gathers ahead of a showing.

Narrated guide

An in-venue guide that speaks six languages, with hand-written scripts in each.

Virtual tour of Lumo Leicester Square: the auditorium screen ahead, with an IMAX Screen hotspot open — Virtual tour · Leicester Square · a hotspot opened

07

Recommendations

A scoring model you can read and argue with.

Recommendations are not a black box. Each film is scored on five weighted signals, and the operator can see exactly why a title surfaced.

Genre match × 40% + Rating × 20% + Trending × 20% + Recency × 10% − Already watched × 50%

That last term earns its weight: without a heavy penalty for films the customer has already seen, popular titles dominate every list and the feature stops being personal at all.

08

For the operator

The console the venue team actually works in.

Venues and screens

Create a venue, add screens, and design each seat layout row by row — including aisles, which renumber the seats around them the way a real venue labels a row.

Showtimes and holds

Schedule showings, set tier prices, and hold seats back from sale. Double-booking a screen is rejected, and a sold seat cannot be held.

Two levels of access

A group administrator sees the whole estate; a venue administrator sees only their own sites — and the system never confirms that the others exist.

Every administrative action is authorised on the server. The interface guard is a convenience, never the control.

09

Engineering

Current tooling, and a demo that runs anywhere.

The platform is built on the current generation of the React ecosystem, typed end to end. What you are evaluating today is a complete static export of that interface: 176 pages, no server, no keys, no database — it will run from a laptop with the network switched off.

Next.js 16 React 19 TypeScript Tailwind CSS v4 Three.js 39 films · live metadata

The production application and the offline demo share one codebase. Nothing was rewritten or stubbed to make the demo work, so what you click is what ships.

10

Where it stands

Built and working. Here is the honest boundary.

Complete

The product

Booking, venues, seat selection, tickets, the 3D layer, recommendations and the operator console.