I want to make the device vibrate with some part of my code (not relevant), I have seen some methods for js but I can't get it to work in react. Here is what I have tried so far inside of a function:
window.navigator.vibrate(200);
navigator.vibrate([1000, 500, 1000]);
navigator.vibrate(Infinity); // Infinity is a number
Check to make sure vibrate is supported in your current browser
if ("vibrate" in navigator) {
// vibration API supported
navigator.vibrate(1000);
}
or
// enable vibration support
navigator.vibrate = navigator.vibrate || navigator.webkitVibrate || navigator.mozVibrate || navigator.msVibrate;
if (navigator.vibrate) {
// vibration API supported
navigator.vibrate(1000);
}
Related
I can detect iOS 13 on iPhone but in iPad OS 13 navigator.platform comes as MacIntel. So it is not possible to get iPad identified using below code, but it works perfectly on iPhone.
if (/iP(hone|od|ad)/.test(navigator.platform)) {
var v = (navigator.appVersion).match(/OS (\d+)_(\d+)_?(\d+)?/);
var version = [parseInt(v[1], 10), parseInt(v[2], 10), parseInt(v[3] || 0, 10)];
return version;
}
When we request for mobile website using the browser on iPad navigator.platform returns as iPad and works perfectly.
Can anyone suggest a way to identify iPad running on iOS 13 and up using Javascript?
I was able to get iPad detection working by checking for navigator.maxTouchPoints as well as navigator.platform. It's not perfect (as discussed in the comments below) but it's the best solution I've come across so far so I wanted to share.
const iPad = (userAgent.match(/(iPad)/) /* iOS pre 13 */ ||
(navigator.platform === 'MacIntel' && navigator.maxTouchPoints > 1) /* iPad OS 13 */);
TL;DR
const iPad = !!(navigator.userAgent.match(/(iPad)/)
|| (navigator.platform === "MacIntel" && typeof navigator.standalone !== "undefined"))
We can use the navigator.standalone param. It's non-standard and used only on iOS Safari at present:
Navigator.standalone
Returns a boolean indicating whether the browser is running in standalone mode. Available on Apple's iOS Safari only.
When combined with navigator.platform === "MacIntel" iPad's are the only devices that define this property, therefore typeof navigator.standalone !== "undefined" filters out Macs running Safari (touchscreen or not).
I set up a CodeSandbox and manually tested on Browserstack, seems to work as expected: https://bc89h.csb.app/
Version Detection (iOS only)
I haven't tested this too extensively but should give anyone else looking a good place to start:
const version = navigator.userAgent.match(/Version\/(\d+)\.(\d+)\.?(\d+)?/);
const major = version && version[1] ? version[1] : "";
const minor = version && version[2] ? version[2] : "";
const patch = version && version[3] ? version[3] : "";
The above takes the version and breaks it down into major, minor and patch elements. This seems to work for iOS 12 & 13 which I ran a quick test against. The above SandBox link shows the output.
You can use WURFL.js, which is free if you just want to know what device is in use: https://web.wurfl.io/#wurfl-js
Full disclosure, I'm the COO of the company behind WURFL and ImageEngine, but I'm also an open-source developer :)
WURFL.js can tell you what OS is in use and if it's an iPhone or iPad.
To use it, just add this to the head of your page:
<script type="text/javascript" src="//wurfl.io/wurfl.js"></script>
Then you can use the device information in javascript:
console.log(WURFL.complete_device_name);
Note: With the paid version you can get more accurate results (ex: Apple iPhone XS Max, Apple iPad Pro 11) as well as a many other device characteristics.
If you don't need the device information for the initial paint, you can also run this asynchronously so it doesn't block rendering. Stick it at the end of the body and use async or defer:
<script type="text/javascript">
window.addEventListener('WurflJSDetectionComplete', () => {
console.log(`Device: ${WURFL.complete_device_name}`);
});
</script>
<script type="text/javascript" src="//wurfl.io/wurfl.js" async></script>
While you're at it, you might as well use this improved device information to enhance Google Analytics: https://www.scientiamobile.com/wurfljs-google-analytics-iphone/
Note that unlike the other answers, this one requires no ongoing maintenance on the part of the developer.
It's simple - you can't. You can only use hacks like this one
let isIOS = /iPad|iPhone|iPod/.test(navigator.platform)
|| (navigator.platform === 'MacIntel' && navigator.maxTouchPoints > 1)
The first condition for "mobile", second for iPad mimicking Macintosh Safari.
It works reliably for me, but who knows what will change in the future.
If there are to be macs with touch screen, this will detect not only iPads in Desktop mode, but also regular Macs.
The other way is feature detection - you can, but probably shouldn't rely on browser features support. For example, Safari on Mac doesn't support date picker, but the mobile one does.
Anyway, I suggest you try not to rely on platform detection (which will be broken in future anyway) and use feature detection (but not to distinct platforms) as Modernizr instead - if you want to use Date picker, you can check if it is available and if it's not, use an HTML solution instead. Don't lock out users just because they use some other browser. You may notify them but give them the option to hide the notification and use your site anyway.
As a user, I hate it when someone tells me to go and use another browser
Just remember - platform detection indicates a bad code smell since all these are hacks.
I did expand the implementation a little to make use of some more default browser features on iPad OS vs Mac OS Catalina.
According to my tests on diverse iPads and all late iOS Devices this works well.
var isIPadOs = window.AuthenticatorAssertionResponse === undefined
&& window.AuthenticatorAttestationResponse === undefined
&& window.AuthenticatorResponse === undefined
&& window.Credential === undefined
&& window.CredentialsContainer === undefined
&& window.DeviceMotionEvent !== undefined
&& window.DeviceOrientationEvent !== undefined
&& navigator.maxTouchPoints === 5
&& navigator.plugins.length === 0
&& navigator.platform !== "iPhone";
Gist: https://gist.github.com/braandl/f7965f62a5fecc379476d2c055838e36
It's a bit hackish and surely not very future safe but for now we are using the following and it seems to do the trick.
The first block is just sniffing the user agent for older iPads and the the second block after 'OR' is checking if the platform is Macintosh and has touch points. At the time of writing this, there's no official touch screen for Mac yet, so it should be pretty safe for a while.
if ((/\b(iPad)\b/.test(navigator.userAgent)
&& /WebKit/.test(navigator.userAgent)
&& !window.MSStream)
|| (navigator.platform === 'MacIntel'
&& navigator.maxTouchPoints
&& navigator.maxTouchPoints === 5)
) {
return true;
}
I am using Vibration API to vibrate user device to improve UX.
navigator.vibrate(200);
The problem is it breaks my website on unsupported browsers/devices. I know I can check for vibration support before calling the vibrate method like this:
if("vibrate" in navigator) {
// vibration API supported
}
But I have already published my website, its live. I require some kind of a hack which will force unsupported browsers/devices to ignore navigator.vibrate() method where ever used.
METHOD 1
if(window.navigator && typeof window.navigator.vibrate !=='undefined')
{
//Execute your code
console.log("Vibrate API is supported by browser",window.navigator.vibrate);
}
else
{
console.log("Browser issues: Vibrate API not supported");
}
MEHTOD 2
try
{
console.log("Vibrate API is supported by browser",window.navigator.vibrate);
//Execute your code
}
catch(Err)
{
console.log("Browser issues:",Err);
}
As suggested by Keith
These 4 lines (kept in global scope) will stop unsupported browsers/devices from breaking your site.
let mainNavigator = window.navigator;
let navigator = {};
let vibrationSupport = "vibrate" in mainNavigator;
vibrationSupport ? navigator.vibrate = function(value) { mainNavigator.vibrate(value); } : navigator.vibrate = function(value) {};
I'm building a web app and I need to check if the client has a camera after the user clicks on a button.
I'm currently using this script but it seems not to work on IE.
navigator.getMedia = ( navigator.getUserMedia || // use the proper vendor prefix
navigator.webkitGetUserMedia ||
navigator.mozGetUserMedia ||
navigator.msGetUserMedia);
navigator.getMedia({video: true}, function() {
//has camera
}.bind(this), function() {
//no camera
}.bind(this));
So what's the best method?
Might be problem with:
navigator.getUserMedia();
This feature has been removed from the Web standards. Though some
browsers may still support it, it is in the process of being dropped.
Avoid using it and update existing code if possible; see the
compatibility table at the bottom of this page to guide your decision.
Be aware that this feature may cease to work at any time.
Obtained via:
MDN web docs
Try: mediaDevices.getUserMedia() as a singleton
navigator.mediaDevices.getUserMedia(constraints)
.then(function(stream) {
/* use the stream */
})
.catch(function(err) {
/* handle the error */
});
Even if it's not solution you will future-proof your code.
EDIT:
T.J. Crowder pointed out that indeed the deprecated navigator.getUserMedia(); is listed as not working in IE.
With navigator.vibrate one can make smartphones and tablets vibrate. However, the function is also available on desktop browsers, so its presence is not useful to detect whether a vibration motor is actually available.
Of course, I could check if the device is running a mobile OS for a decent approximation, but is there a proper way to detect whether vibration is actually available?
Reason: I'm using the vibration in a game, and include an on/off button for it. It makes no sense to show this button on a desktop PC.
Unfortunately, it sounds like you can't:
So apparently this is intentional, to avoid exposing accessibility
settings (which are seen as sensitive), to allow UAs to offer a
fallback, and potentially as a barrier to fingerprinting too.
From http://github.com/Modernizr/Modernizr/issues/1217
The spec itself says:
If pattern is an empty list, or if the device is unable to vibrate,
then return true and terminate these steps.
It seems impossible to detect if the device would actually vibrate somehow, so when I came to a similar problem I just used a fallback to sound if the OS seems not to be mobile device:
var navigatorTest = (function(ua){
return function(){
for(var i=0; i<arguments.length; ++i) {
if(ua.indexOf(arguments[i]) >= 0)
return true;
}
return false;
};
})(navigator.userAgent);
var bleep = ((
(navigatorTest("iPad", "iPod", "iPhone", "Android") || !navigatorTest("Macintosh", "Windows", "X11", "Linux"))
&& (navigator.vibrate || navigator.webkitVibrate || navigator.mozVibrate || navigator.msVibrate)
) || (
function(ctx){
return function(len){
var osc = ctx.createOscillator();
osc.connect(ctx.destination);
osc.start();
setTimeout(function(){
osc.stop();
}, len);
};
}
)(
window.AudioContext ? new AudioContext() : new webkitAudioContext()
)).bind(navigator, 300); // Vibration/bleep time
Although it is not what you mean (not a feature detection) it gives a fair fallback.
A client recently asked me to implement a slideshow on our website. I'm concerned that constantly animating picture transitions on the homepage will peg the processor of most mobile devices, so I want to disable the automatic advancing to preserve battery life. Is there any way to do this without trying to detect the user agent?
I've seen that there is a battery status API drafted here, but I don't know how complete it is, or which browsers have implemented it.
Actually determining battery would be quite difficult and probably involve various permissions problems.
Try just executing a small piece of code and checking the time it took. Pick a cutoff and if the code executes too slowly, turn off the transitions/animation/autoadvance. This will catch more than just battery devices; anything too slow will get the un-animated version. Degrade gracefully.
Now you can, with this API: http://davidwalsh.name/javascript-battery-api
navigator.getBattery().then(function(result) {});
Another old topic, but still relevant - I now check if the device has motion sensors, not many laptops do, but all modern smart phones and tablets do - so laptop users can live with slightly more battery use -
jQuery:
if (window.DeviceOrientationEvent) {
$(window).one("devicemotion", function(event) {
if (event.originalEvent.acceleration
&& event.originalEvent.acceleration.x !== null) { // Chrome fakes it on desktop
isMobile = true;
}
});
}
Plain Javascript:
if (window.DeviceOrientationEvent) {
window.ondevicemotion = function(event) {
if (event.acceleration
&& event.acceleration.x !== null) { // Chrome fakes it on desktop
window.ondevicemotion = null;
isMobile = true;
}
};
}