A creator-facing overlay, not a public browser source
FeedNChat keeps the HUD inside the desktop application. It is intended to help the creator follow operational information while playing, presenting or producing—not to publish private dashboard data to viewers.
This separation keeps the broadcast layout in your existing studio while the creator retains a focused personal view of the signals that matter.
Adapt the surface to the session
Different formats need different amounts of information. A fast game may call for a compact, transparent chat surface; a podcast may benefit from larger questions and clearer cues.
FeedNChat provides configurable desktop controls for visibility, text sizing and placement. The objective is legibility without taking unnecessary screen space.
- Choose the operational content shown in the HUD
- Adjust opacity and text size for the current setup
- Keep the surface lightweight when it is not being used
Connected to the same control-room context
The HUD is not a second independent dashboard. It receives the relevant state from the same FeedNChat session, keeping messages, goals and cues consistent with the main control room.
Platform-specific restrictions still apply. FeedNChat displays and acts only on information available through the connected or monitored workflow.
FAQ
Questions creators ask
Is the FeedNChat HUD visible to viewers?
It is designed as a private desktop surface for the creator. Your broadcast composition remains under the control of your existing streaming software.
Can I change the HUD appearance?
Yes. FeedNChat provides controls for content, text size, opacity and placement so the HUD can fit different desktop setups.
Does an inactive HUD keep doing background work?
FeedNChat is designed to avoid unnecessary overlay activity when the surface is disabled or inactive.