Kiosk layouts as compositions
Composed and published like any other screen.
Interactive kiosks
Let people
find it themselves.
A touch kiosk lets somebody choose. Everything ScreenQube has been observed doing is playback — content published to a screen and played. That is a real distinction and this page keeps 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 layout composes fine
A kiosk screen is a composition like any other.
-
The playback half is evidenced
Publishing, scheduling, monitoring, reporting and auditing all apply.
-
The interaction half is not
No touch handling, menu logic or input capture has been observed.
-
Which makes this a question, not a page of features
Ask us and we will get a direct answer from the product team.
What you get
Six things it does today.
Scheduled content
Changes with the day, the week or the season.
Per site
Publish targets facilities.
Outage counting
A dark kiosk is a headline number.
Playback reporting
Reports run in three kinds: a Media Report, an Uptime Report and Audit Logs.
Change history
Audits, with a name against each action.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Does ScreenQube support touch screens?
Not that we can evidence. No touch interaction has been observed in the console.
Can a kiosk still be useful without touch?
As a playing information screen, yes — and it is monitored and audited like every other screen.
Who can answer definitively?
The product team. Contact us and we will put the question directly.
What runs on the screen?
An Android player app on a display you own.