bowser vs ua-parser-js vs universal-user-agent vs platform vs detect-browser vs user-agent
Browser Detection Libraries Comparison
1 Year
bowserua-parser-jsuniversal-user-agentplatformdetect-browseruser-agentSimilar Packages:
What's Browser Detection Libraries?

Browser detection libraries are essential tools in web development that help identify the user's browser and its capabilities. This information can be crucial for optimizing user experience, ensuring compatibility, and implementing browser-specific features or fixes. These libraries provide developers with the ability to tailor their applications based on the environment in which they are running, enhancing functionality and user satisfaction.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
bowser15,694,3855,560-955 years agoMIT
ua-parser-js15,612,7619,5821.21 MB21a month agoAGPL-3.0-or-later
universal-user-agent11,952,223208.14 kB02 years agoISC
platform1,808,0653,233-345 years agoMIT
detect-browser1,297,27769627 kB433 years agoMIT
user-agent2,479-----
Feature Comparison: bowser vs ua-parser-js vs universal-user-agent vs platform vs detect-browser vs user-agent

Browser Detection Accuracy

  • bowser:

    Bowser provides high accuracy in detecting modern browsers and their versions, including mobile and desktop environments. It uses a well-maintained list of user-agent strings to ensure reliable results.

  • ua-parser-js:

    ua-parser-js is known for its comprehensive parsing capabilities, accurately identifying browser versions, operating systems, and device types from user-agent strings.

  • universal-user-agent:

    Universal-user-agent ensures consistent detection across client and server environments, maintaining high accuracy in identifying user agents regardless of the context.

  • platform:

    Platform excels in providing accurate detection of both browsers and operating systems, making it a versatile choice for applications that need to adapt to different environments.

  • detect-browser:

    Detect-browser offers a straightforward detection mechanism that accurately identifies major browsers but may lack detailed versioning for less common browsers.

  • user-agent:

    User-agent provides basic detection capabilities with reasonable accuracy, suitable for lightweight applications that do not require extensive details.

Library Size and Performance

  • bowser:

    Bowser is lightweight, making it ideal for performance-sensitive applications. Its small footprint ensures quick loading times and minimal impact on overall application performance.

  • ua-parser-js:

    ua-parser-js has a moderate size but offers extensive features, balancing performance with functionality for applications that require detailed user-agent analysis.

  • universal-user-agent:

    Universal-user-agent is designed to be efficient in both client and server environments, ensuring good performance without compromising on detection capabilities.

  • platform:

    Platform is slightly larger due to its comprehensive capabilities, but it remains efficient for most applications without significant performance overhead.

  • detect-browser:

    Detect-browser is also lightweight and designed for quick execution, making it suitable for applications where performance is a key concern.

  • user-agent:

    User-agent is very lightweight, making it an excellent choice for applications where minimalism and speed are priorities.

Ease of Use

  • bowser:

    Bowser features a simple API that is easy to integrate into projects, making it accessible for developers of all skill levels.

  • ua-parser-js:

    ua-parser-js has a slightly steeper learning curve due to its extensive capabilities, but it offers clear documentation to assist developers.

  • universal-user-agent:

    Universal-user-agent is designed for ease of use across different environments, providing a consistent API that simplifies integration.

  • platform:

    Platform provides a user-friendly API but may require a bit more understanding due to its broader feature set compared to simpler libraries.

  • detect-browser:

    Detect-browser is designed for simplicity, with a straightforward API that allows for quick implementation and minimal setup.

  • user-agent:

    User-agent is very easy to use, making it a great choice for developers looking for quick and simple browser detection.

Community and Support

  • bowser:

    Bowser has a strong community and is actively maintained, ensuring ongoing support and updates to keep up with browser changes.

  • ua-parser-js:

    ua-parser-js has a large user base and active contributions, ensuring robust support and frequent updates to maintain accuracy.

  • universal-user-agent:

    Universal-user-agent has a growing community, with support available through documentation and user contributions.

  • platform:

    Platform benefits from a decent community and regular updates, making it a reliable choice for ongoing projects.

  • detect-browser:

    Detect-browser has a smaller community but is still maintained, providing basic support for users.

  • user-agent:

    User-agent has limited community support, but it is straightforward enough that most users can troubleshoot common issues independently.

Extensibility

  • bowser:

    Bowser allows for easy customization and extension, enabling developers to add their own detection rules if needed.

  • ua-parser-js:

    ua-parser-js is highly extensible, allowing developers to modify or add parsing rules to suit their application's requirements.

  • universal-user-agent:

    Universal-user-agent offers extensibility features, making it adaptable for various use cases, especially in server-side applications.

  • platform:

    Platform provides some extensibility options, allowing developers to adapt its functionality to specific needs.

  • detect-browser:

    Detect-browser is not highly extensible, focusing instead on simplicity and ease of use without additional customization features.

  • user-agent:

    User-agent is not designed for extensibility, focusing on providing a simple and effective solution without customization.

How to Choose: bowser vs ua-parser-js vs universal-user-agent vs platform vs detect-browser vs user-agent
  • bowser:

    Choose Bowser if you need a lightweight and fast solution for browser detection with a focus on modern browsers. It provides detailed information about the browser version and platform, making it suitable for applications that require precise detection.

  • ua-parser-js:

    Use ua-parser-js if you need a robust and well-maintained library that offers extensive parsing capabilities for user-agent strings. It's suitable for applications that require detailed information about the user's environment.

  • universal-user-agent:

    Choose universal-user-agent for projects that need to handle user-agent strings in a universal way, especially in server-side applications. It provides a consistent API for both client and server environments.

  • platform:

    Opt for platform if you require a comprehensive library that not only detects browsers but also provides information about the operating system and device type. This is useful for applications that need to adapt to various environments.

  • detect-browser:

    Select detect-browser for a simple and straightforward API that allows for quick browser detection. It's ideal for projects where you need a minimalistic approach without the overhead of additional features.

  • user-agent:

    Select user-agent if you want a simple and effective way to parse user-agent strings without the complexity of larger libraries. It's perfect for lightweight applications that need basic detection.

README for bowser

Bowser

A small, fast and rich-API browser/platform/engine detector for both browser and node.

  • Small. Use plain ES5-version which is ~4.8kB gzipped.
  • Optimized. Use only those parsers you need — it doesn't do useless work.
  • Multi-platform. It's browser- and node-ready, so you can use it in any environment.

Don't hesitate to support the project on Github or OpenCollective if you like it ❤️ Also, contributors are always welcome!

Financial Contributors on Open Collective Build Status Greenkeeper badge Coverage Status Downloads

Contents

Overview

The library is made to help to detect what browser your user has and gives you a convenient API to filter the users somehow depending on their browsers. Check it out on this page: https://bowser-js.github.io/bowser-online/.

⚠️ Version 2.0 breaking changes ⚠️

Version 2.0 has drastically changed the API. All available methods are on the docs page.

For legacy code, check out the 1.x branch and install it through npm install bowser@1.9.4.

Use cases

First of all, require the library. This is a UMD Module, so it will work for AMD, TypeScript, ES6, and CommonJS module systems.

const Bowser = require("bowser"); // CommonJS

import * as Bowser from "bowser"; // TypeScript

import Bowser from "bowser"; // ES6 (and TypeScript with --esModuleInterop enabled)

By default, the exported version is the ES5 transpiled version, which do not include any polyfills.

In case you don't use your own babel-polyfill you may need to have pre-built bundle with all needed polyfills. So, for you it's suitable to require bowser like this: require('bowser/bundled'). As the result, you get a ES5 version of bowser with babel-polyfill bundled together.

You may need to use the source files, so they will be available in the package as well.

Browser props detection

Often we need to pick users' browser properties such as the name, the version, the rendering engine and so on. Here is an example how to do it with Bowser:

const browser = Bowser.getParser(window.navigator.userAgent);

console.log(`The current browser name is "${browser.getBrowserName()}"`);
// The current browser name is "Internet Explorer"

or

const browser = Bowser.getParser(window.navigator.userAgent);
console.log(browser.getBrowser());

// outputs
{
  name: "Internet Explorer"
  version: "11.0"
}

or

console.log(Bowser.parse(window.navigator.userAgent));

// outputs
{
  browser: {
    name: "Internet Explorer"
    version: "11.0"
  },
  os: {
    name: "Windows"
    version: "NT 6.3"
    versionName: "8.1"
  },
  platform: {
    type: "desktop"
  },
  engine: {
    name: "Trident"
    version: "7.0"
  }
}

Filtering browsers

You could want to filter some particular browsers to provide any special support for them or make any workarounds. It could look like this:

const browser = Bowser.getParser(window.navigator.userAgent);
const isValidBrowser = browser.satisfies({
  // declare browsers per OS
  windows: {
    "internet explorer": ">10",
  },
  macos: {
    safari: ">10.1"
  },

  // per platform (mobile, desktop or tablet)
  mobile: {
    safari: '>=9',
    'android browser': '>3.10'
  },

  // or in general
  chrome: "~20.1.1432",
  firefox: ">31",
  opera: ">=22",

  // also supports equality operator
  chrome: "=20.1.1432", // will match particular build only

  // and loose-equality operator
  chrome: "~20",        // will match any 20.* sub-version
  chrome: "~20.1"       // will match any 20.1.* sub-version (20.1.19 as well as 20.1.12.42-alpha.1)
});

Settings for any particular OS or platform has more priority and redefines settings of standalone browsers. Thus, you can define OS or platform specific rules and they will have more priority in the end.

More of API and possibilities you will find in the docs folder.

Browser names for .satisfies()

By default you are supposed to use the full browser name for .satisfies. But, there's a short way to define a browser using short aliases. The full list of aliases can be found in the file.

Similar Projects

  • Kong - A C# port of Bowser.

Contributors

Code Contributors

This project exists thanks to all the people who contribute. [Contribute].

Financial Contributors

Become a financial contributor and help us sustain our community. [Contribute]

Individuals

Organizations

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]

License

Licensed as MIT. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE file for more details.