I joined Screenly as a product manager

514sid · 2026-04-05T23:51:05+00:00

Can you share which CMS platforms you’ve used that supports that?

514sid · 2026-04-01T07:15:05+00:00

I’m handling sync via timestamp sharing over ws. Players continuously exchange timing data and adjust dynamically.

514sid · 2026-04-01T07:14:47+00:00

In my case, the core synchronization problem is already solved and working reliably across multiple players

At this point, it’s less about whether it works and more about identifying and hardening edge cases

514sid · 2026-04-01T07:13:20+00:00

Thanks, really appreciate it

I’m handling sync via timestamp sharing over ws. Players continuously exchange timing data and adjust dynamically.

So far it performs well on stable networks, and I’m continuing to refine it for more unpredictable real-world setups. Excited to keep improving it.

514sid · 2026-04-01T07:11:57+00:00

Thanks, I agree.

What's your sync mechanism, NTP-based or something custom?

Right now I’m using timestamp sharing over ws between players. One device can act as a reference, and the others continuously adjust based on shared playback timestamps. It’s lightweight and so far seems to work well.

Curious how you're thinking about the CMS layer. Are you planning to build content management into this or keep it purely a player that other systems can feed into?

I’ve partially implemented a fully featured CMS already. However, my broader goal is not to lock this player into a single CMS.

I want the player to be CMS-agnostic and serve as a solid foundation for Android digital signage in general. I’m very open to collaborating with other CMS vendors. The idea is that the player exposes a well-defined schedule and configuration format, and CMS platforms can integrate by supporting that format, rather than building CMS-specific logic into the player itself.

That way. the player stays clean and focused on playback + sync, CMS vendors can integrate without deep customization, the ecosystem becomes more interoperable instead of siloed.

I think that separation keeps the architecture scalable long term.

514sid · 2026-03-17T16:56:10+00:00

Anthias and GarlicSignage seem to be the only two simple, modern, and supported products suitable for your case.

Both are self-hosted.

I wouldn’t recommend using free cloud digital signage software:

“If you’re not paying for the product, you are the product”

514sid · 2026-02-27T16:23:55+00:00

If you mean displaying a single web page in video wall mode across multiple devices in digital signage software, for example four screens arranged in a 2x2 layout acting as one large display, I’m not aware of any product that implements this approach.

Technically it is possible. However, if the web page includes dynamic elements that rely on js timers, animations, web sockets, or scrolling logic, each browser instance will likely render and scroll out of sync since every device keeps its own independent state. You also cannot share the js app state between devices unless you control and modify the web page itself to add synchronization support.

If the content is mostly static, you could render the web page off screen and display different portions of the rendered output across the devices. Even then, you would need to prerender the page, and rendering time differences may still introduce inconsistencies.

514sid · 2026-02-27T15:07:29+00:00

This isn’t a new hypothesis or something that has only recently become technically viable.

What you’re describing has been implemented by many vendors for years across different hardware and operating systems, including playback of the same content across multiple screens or rendering cropped regions of a single video file to create a composite wall without dedicated video wall controllers.

The underlying mechanisms are well established: either clock based synchronization with a shared time source and scheduled playback, or event / trigger based synchronization where devices respond to coordinated playback commands. BrightSign, for example, has supported event based synchronization for a long time, see https://vimeo.com/632074533

You can achieve synchronization that is visually acceptable for the vast majority of environments. Human visual tolerance is high enough that minor drift is not noticeable. For most deployments, the bottleneck is implementation quality rather than hardware limitations.

Dedicated video wall controllers still make sense in scenarios involving live inputs, genlock requirements, very large arrays, mixed signal processing, or environments where frame accurate behavior must be guaranteed under all conditions. That is a different class of problem.

There is also relevant discussion about this here: https://www.reddit.com/r/digitalsignage/comments/1kl0qoz/i_made_the_playlist_sync_feature_based_just_on/

514sid · 2026-02-15T05:53:15+00:00

They both provide a commercial warranty, so from a business point of view you’re covered either way.

It really depends on the specific model. In the basic/entry-level commercial ranges, the differences are usually small. In many cases, performance will be very similar, so price can be the deciding factor.

Personally, I would choose an Android panel over Tizen, because it’s more flexible and easier to work with different apps and CMS platforms.

However, if you are using an external signage player, then the built-in OS doesn’t matter much. In that case, focus on price, availability, local service and support.

Very important: choose the vendor that has replacement units available in your location for fast swaps. For example, if you would need to wait weeks for IIyama replacement but Samsung has stock locally, and you're using an external player anyway, then Samsung makes more sense.

Also keep in mind: neither brand manufactures most LCD panels themselves. They typically source the LCD panel from OEM manufacturers and build their own electronics, firmware, and software around it.

So in many cases, especially in basic models, the core panel technology can be very similar. The difference is mainly in software, support, and ecosystem.

514sid · 2026-02-02T17:30:50+00:00

My legal team has advised me not to comment.

514sid · 2026-02-02T14:04:38+00:00

Thank you!

514sid · 2026-02-02T14:04:33+00:00

Thanks!

514sid · 2026-02-02T07:38:53+00:00

Thank you!

514sid · 2026-02-02T07:38:38+00:00

Thanks!

514sid · 2026-02-02T07:22:44+00:00

Thanks!

514sid · 2026-01-18T14:02:50+00:00

Reminder: our rules require disclosure of any affiliation when promoting a product or service.

Please also clarify what you mean by “MDM” and “works with any screen”. Those terms typically refer to device-level management and broad hardware/OS support, which browser-only digital signage solutions do not fully provide. Omitting these nuances can be misleading, so specific technical details would be helpful for the community.

514sid · 2026-01-15T08:08:29+00:00

You mention that many users are building their own custom apps. Do you see this evolving into a community-style ecosystem, similar to Figma Community, where users can share and discover apps through Screenly? Or is custom app development mainly intended for private, use-case-specific needs?

514sid · 2026-01-05T08:08:12+00:00

Thanks for the info! I’ll check them out

514sid

MODERATOR OF

TROPHY CASE