...
Each player interactions ie. StartPage, Endpage, Menu, Navigation, etc is also a library which that will get injected based on the input config to the player.. [TBD]
Here we will have the extension points which player should define to
Events (TBD)
START
Code Block |
---|
{ "typeeid": <uuid>, "STARTets": <timestamp>, "metaDataver": "<object>" // will change based on player<event-version>, "type": "START", "data": "<object>" (TBD) } |
END
Code Block |
---|
{ "typeeid": <uuid>, "ENDets": <timestamp>, "metaDataver": "<object>" // will change based on player <event-version>, "type": "END", "data": "<object>" (TBD) } |
EVENT
Code Block | ||
---|---|---|
| ||
{ "eid": <uuid>, "ets": <timestamp>, "ver": <event-version>, "type": <event-type> // play, pause, scroll, touch, heartbeat "data" : <object> } |
Event library emits the above events and container should convert them to telemetry events when in standalone mode?
Distribution and composability
The primary distribution will be npm as the angular library
{
Player :
static dependencies {
Events Library
...