---
title: "Comment by Surya Teja Karra on \"Screen Wake Lock API In JavaScript\" | Hashnode"
description: "Please note, acc. to MDN, this is experimental technology and is majorly supported by Chrome &amp; its forks and Samsung browser. We, as developers, have a resp"
url: "https://hashnode.com/posts/screen-wake-lock-api-in-javascript/6366c18d5a89e323416255e8/comment/636795ba4eeb55c059f20313"
---

[Discussion](https://hashnode.com/posts/screen-wake-lock-api-in-javascript/6366c18d5a89e323416255e8)

Comment [Screen Wake Lock API In JavaScript](https://hashnode.com/posts/screen-wake-lock-api-in-javascript/6366c18d5a89e323416255e8)

[Surya Teja Karra](https://hashnode.com/@shanmukhateja)

[Nov 6, 2022](https://hashnode.com/posts/screen-wake-lock-api-in-javascript/6366c18d5a89e323416255e8/comment/636795ba4eeb55c059f20313)

Please note, acc. to MDN, this is _experimental technology_ and is majorly supported by Chrome & its forks and Samsung browser.

We, as developers, have a responsibility to ensure consistent experiences for our users across all supported platforms (in this case browsers). I feel like usage of this tech would hurt it.

I highly recommend providing a fallback like [NoSleep.js](https://github.com/richtr/NoSleep.js) at least for iOS & Android.

**Reference:** [dev.to/mikeesto/the-screen-wake-lock-api-51hp](https://dev.to/mikeesto/the-screen-wake-lock-api-51hp)

**MDN:** [developer.mozilla.org/en-US/docs/Web/API/WakeLock](https://developer.mozilla.org/en-US/docs/Web/API/WakeLock#browser_compatibility)
