improvements - "freezing the flows"

hey, this is supercool! It can give space to lot of playful and interesting applications!

Can I contribute with a UX suggestion and a discussion ?

I tried to play a bit - what about to make persist the apparent movement ?
The idea is that once a movement is given, the ball will keep on moving.
So instead of calculating the flow at any step, it would be possible to calculate the Impulse given at a step, and if the Impulse > threshold (e.g. velocity of vector), the ball will move.

Reading about getUserMedia() is possible to pass a frame rate, and maybe delay the frame rate to make persist the last calculation of the flows.

https://addpipe.com/blog/getusermedia-video-constraints/

No files, tests, or entry points are named. Start by reviewing the repository's optical-flow implementation and camera-input handling; done requires an agreed approach for retaining movement after an impulse exceeds the proposed threshold.

Written by the indexing model from the issue text.