September 25, 2019

Technical Feasability

Tim Reid @tmrd

I've been researching how I'm going to build Backwards. As with any idea, there's always more to it than meets the eye.

Firstly there will be a web app. Users will need to be able to log in, setup multiple channels, match behaviours, and select audio for each associated state.

This data will need to be persisted to a backend.

I also need a way to track users activity, a browser extension seems to be the obvious method here.

The web app will need to play audio, and retrieve the audio tracks from remote storage somewhere. Because the audio tracks may be quite long, I need to read up on range requests, HTTP 206 responses, and the content-range header.

Back with more info soon.

Loading comments...