1944
As if it wasn't bad enough that they want me to use a random internet service to add a keyboard to a usb wifi receiver, they have the balls to put this for Firefox users. I clicked out of pure curiosity, as I'm not even remotely interested in involving a corporate internet service in getting my keyboard connected to my computer. This is the message you get now on Logi Options software if you have a Unifying Receiver: 
For the curious: https://logiwebconnect.com
EDIT: some people on the thread have brought up that the error message being displayed for Firefox users is due to the WebUSB API not being implemented by Firefox due to security concerns. This still does not justify having to use a web app to plug peripherals to a PC.
Browser auth is easier to dev and more secure because SSL is pre-established. Browsers tend to get security updates more often and have built in cert stores. Browsers are so central to an OS nowadays that path traversal is easier to set up, relative to individual apps.
If every application had to write this functionally, companies would have to redirect dev focus away from their core services and, most likely, would be shittier (for a number of reasons). It would also lead to more OS bloat.
On the other hand, if every app was a web app they'd be able to track you even better than they do now (at least regarding human interaction with the app itself); it's easy to set up an outbound block on an application that isn't a browser. On the other hand, installed apps can establish persistence. Like how Logitech does with its options software (I fucking hate this behavior btw).
I understand that they're leveraging the browser SSL for authentication. But there are ways to do that without opening another tab inside of your browser and then just leaving it there. They could handle those calls inside of an app window that loads whatever resources they need, or makes secure CURL calls, or whatever. There are a lot of ways to implement it that would result in a better UX. Yes I agree with you, they're saving time by doing it the way they're doing it. But I disagree that the UX should suffer because the business management wants the engineers want to save time. There are paths that address both issues. They may require some compromise, but the end experience for the user is superior. Maybe my ideas are dated, but I have always strongly supported the belief that user experience should be one of the highest priorities when building user interfaces. I think the problem is that we now live in a world with thoroughly entrenched tech companies, so they put UX third, knowing the user has very few options.