01
Clinic waiting room
Example: A queue board calling the next patient
Approach: Show a ticket number or initials chosen by the clinic, never full names, dates of birth or reasons for the visit
Digital Signage
Digital signage CMS and player app development
Screens in stores, lobbies and waiting rooms go stale, go blank when the network drops, or show something they should not. Agnotic Technologies builds digital signage software: a content management system your teams schedule from and player apps that keep playing offline.
Daypart schedulingOffline playbackProof-of-play logsRemote device management
Trusted by global innovators
What is digital signage software?
Digital signage software is the content management system and player apps that decide what each screen shows, where and when, and prove that it played. Agnotic Technologies builds digital signage software for retail stores, hotels, campuses and clinic waiting rooms, with scheduling by location and daypart, offline players and remote device management.
We build the software, not the screens. You choose the displays and media players; we write the CMS, the player app for that platform and the monitoring that tells you when a screen is off.
Most screens also show live data: menus and prices from the POS, queue numbers from a ticketing system, room bookings or campus alerts. Each feed gets a fallback, so a screen never shows an error page.
Player platforms
Which player platform should each screen run?
The platform decides how the player caches content, how it is managed remotely and how it is updated. We choose per screen type, and one CMS can drive all three.
| Screen platform | Offline support | Remote management route | Update method |
|---|---|---|---|
| Android media player or tablet in dedicated device mode | Native app caches playlists and media on the device | A device policy controller or EMM, with lock task mode keeping the screen in the player app | App updates through the EMM; system updates frozen during opening hours |
| Web player on a small PC or stick | A service worker and browser cache hold the playlist and media | The operating system's management agent plus the player's own heartbeat | The player updates when the web app is redeployed; OS patches through the agent |
| Commercial display with a built-in system on chip | Depends on the display's app platform, usually local storage for media | The display maker's management tools or its local network API | App packages pushed through the maker's tools; firmware on its own schedule |
Interactive screens such as wayfinding or self check-in add touch input and accessibility needs, so we scope them apart from playback-only screens.
Content rules
What should each screen be allowed to show?
A screen in a public space is a disclosure. We set content rules per venue, and on clinic screens we design to the HIPAA minimum necessary standard.
02
Pharmacy pickup
Example: An order ready notice
Approach: Order numbers only, with names confirmed at the counter
03
Retail store
Example: Prices and promotions
Approach: Prices come from the same source as the till and expire with the promotion
04
Hotel lobby
Example: Event and meeting room listings
Approach: Only what the organizer approved for public display; private bookings stay hidden
05
Campus
Example: Emergency alerts
Approach: One action overrides every screen, and an authorized user clears it, with both steps logged
Platform layers
How is a digital signage platform put together?
Six layers, so a screen keeps playing even when the CMS, a data feed or the network is down.
Content and approval
- Media library and templates
- Approval before anything is scheduled
- Contrast and flash checks on templates
Scheduling
- Playlists by location, screen group and daypart
- Priority slots for urgent messages
- Calendar exceptions for holidays and events
Data feeds
- Menus and prices from POS or ERP
- Queue numbers and room bookings
- Fallback content when a feed fails
Player
- Downloads and caches the schedule and media
- Plays offline from local storage
- Reports heartbeats, errors and plays
Device management
- Screen status, screenshots and restarts
- App and OS updates in maintenance windows
- Alerts when a screen goes dark
Proof of play
- A record of every play with time, screen and content
- Reports for advertisers, franchise owners and audits
Failure points
What breaks digital signage, and how do we design around it?
The problems we plan for on every signage build.
Challenge
The network drops and screens go blank.
Agnotic approach
Players cache upcoming schedules and media and keep playing offline, then upload play records when the network returns.
Challenge
A failed data feed shows an error on a public screen.
Agnotic approach
Each live widget has a timeout and fallback content, so the screen shows the last good data or a static slide.
Challenge
Nobody knows a screen is off until a customer mentions it.
Agnotic approach
Players send heartbeats and screenshots; a missed heartbeat opens an alert for that site.
Challenge
One update breaks every screen at once.
Agnotic approach
Updates go to a small group of screens first, then roll out in stages inside a maintenance window.
Challenge
Content goes live without review.
Agnotic approach
Nothing reaches a screen until an approver signs off, and urgent messages use a separate, logged path.
Challenge
Flashing slides or low contrast make screens hard to read.
Agnotic approach
Templates are checked against WCAG 2.2 contrast and flash thresholds before approval.
What do we build into digital signage software?
Modules for the CMS, the players and the people who look after the screens.
Content management system
Media library, templates and playlists, with roles for head office, regions and individual sites.
Scheduling engine
Schedules by location, screen group, daypart and date, with priorities and urgent overrides.
Player apps
Android, web and display platform players that cache content, play offline and report back.
Device management
Heartbeats, screenshots, remote restarts and staged updates, through your EMM or the display maker's tools.
Proof-of-play reporting
A record of every play for advertisers, franchise owners and compliance audits.
Live data widgets
Menus, prices, queues, room bookings and alerts from POS, ERP and building systems, each with fallback content.
Approval workflow
Draft, review and approve steps, with every change to a live playlist logged.
Standards
Which platform rules and standards does signage software follow?
Android dedicated devicesW3C Service WorkersWCAG 2.245 CFR 164.502
Facts and sources
Facts behind digital signage software
The platform, privacy and accessibility rules the player and content checks are built on, each linked to its primary source.
Android dedicated devices, formerly called corporate-owned single-use (COSU) devices, are fully managed devices that serve one purpose, such as digital signage; a custom home app can lock the device to an allowlisted set of apps with lock task mode and freeze over-the-air system updates during critical periods.
Source: Dedicated devices overview (Android Developers)When using or disclosing protected health information, a covered entity or business associate must make reasonable efforts to limit it to the minimum necessary to accomplish the intended purpose.
Source: 45 CFR 164.502(b) (eCFR)The HIPAA Privacy Rule permits a use or disclosure incident to an otherwise permitted one only if the covered entity has met the minimum necessary requirements and the safeguard requirements of 45 CFR 164.530(c) for that permitted use or disclosure.
Source: 45 CFR 164.502(a)(1)(iii) (eCFR)WCAG 2.2 success criterion 2.3.1 (Level A) says web pages must not contain anything that flashes more than three times in any one second period, unless the flash is below the general flash and red flash thresholds.
Source: WCAG 2.2, SC 2.3.1 Three Flashes or Below Threshold (W3C)WCAG 2.2 success criterion 1.4.3 (Level AA) requires a contrast ratio of at least 4.5:1 for text and images of text, and at least 3:1 for large-scale text.
Source: WCAG 2.2, SC 1.4.3 Contrast (Minimum) (W3C)
Who it is for
Who do we build digital signage software for?
Organizations running screens across many sites.
Retail chains and franchises
Promotions and prices scheduled from head office, with local slots for each store.
Hotels and venues
Lobby, event and wayfinding screens fed from booking and event systems.
Campuses and offices
News, room displays and emergency alerts across buildings.
Clinics and health systems
Waiting room and queue screens that call patients without showing who they are.
Screen network operators
Advertising networks that need proof-of-play records for every advertiser.
Scope and cost
What drives the cost of digital signage software?
We do not publish prices. These are the things that change the size of a build, and we price them on the scoping call.
Screen platforms
How many player platforms the first release must support.
Sites and screens
How many locations and screen groups, and how content ownership is split.
Live data feeds
POS, ERP, queue, booking and alert feeds, each with its own fallback.
Interactivity
Whether any screens take touch input, such as wayfinding or check-in.
Proof-of-play reporting
The reports advertisers, franchise owners or auditors need.
Device management route
Your EMM, the display maker's tools or a management agent we build.
Engagement
How does a digital signage engagement work?
We prove offline playback at real sites before rolling out.
1.
Scoping call
We list your screen types, locations, content owners and data feeds, and choose the player platforms.
Scope2.
Pilot sites
A fixed-scope first release: the CMS, scheduling and a player on one platform at a few pilot sites, with offline tests.
Build3.
Roll out and support
More platforms, feeds and sites, staged updates and support after launch.
ScaleFrequently Asked Questions
No. Agnotic Technologies builds the software. You choose the displays and players, and we build for those platforms or tell you what the software needs from them.
The player keeps playing from its local cache, follows the schedule it already downloaded and stores play records. When the connection returns, it fetches new content and uploads the plays.
Yes. Live widgets read from your POS or ERP, so the screen and the till use the same price. If the feed fails, the screen shows the last good data or a fallback slide.
Queue screens show only what the clinic chooses, such as a ticket number or initials, and never names with reasons for the visit. We design to the HIPAA minimum necessary standard, and the clinic signs off on what each screen may show.
Proof of play is a record of each time content was shown, with the screen, time and duration. Advertisers, franchise owners and auditors use it to check that paid or required content ran as scheduled.
Yes. Roles decide who edits what: head office schedules brand campaigns, regions add local promotions and each store fills its own slots, all through an approval step.
The number of player platforms and live data feeds in the first release sets most of the schedule. We agree a fixed first release at a few pilot sites on the scoping call.