Casting hardware, signage software and the alerting system are usually three purchases, three renewals and three vendors. Here they are one product.
One message takes over every screen at once, sent from a phone, on site or across town. Written text is spoken aloud through the screens, it interrupts whatever was playing, and nothing else can outrank it. Screens that were asleep wake up for it.
Whoever is presenting opens Ava and casts to the rooms they are allowed to reach, which need not be the one they are standing in. No pairing code to hunt for, no dongle to find, no adapter to unplug. Nobody else on the network can see a display, let alone connect to one. When the host wants somebody else to take the screen, they put a code on the screen itself, as digits and as a QR code. The other person scans it and asks for the screen, the host accepts, and nothing reaches the glass until they do: a teacher taking one student after another, or a chair handing the room to a visitor. Same mechanism either way.
When nothing is being cast or broadcast, a screen is not blank and not a fixed slideshow. It rotates through cards chosen for that screen: by priority, by the time of day, by the date, and by where the screen physically is. A hallway at lunchtime and a front office at eight in the morning are not showing the same thing, and nobody set that up twice.
A broadcast is different: an interruption you schedule. Morning news plays together across rooms, pre-loaded onto every device beforehand so the network is not carrying it at the moment it matters, then the screens return to their idle rotation.
The screens know the schedule, including the days that break it. Assembly timetables and odd-even rotations change what is shown without anyone touching a screen.
Post to one room, a wing, a building or everything. Roles decide who can do which, and every action is recorded against the person who took it.
Ava Display is one surface of a larger platform. Most signage systems are a content manager with a media player attached: someone builds a slide, someone schedules it, and the screen plays it back. Ava works the other way round. She holds what your organization actually knows, and the screens read from that.
A closure, a shift change, a room move or an early release is a fact about your organization, not a slide. Tell Ava once and the hallway screens, the room displays and the front desk all reflect it, because they are all reading the same thing rather than each holding their own copy.
That is also why the screens know what day it is. Shift patterns, term dates, bell schedules and the days that break them are not signage content someone remembers to update. They are what the place runs on, and the screens follow.
Casting, signage, announcements, bell awareness, emergency broadcast and fleet management are one system with one login and one bill. Nothing between them needs wiring together, because nothing between them was separate.
The screens you already trust become the way a teaching partner reaches every room. Ava Classroom adds lessons, practice and the bridge home, on the same devices and the same login. Display is the safe place to start, and nothing gets replaced to go further.
Runs in any browser today.
Most signage is stills with a play button bolted on. Video is the part that separates a platform from a slideshow, because it is the part that needs a backend: something has to get the file onto hundreds of devices before it is due, decide what yields to what, and prove afterwards that it played.
A campaign, a safety film, a training video or a season trailer is cached on every screen before its slot. When the moment comes it plays at full rate from local storage, so a busy network at the wrong minute cannot turn a paid spot into a frozen frame. Every screen reports that it actually played.
A camera or a screen capture goes out as a live stream to every display in scope: a keynote to overflow rooms, a leadership address across a campus, morning news from the studio down the corridor. It starts from a browser and needs nothing installed in the room it is coming from.
A person presents to the screens they are allowed to use, in several rooms at once, from anywhere. authorized rather than discovered, so there is no pairing, no dongle and no display visible on the network.
Most of the day, no one is casting and nothing is being broadcast. That is when a signage system either earns its place or sits there showing a logo. Ava chooses what each screen shows from three things at once.
A gym, a front office, a staff room and a cafeteria want different things. Cards are targeted at rooms, wings or the whole site, so a screen shows what belongs in that place without anyone configuring it screen by screen.
Cards carry the hours, the days of the week and the date range they apply to. Breakfast before the bell, the day rotation during class, the game on Friday, and the whole thing changes for a holiday week on its own.
Everything eligible is ordered by priority and each card holds the screen for a set dwell before the next one. Something urgent moves to the front of the rotation rather than waiting its turn.
A broadcast is the opposite of this: a deliberate interruption that takes the screen, then hands it back. The rotation is what the screen does for the rest of the day, and it is the part nobody should have to maintain.
Most workplace and classroom technology gets better on a vendor roadmap, at a vendor pace, decided by people who have never stood in the room. This one has a request button in the console, and the people who wrote the software read it.
Staff raise a request from the same console they use to cast. No support ticket, no account manager to route it through, and no waiting for an annual survey nobody remembers filling in.
Requests carry a state your staff can see, so whoever asked for something knows whether it is being considered, is being built, or has shipped. Asking into silence is what makes people stop asking.
We are the people who build it, so a good idea does not have to survive three layers of prioritization to become real. Requests from staff on site are already in the product.
This is why the feature list on this page will be out of date. It grows most weeks, and the direction it grows in is set by the people using it.