Fleet view
One console across many panels: last seen, current layout, and push a board to a group.
Roadmap
Published because a gap you discover after deploying forty screens is worse than one you were told about. Nothing here has a date, because dates we cannot keep are worse than no dates.
Next
One console across many panels: last seen, current layout, and push a board to a group.
Dayparting — a different board at nine and at five, without anyone touching it.
Later
A distribution channel that does not require sideloading instructions.
Dated releases, so active development is visible without a hosted dashboard.
Direct connectors for the sources people keep asking for, rather than CSV in the middle.
Multi-screen interactive journeys for wayfinding and self-service.
Considering
Asked for often. Not a decision we have made, and we would rather not promise it than promise it vaguely.
Only meaningful with somewhere to report to, which means a cloud component we do not currently want.
The engine is web-based, so it is feasible. It is not scheduled.
If one of these is the thing standing between you and a rollout, say so — hello@unikiosk.io. What real deployments are blocked on is how this list gets reordered.
The features page describes only the shipped build. Anything unreleased is badged.