Places of worship

Announcements that
outlive the printer.

A noticeboard by the door, a screen in the hall, and one volunteer who can change both from a phone browser. Service times, announcements, appeals and welcome — published without anyone needing to be technical.

Plans, prices and trials are set by your ScreenQube partner.

A community hall noticeboard screen listing service times, a community lunch and a roof repair appeal.

Where it ends up

You work in a browser.
They see the wall.

The screen above is what you publish. This is where it ends up — a display a customer stands in front of, driven by a player that fetched it on its own.

A large lobby screen welcoming visitors to a conference, beside a reception desk and seating.
A video wall on an exhibition stand. You work in a browser. This is the other end of it — a display a customer stands in front of, driven by a player that fetched its content on its own.

What goes on the screens

Six things worth putting up.

Every one of these is ordinary media, arranged in Composition and sent out by Publish. Nothing here needs a separate system.

Service and prayer times

The one thing every visitor is looking for.

Announcements

This week's notices, published with a start and an end.

Appeals and giving

Progress against a target, changed as it changes.

Groups, classes and community events

The hall diary, on the hall wall.

Welcome and orientation

Where to go, what happens, and who to ask.

Codes for giving and sign-up

A code on the screen is easier than a form at the door.

Where the screens go

Four walls that earn it.

  1. Entrance and porch

    Times, welcome and what is on today.

  2. Main hall

    Announcements before and after, and the appeal in between.

  3. Community rooms

    The diary for the groups that use them.

  4. Notice wall

    The printed board, replaced by one that is current.

How it is run

Four steps, then it runs itself.

The same four steps whether you have four screens or four hundred. This is the real console, not an illustration.

  1. Add facilities, pair screens

    One facility per site, branch or building. A screen joins by showing a registration code, which you type in once. Switch between facilities from the header.

  2. Upload and compose

    Media goes into the library, in folders, with tags. Composition arranges it into zones — your own files, plus App Store apps like weather, news or a ticker.

  3. Publish three ways

    On a schedule, with day sequences. Or QuickPlay, which the console describes as displaying content instantly for a flash sale or an emergency. Or as the default composition a screen falls back to.

  4. Check it, without going there

    Live Monitoring reports each screen's state. Take Screenshot shows what one is really displaying. Reload, clear the cache or reboot it remotely.

What it fixes

The three complaints we actually hear.

Notices are printed by whoever has a printer, and never removed.
Publish carries a schedule. A notice can be given an end date.
Only one person knows how to change the screen.
It is a browser and a media library. Users belong to groups, so more than one person can be trusted with it.
Nobody notices the hall screen is off until Sunday morning.
Total Disconnected Screens is a headline tile on the dashboard.

Set it up as

The solutions this usually becomes.

Nearby

Other industries with the same problem.

Questions

What places of worship teams ask first.

Is this too much software for one hall?

The console is the same whether you run one screen or four hundred. What you pay for is set by your ScreenQube partner, in their own plan.

Can a volunteer change it from a phone?

The console runs in a browser. A mobile-specific app has not been confirmed.

Can we stream the service to an overflow room?

Live streaming has not been observed in the console.

What hardware do we need?

A display that runs Android, plus the player app.

Put it on every screen.

Talk to us about becoming the partner who sells it.

We will introduce you to the partner who covers your region.