Digital Kiosk Content Setup in Richmond, TX 77406

A kiosk is four separate systems, and only one of them is the screen

When somebody reports that a kiosk stopped working, the fault sits in the content layer far more often than in the glass. Getting to it quickly means knowing which of four independent systems broke, because at ten feet away they all look the same.

The first fork is which player you are authoring for. Commercial panels increasingly run the player on a chip inside the display — one cable, no separate box, nothing to steal. The trade is that you are bound to that manufacturer’s platform and however long they keep publishing firmware for it, with narrower codec support than a small computer. An external player costs more to mount and feed, but takes wider formats and can be swapped in ten minutes when it dies.

Authoring to the panel instead of fighting it afterwards

Almost every legibility complaint traces back to artwork built on the wrong canvas. A portrait kiosk wants artwork built tall from the start, not a wide file spun ninety degrees — some chip-based players scale a landscape asset first and rotate it second, softening every edge of the type before it reaches the glass.

• H.264 video inside an MP4 container is the safest common denominator across nearly every player platform we meet.
• Avoid variable-frame-rate exports — phone screen recordings are the usual culprit — because many players stutter or drift on them.
• Flat artwork with text stays crisper as PNG; photographic backgrounds compress better as JPEG.
• Name every asset for what it is and when it dies, never a camera filename.

Type size is arithmetic, not taste. Divide a panel’s vertical pixel count by its physical height in inches and you get pixels per inch — on a widescreen fifty-five-inch display that lands near forty. Signage practice puts comfortable reading at roughly one inch of capital height per ten feet of viewing distance. A lobby kiosk read from twelve to fifteen feet therefore wants capitals near fifty to sixty pixels tall. Body copy set at a web page’s default size is decorative at that range, and nobody will tell you — they will just stop looking at the screen.

Loop length, dayparts and the expiry date that saves you

A playlist is a sequence of assets with a dwell time each, and the sum of those dwells is the loop. Match that against how long a human actually stands there. Someone waiting on a leasing agent may give a screen four minutes; someone crossing a clubhouse mailroom gives it eight seconds. Load a four-minute loop where dwell is under fifteen seconds and most of your audience sees exactly one asset, possibly the least important. In pass-through positions we argue the loop down to a handful of short items and rotate the set weekly.

Dayparting — a morning set, a weekend set, a holiday set that fires itself — is genuinely useful in amenity spaces where the audience changes completely between a Tuesday morning and a Saturday afternoon. It depends entirely on the player knowing the time, which is why clock sync is a content problem and not only an IT one.

The highest-value habit we set up on every account is a hard expiry date applied to each promotional asset at upload. Content that outlives its event is how a kiosk loses credibility, and it never announces itself. An asset that removes itself on the right date turns a forgotten screen into a self-cleaning one. We pair it with a short evergreen set that plays when everything scheduled has expired, so the fallback is a tidy identity slide rather than a black rectangle.

What the kiosk does on the day the internet drops

A properly configured kiosk is boring during an outage. Content is cached to local storage, so the loop keeps running off the last good copy and simply stops receiving updates until the link returns. Kiosks that go black in a circuit fault are almost always pointed at live streamed content with no fallback designed behind them.

Three network details cause most of the calls. Guest wireless expects a human to tap an accept button periodically and an unattended player cannot, so a kiosk needs a real network path — ideally a wired drop. Outbound filtering matters next: players reach a management service and a time source, and a firewall change that quietly closes either leaves the screen playing old content for days before anyone notices it has gone deaf. Third, reserve the player’s address so its heartbeat is traceable and a technician on the phone can be pointed at the right device.

We also schedule an overnight restart. Browser-based layouts leak memory over weeks, and a reboot in the small hours clears the fault class where a kiosk is responsive but progressively slower. Combined with the panel’s own scheduled power cycle, the display is not holding a static logo on the same pixels all night.

Where these kiosks land west of the Brazos

This side of Richmond is master-planned growth — Aliana, Long Meadow Farms, Grand Vista, Waterside and the newer sections feeding off the Westpark corridor and the Grand Parkway. That shapes the work in ways an older part of the county would not.

• Amenity centres and clubhouses. The most common kiosk out here: one screen carrying pool hours, class schedules and community notices. The content owner is usually an on-site lifestyle director, and the real constraint is approvals — anything on that screen may pass a board, so the schedule has to tolerate content arriving late. We build those accounts so one person can swap a single slide without touching the layout.
• New retail and medical suites. Tilt-wall and stucco centres along the tollway and FM 1093 lease as shells. Catch it during finish-out and a drop and receptacle land exactly behind the screen for the price of asking; after the finishes are in, the same result means cutting and patching.
• West-facing glass storefronts. Late afternoon sun across a glass front washes out a standard indoor panel for the busiest hour of the day. Sometimes the fix is content — heavier type, higher contrast, no thin light-on-light layouts — and sometimes it is honestly a brighter panel or a different wall, which we say on the estimate rather than after.
• Gated access. Several of these neighbourhoods are gated and the amenity buildings run on scheduled access, so we confirm gate and door arrangements before the appointment.

What EVOTECH actually does on a content setup engagement

1. Sit down with whoever owns the message. Before any software, we want the list of what the screen is for in priority order, and who signs off. That conversation routinely shortens the build, because half the wish list belongs on a website.
2. Confirm the canvas. Panel size, orientation, viewing distance and player platform, measured on site. Everything downstream is authored to those numbers.
3. Stand up the account. Screens named so a human can tell them apart, roles set so the front desk cannot break the layout, time zone and clock sync confirmed on the player.
4. Build the layout and first playlists, including the evergreen fallback and the schedule rules, with dwell times set against the dwell we observed in the space.
5. Review every asset at full size on the real screen, from where people will actually stand, and reject anything that does not read.
6. Break it on purpose. Pull the network and watch the cache hold; power cycle the panel and confirm it returns to the loop unattended.
7. Train and document — one short session plus a written sheet with logins, file specs and how to swap a slide. That sheet is what keeps the screen alive through staff turnover.

What changes the number on a Richmond content-setup quote

We quote after seeing the space, itemised, and never over the phone — the range between a one-screen clubhouse notice board and a scheduled multi-zone build is enormous. What genuinely moves it:

• Number of distinct layouts, not number of screens. Ten screens playing one design is a smaller build than two screens with two zone layouts.
• Whether usable artwork exists. Print-ready flyers are the wrong shape and resolution for a screen; rebuilding them to the canvas is real work we would rather quote than surprise you with.
• Schedule complexity. One loop running all week is quick. Separate morning, evening, weekend and seasonal sets with override rules is another exercise.
• Interactive versus playback. The moment the public touches it you have added lockdown, timeouts and testing.
• Existing infrastructure. If the drop and mount are already right, the visit is content only.

Related services

Frequently asked questions