Our Browser Detection libraries are always being improved.
Our customer-facing website: whatismybrowser.com gets used tens of thousands of times per day, often by very strange and exotic web-browsers. We record the headers of each visitor that visits our site. We group those different types of records together and then in the order of popularity, we work through the list ensuring that our browser detection libraries work with the user agents and client hints to detect them fully and properly. If they don't, then we add detection for it, create a unit test for it, tick it off the list and move to the next one.
We keep a large database of unit tests, to ensure that our detection never regresses and that any change we make doesn't accidentally impact some other aspect of detection.
Before we deploy any new detection we always make sure that all unit-tests pass 100%.
This ensures that we continue to develop the browser detector to detect the most browsers, bots and other applications possible.
Here at whatismybrowser.com, we love to monitor everything. We use Statsd, InfluxDB and Grafana to keep an eye on our server's vital statistics as well as actual performance and statistics about the API itself.
That way we can see problems as they develop and quickly move to prevent or fix them.
We have automated monitoring and alerting systems in place to make sure that everything keeps running smoothly and to let us know if there's a problem.
Our API has moved beyond just browser detection, and we continue to add new end-points, such as the Browser Version API.
If you have other ideas for related API End Points, then we'd love to hear about them.
The API is free to use and easy to set up, so why not get started right now.
Do you have a question? Get in touch! We'd love to help you.