Should digital signage run standalone or in the cloud?

One building or campus with up to 50 screens suits standalone mode on a local server with no cloud dependency; multiple sites, cities or countries suit cloud mode. The management desk works the same either way, so many clients start standalone and migrate.

What happens when a digital signage screen loses network?

It keeps playing - content downloads to the terminal's 32GB local storage on schedule and playback runs from that cache. A network drop pauses updates, not the show.

How bright must an outdoor digital signage screen be?

Bright enough to beat the site's direct sun - shaded entrances need far less than west-facing plazas, so brightness is specified per position from a site survey rather than one catalog number.

Home / Solutions / Media Publishing System

SPECIAL SCENARIOS

Digital Signage: Update Every Screen in Every City From One Desk

Q: Can different screens play different content?

Yes - screens group by site, zone or purpose with their own playlists and schedules, while a company-wide notice can override all groups at once. Multi-screen synchronization lets adjacent screens play as one coordinated display.

Q: Can digital signage run ads and earn revenue?

Yes - the scheduling engine sells slots by daypart and screen group, and playback logs give advertisers per-screen, per-day proof of play. Reliable screens, a rate card and local advertising compliance are the prerequisites.

Lobbies, malls, school corridors, visitor centers, lift landings — anywhere a poster hangs today, a managed screen earns more attention tomorrow. This system publishes text, images, video and live notices to fleets of Android-powered displays, in standalone mode (up to 50 terminals) or cloud mode across cities and countries.

Why Posters and USB Sticks Don't Scale

The original solution lists what breaks in manual information publishing:

Content updated by courierNew price list, new campaign, new notice — someone drives to every site with a USB stick, and the update takes a week.

Fifty screens, fifty versionsWithout central control, every screen drifts: last month's promotion here, a typo there, a competitor price that nobody took down.

Nobody knows what's playingHeadquarters approves content, but what actually shows on the lobby screen in another city is a matter of faith.

Static boards, moving audiencesA printed poster shows one message forever; the audience walking past changes by hour — morning staff, midday visitors, evening events.

Dead screens found by visitorsA frozen or dark display in the lobby broadcasts exactly one message: nobody here is paying attention.

System Architecture

Per the original design: a browser-based content desk publishes to Android terminals over LAN, WAN or 4G; standalone mode runs a local server for up to 50 terminals, cloud mode manages fleets across cities and countries — same editing, scheduling and monitoring either way.

Simplified diagram. Screen types, sizes and mounting follow each site's traffic and viewing distances.

Six Jobs This System Does

Each card is a module of the original solution, in communications-manager language.

Publish once, play everywhereText, images, video, scrolling tickers and live notices go from the browser-based desk to any set of terminals — one campaign lands on fifty screens in the time it used to take to print one poster.

Schedules that run themselvesTimed playback, playlists and multi-screen synchronization: the morning welcome, the lunch promotion and the evening event notice rotate on schedule without anyone touching a screen — and a company-wide notice can interrupt everything, everywhere, in a minute.

Screens for every spotIndoor and outdoor wall-mounted displays, floor-standing posters and window screens — high brightness, high resolution, wide viewing angles — matched to each location's light, traffic and viewing distance instead of one size pretending to fit all.

Terminals you can trustThe players run Android 11 on ARM Cortex A55 with 4GB RAM and 32GB storage — enough to decode and loop multimedia around the clock, cache content locally and keep playing through network drops; app support means the same terminal can run interactive content later.

A fleet managed remotelyOnline status, content version, playback logs and remote reboot per device — the dead screen is discovered by the dashboard, not by a visitor, and fixed by a click, not a road trip; one administrator manages terminals across cities and countries.

Two modes, one deskStandalone mode keeps everything on a local server (up to 50 terminals) for sites that want no cloud dependency; cloud mode scales the same desk to chains and groups across cities and countries — start standalone, migrate to cloud when the fleet outgrows the building.

The Numbers That Matter

Key capabilities from the official solution:

Standalone mode: local server managing up to 50 terminals

Cloud mode: one platform across cities and countries

Android terminals: ARM Cortex A55, 4GB RAM, 32GB storage, Android 11

Content: text, images, video, tickers, live notices — scheduled and synchronized

Browser-based management — no client software to install

System Components

These are the equipment roles the solution is built from. Exact models are chosen per site conditions, country requirements and budget — several of our product lines fit each role, so we spec the model list after receiving your requirement list.

Item	What it does
Indoor wall-mounted displays	Lobbies, corridors, lift landings — sized to viewing distance.
Outdoor high-brightness displays	Sunlight-readable, weather-sealed units for entrances and plazas.
Floor-standing & window posters	Freestanding units for retail floors and glass-front visibility.
Publishing platform (standalone or cloud)	Content desk, schedules, device monitoring — licensed by mode and terminal count.
Site network	PoE switches simplify cabling where screens cluster.
Companion CCTV (screen-site security)	A dome per outdoor screen site deters vandalism and documents damage.
Content templates & commissioning	Launch layouts in your brand and languages, plus operator training.

Browse the full product catalog — cameras, NVRs & switches →

Send your site list (locations, indoor/outdoor, viewing distances) — we reply with a screen-by-screen plan, platform mode recommendation and BOQ.

Design Notes & Honest Limits

Read this before you order:

Screens don't create content — budget the content workflow (who writes, who approves, how often) alongside the hardware; a screen looping one stale slide is a printed poster that cost more.
Outdoor screens need brightness matched to your sun and sealed, ventilated housings for your climate — an indoor panel behind glass in the tropics dies its first summer; specify by site survey, not catalog page.
The 50-terminal standalone ceiling is a real line — plan the cloud migration path if your fleet will grow past it, so the switch is licensing, not re-deployment.
Public screens are a cybersecurity target — change default passwords, put terminals on their own VLAN and restrict publishing rights; a hijacked lobby screen is a reputation incident, not an IT ticket.
Advertising to the public may need municipal permits and content rules (brightness at night, no flashing near roads) — check local signage regulation before outdoor positions are fixed.

FAQ

Standalone or cloud — which mode should we pick?

By fleet size and geography: one building or campus with up to 50 screens — standalone keeps everything on your local server with no cloud dependency and no recurring hosting. Multiple sites, cities or countries — cloud mode gives one desk over the whole fleet. The desk works the same either way, so the pragmatic path many clients take: start standalone, migrate to cloud when the fleet outgrows the ceiling.

What happens when a screen loses network?

It keeps playing: content downloads to the terminal's local storage (32GB) on schedule, and playback runs from that cache — a network drop pauses updates, not the show. When the link returns, the terminal syncs the latest content and reports its logs. The screen that goes dark on a network blip is the pattern this architecture specifically avoids.

Can different screens play different content?

Yes — that is the core of fleet management: screens group by site, zone or purpose, and each group gets its own playlists and schedules. The lobby runs the welcome loop, the canteen runs menus, the outdoor totem runs campaigns — while a company-wide notice can override all groups at once. Multi-screen synchronization also lets adjacent screens play as one coordinated display.

How bright must an outdoor screen be?

Bright enough to beat your sun, which is a site property, not a catalog number: shaded entrances need far less than west-facing plazas. The honest method: we assess each position's direct-sun exposure and specify high-brightness, sunlight-readable panels only where they earn their premium — over-buying brightness for a shaded lobby is the most common way signage budgets are wasted.

Can this run ads and earn revenue?

Yes — the scheduling engine is exactly an ad-rotation engine: sell slots by daypart and screen group, load the creatives, and the playback logs give advertisers per-screen, per-day proof of play. Malls, visitor centers and lift landings monetize this routinely. The prerequisites are the boring ones: reliable screens (the dashboard keeps them alive), a rate card, and local advertising regulation compliance for outdoor positions.

Send your site list — get a screen-by-screen signage plan back

Locations, indoor/outdoor and screen count are enough for a first plan with platform-mode recommendation.

WhatsApp an engineer →