Chrome Extension

[prastut]

Latch onto (ranked in order of monetization preference):

• Hotstar video.
• Sony Liv video.
• Any YouTube videos for the world cup and show our UI elements. This could easily go on ProductHunt.

[prastut]

• Start connecting with our UI and backend pipeline.

[prastut]

Our purpose for the chrome extension is to be a sidekick to the consumer experience who are streaming videos on the desktops/laptops. Since we are focusing in the sports niche at the moment, the videos will be around that content.

So we would want to latch our UI elements (TrendingEntitites, ReactionFeed etc) onto these videos or the platforms that host these videos such as Hotstar, Sony Liv and YouTube. An extension will serve a dual purpose:

• makes it easier for the partnering company to see traction themselves without the said period of due diligence.
• makes it easier for us to raise investment since chrome extension + the second screen experience app = x users using it = traction = interest by VC's.

This is how I imagine it on YouTube (This layout would obviously change, but the elements will remain the same):

Full-screen:

What I need from the extension is the following events relayed to our blackbox:

• pause/play event.
• current duration inside the video.
• video end time.
• fullscreen event

This helps in making the UI reactive to the video player state.

[krshubham]

@prastut , when is the value of current duration required? and in what format is the end time required? We have end time in seconds, so for example if end time is 5:56. then we have 356 as the value.

[krshubham]

Should the current time duration be relayed when the user plays or pauses the video only or after every fixed interval of time?

[prastut]

when is the value of current duration required? and in what format is the end time required? We have end time in seconds, so for example if end time is 5:56. then we have 356 as the value.

First, let's break down the end goal. The timeline of a user interaction would look like this:

• User downloads the extension.

• User goes to some website (which we provide in the instructions) where our extension activates.

• Now generally video's in YouTube/Hotstar autoplay on click (which is different from the rest of the websites in the world where videos are started based on clicking on the play button, we need to account for both cases)

• I need the MATCH INFO & START events generated from the chrome extension for the UI to consume it.

  • Why MATCH INFO: If somebody is on FRANCE vs CROATIA final video page vs somebody is on the BELGIUM VS GERMANY video page, my UI will be different. Case in point my UI has to adapt to whatever page the user is currently viewing. That can be given via URL of the match, or the title of the video, something that uniquely identifies that page.
  • START: to start the UI.

• When the user clicks on pause -> PAUSE event -> I would pause the UI.

• When the user clicks on play -> PLAY event -> play the UI.

• When the user scrubs to a certain timeStamp inside the video -> the UI should adapt accordingly. For example I am watching FRANCE vs CROATIA match -> I watched till 55 seconds and then jumped to 2:55 in the video. That event should be relayed to the UI so that it adapts accordingly to the time inside the video.

TL;DR I don't think I need the current duration inside the video if you are able to sort the above usecase.

[krshubham]

Cool, got it!

[krshubham]

In what sense is MATCH Info given to the backend? Do we rely on title of the youtube video or what?

[krshubham]

This is what Youtube API returns if you query it for a video with its ID.

[prastut]

@krshubham Let's make this setup work for one video. Uske baad scale ka sochlenge.