Website integration Web Speech Api + Text processor

The website must have/allow the following functionality:
1)An audio/video player that can pause,play, rewind, etcétera.
2)A text processor where the trancription appears, must allows for shortcuts (for exemple, when i press "shift" the text processor should introduce  after the last linebreak (or shift)  a prefix: Important things: together with a line break and a Caps for the next word; when i press "enter" it send the text above to the API1, when i press * it send the text above to the API2 etcétera).
3) 2 API (out): API1 one that connects with an Android APP (for users), and the other that connects with a website.



4)Integration with Web Speech API (https://wicg.github.io/speech-api https://github.com/WICG/speech-api/issues/), for live transcription. Of course the pc's in which this will be used have the following configuration: external audio-->splitter--->microphone+external audio. The text must appear in the text processor as the audio/video is being played, just like webcaptioner does, but it must allow the edition of the transcription as it's being transcribed (webcaptioner only shows you the transcript, doesn't allow you to modify it), must not introduce linebreaks when the audio/video is paused, and must allow different languages to be used.



It will be tested against webcaptioner (it's using the same API so it should yield similar results)
5)Upload an .srt together with a audio/video file. When the audio/video plays, the text processor must show the transcription from the .srt, part by part as the audio/video advances, without the linebreaks, this is, the text must apper all together,in a webcaptioner kind of style.


This are the core features, at first it will be beta tested and improved for a time, but eventually it must be added an users interface and usser accounts in whichs to save incomplete works, you can send me your budget with and without the users part.
The final design, how the video player, text processor, API, etc must be integrated together will be described  via private messages.
The $$ destined to this proyect will depend of what you can offer, have in mind that there're also other people approaching proposals.



This will be a work for the development described before, and after we will also need to fix eventual bugs or add news features or just general support, so we can also arrange a monthly fee for that.

The freelancer who develop the project must also agree  to renounce all property rights of the software and that the development will not be used in other project or made public.