Digital Signage

The problem

Screens in public spaces are almost always shouting. Loud loops, over-compressed video, weather widgets nobody asked for, a news ticker that dates within the hour. The best screens are quiet — a café menu that changes at three, a clinic directory that stays still, a classroom timetable that knows it is Thursday.

Most existing signage platforms are built for advertising, not communication.

What we're exploring

A signage platform with the opposite posture: calm by default, configurable only when you need it to be. A small CMS for people who don't enjoy CMSs. A runtime that survives flaky power and flakier internet. A fleet view that treats fifty screens the same as five.

Who it could be for: cafés, clinics, schools, corporate receptions, event venues. Anywhere a screen should inform, not sell.

Where it stands

This is early. We're in the planning and research stage — talking to people who run screens, mapping the real problems, and pressure-testing the idea before any production code is written. We'd rather be sure it's worth building than rush a build. There is no product to try yet.

The direction we're considering

A working hypothesis, not a commitment — it will change as the research does. We're leaning toward a split architecture: a resilient on-device runtime for screens that lose power and connectivity, a lightweight dashboard for composing and scheduling content, and a small channel for remote preview. The aim is reliability first, features second.

Questions we're working through

How offline is offline enough? · What does scheduling look like for someone non-technical? · How do you manage a fleet of screens without a dedicated operator? · Where does a white-label version make sense for existing networks?

If this is your world

If you operate a screen network — or are about to — we'd genuinely like to talk. Early conversations are what shape whether and how we build this.