Levels, zones and departments
The information somebody is standing there looking for.
Wayfinding
Directories that change
when the building does.
A printed directory is wrong the first time a department moves. A published one is a composition: change the line, publish, and every board in the building carries it.
Plans, prices and trials are set by your ScreenQube partner.
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.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
The board is a composition
Rows, arrows and levels are artwork arranged in Composition, not a database view.
-
One per building, or one per lobby
Publish to the screens that need this version and no others.
-
Portrait or landscape
Media is arranged for the screen it is going to.
-
Changed by whoever owns the building
Users belong to groups; groups decide what a person can reach.
What you get
Six things it does today.
Directional arrows
Part of the artwork, so they are as legible as the type beside them.
More than one language
A composition can rotate languages; the rotation is content, not configuration.
Changed in one place
One publish updates every board in the building.
A record of every change
Audits records who changed the directory and when.
Dark boards are counted
A wayfinding screen nobody can read is worse than a printed one, so it is a headline tile.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can a visitor search for a name on the board?
Not that we can evidence. Touch interaction has not been observed in the console.
Can we run a different directory per lobby?
Yes. Publish targets the screens you choose.
Can facilities teams update it themselves?
Users belong to groups, and groups decide what a person can reach.
What runs on the board?
An Android player app on a display you own.