You're running audiotool on your browser. Browsers are notoriously bad at handling resources. Audiotool booster is a native application. It doesn't run on your browser, but on the specific setup of your PC as an application (this is called a native app).
So, you're running windows: you download the windows version of the booster, run it, then open up AT and it connects with the booster. Essentially, you are now sharing resources between the studio and the booster. In particular, the audio code that is running in the webapp is now going through to the booster, and working directly with your audio driver rather than waiting for the more inefficient browser to handle it first.
There's a lot more technomancy going on in the background (which I am almost 100% certain I don't understand) but that's the long and short of it. Hope this has helped!
I take it you didn't read all of what flamento wrote, then?
It isn't a native app that works as a typical DAW, instead, it shares resources between the (online) studio, and the booster. It literally boosts performance of the (still online) studio, but it doesn't turn the studio into a native app.
You're running audiotool on your browser. Browsers are notoriously bad at handling resources. Audiotool booster is a native application. It doesn't run on your browser, but on the specific setup of your PC as an application (this is called a native app).
So, you're running windows: you download the windows version of the booster, run it, then open up AT and it connects with the booster. Essentially, you are now sharing resources between the studio and the booster. In particular, the audio code that is running in the webapp is now going through to the booster, and working directly with your audio driver rather than waiting for the more inefficient browser to handle it first.
There's a lot more technomancy going on in the background (which I am almost 100% certain I don't understand) but that's the long and short of it. Hope this has helped!