CURRENT-DEVICE


This module makes it easy to write conditional CSS _and/or_ JavaScript based on
device operating system (iOS, Android, Blackberry, Windows, MacOs, Firefox OS, MeeGo,
AppleTV, etc), orientation (Portrait vs. Landscape), and type (Tablet vs.
Mobile).

View the Demo →

$3

This module inserts CSS classes into the element.

#### iPhone

#### Android Tablet

#### Blackberry Tablet

$3

- iOS: iPhone, iPod, iPad
- Android: Phones & Tablets
- Blackberry: Phones & Tablets
- Windows: Phones & Tablets
- Firefox OS: Phones & Tablets

$3

Just include the script. The script then updates the section with the
appropriate classes
based on the device's characteristics.

Installation

``sh
npm install current-device
`

And then import it:

`js
// using es modules
import device from "current-device";

// common.js
const device = require("current-device").default;
`

Or use script tags and globals.

`html

`

And then access it off the global like so:

`js
console.log("device.mobile() === %s", device.mobile());
`

$3

The following tables map which CSS classes are added based on device and
orientation.

#### Device CSS Class Names

#### Orientation CSS Class Names

$3

This module _also_ includes support for conditional JavaScript, allowing you to
write checks on the following device characteristics:

#### Device JavaScript Methods

#### Orientation JavaScript Methods

#### Orientation JavaScript Callback

`js
device.onChangeOrientation(newOrientation => {
console.log(New orientation is ${newOrientation});
});
`

$3

#### device.noConflict()

Run current-device in noConflict mode, returning the device variable to its
previous owner. Returns a reference to the device object.

`js
const currentDevice = device.noConflict();
`

$3

Access these properties on the device object to get the first match on that
attribute without looping through all of its getter methods.

$3

Environment detection has a high rate of misuse. Often times, folks will attempt
to work around browser feature support problems by checking for the affected
browser and doing something different in response. The preferred solution for
those kinds of problems, of course, is to check for the feature, not the browser
(ala Modernizr).

However, that common misuse of device detection doesn't mean it should never be
done. For example, current-device` could be employed to change the interface of
your web app such that it uses interaction patterns and UI elements common to
the device it's being presented on. Android devices might get a slightly
different treatment than Windows or iOS, for instance. Another valid use-case is
guiding users to different app stores depending on the device they're using.

In short, check for features when you need features, and check for the browser
when you need the browser.

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Matthew Hudson 💻 🚧

Rafael Terán 💻

Allan 👀

martinwepner 💻

This project follows the all-contributors specification. Contributions of any kind welcome!