Use a DisplayManager to handle the coordination of overlays

[rtshkmr]

Display Manager Skeleton

The intent of DislayManager is to be able to determine the following things:

1. which layout (e.g. mobile vs desktop) to use (if we’re discriminating b/w device types)
2. hold state about current app mode and other configurations about it.

It seems there are 2 choices when structuring things:

1. We could keep the DM as a sibling of the other liveviews (MediaBridge, Written)
2. DM could be a parent for the other liveviews under it, effectively being somethng like a “stateful layout”

Some questions:

1. Are the user action buttons going to be another liveview or a livecomponent?
   • the only requirement is that, similar to the MediaBridge, stickiness is there even on page-reloads.
     For now, I shall keep the necessary state within the DM

Possible Steps:

1. Nest existing extra live_views within the DM, to create a parent-child r/s
   • quick POCs have shown that the pub-sub comms work regardless of how live_views are nested, so this doesn’t affect the comms b/w these server-side components
2. Add some dummy state in DM, let DM also know the type of device by receving an event from the client-side