I understand the project to require:
* A Video Player, that will take up the user's whole screen once the application is opened.
* A navigation input, which relates each video with a corresponding letter (i.e. A = 1, B = 2, and so on.)
* A Play/Pause Button, in the form of the "K" button on a keyboard.
* A set of timeskip buttons that move in increments of 3 seconds, for M and L going back and forward respectively.
* A seperated, dedicated button specifically for playing in the form of the "N" button on a Keyboard.
At a glance, this sounds like a 2, maybe 3 day job at most, allowing for complications in the video formats, file sizes, and resolutions to be worked out.
I do have some clarifications I'd like to clear up:
* Is what's needed a resource folder that the app references to load video files from at runtime (So that modifying this folder after building the project will change what's inside)? Or will the videos be compiled into the app executable (Which means once the project is built, any changes will require a rebuild)?
* Should videos be stretched to full screen, even if they don't fit the screen resolution? Or is the desired behavior to "Fit" the dimensions as close as possible, without exceeding the screen's smallest dimension?
* Should the videos be always full screen, even if their resolution makes the appearance grainy?
* Will the application run on Windows, MacOS, or a Linux system? I can only handle test cases for Windows based applications.