@Robbo99999 ”software” (ex: the GUI that Amir screenshotted) is separate from drivers.
In pro audio interfaces, the drivers can cause massive issues with certain DAWs (hard crashes, clock issues, straight up not being detected, and many others). These issues can also be unpredictable and can pop up at the most inconvenient times
Poor driver design can also induce huge latency which makes “tracking” (recording audio with live monitoring) essentially impossible. (Which is why I suggested round-trip latency tests for future interface reviews in my previous comment)
There was actually a prank application that was popular awhile back that would slightly delay the microphone of your phone and then play it back thru the headphone jack (best with high isolation headphones). It would effectively completely prevent someone from being able to speak. Now imagine someone needing to sing or play an instrument in time.
Latency is such a high priority in the pro audio world. Not only in hardware processing but also in driver design. Thus why you see lots of high end active monitors with a “low latency” mode which sacrifices measured performance for situations you cannot have audible latency.
Even DIRAC which corrects my desktop system induces too much latency for me (imo) to be able to accurately record instruments into my daw for example. I switch it off for tracking.
To be fair, most people on this forum use ADCs for either measurement purposes or digitization of analog media where latency is irrelevant but considering reviews from this site show up on Google for those who are using them as the intended recording device it would be a very much needed addition.