# Use navigator.mediaDevices.getUserMedia in chrome
**URL:** https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414
**Category:** Features
**Created:** [March 7, 2017, 9:06am UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414 "2017-03-07T09:06:34Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@garcianavalon](https://discourse.lynckia.com/u/garcianavalon)
#### Post date: [March 7, 2017, 9:06am UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414/1 "2017-03-07T09:06:34Z")
Hi there!
Right now [erizo client uses](https://github.com/lynckia/licode/blob/master/erizo_controller/erizoClient/src/Connection.js#L160) the old and deprecated navigator.getUserMedia API in Chrome browser. I’ve seen that in Mozilla browsers the new mediaDevices API [is used instead](https://github.com/lynckia/licode/blob/master/erizo_controller/erizoClient/src/Connection.js#L153)
Are there any plans to upgrade the chrome API? Would you be interested in a PR?
---
### Author:  [@Francesco\_Durighetto](https://discourse.lynckia.com/u/Francesco_Durighetto)
#### Post date: [March 7, 2017, 10:02am UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414/2 "2017-03-07T10:02:20Z")
I know there are other priority right now which requires lot of effort like the simulcast, but the topic was already discussed and we all agree that there is the need to use something like adapter.
---
### Author:  [@garcianavalon](https://discourse.lynckia.com/u/garcianavalon)
#### Post date: [March 7, 2017, 10:59am UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414/3 "2017-03-07T10:59:46Z")
Hi Francesco,
Can you point me to the previous discussion? I’m not sure what you mean by using an adapter.
I have a working erizo client that uses the mediaDevice API, I can clean it up and make a PR with it.
---
### Author:  [@Francesco\_Durighetto](https://discourse.lynckia.com/u/Francesco_Durighetto)
#### Post date: [March 7, 2017, 11:12am UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414/4 "2017-03-07T11:12:13Z")
>
>
what is adapter:
> **[webrtc/adapter](https://github.com/webrtc/adapter)**
>
> READ ONLY FORK: Shim to insulate apps from spec changes and prefix differences. Latest adapter.js release: - webrtc/adapter
---
### Author:  [@Alvaro\_Alonso](https://discourse.lynckia.com/u/Alvaro_Alonso)
#### Post date: [March 7, 2017, 3:11pm UTC](https://discourse.lynckia.com/t/use-navigator-mediadevices-getusermedia-in-chrome/414/5 "2017-03-07T15:11:54Z")
Hi @garcianavalon, if mediaDevice API offers us any advantage with respect the current one, of course the PR is welcome!
Is true that we are thinking on migrating to the adapter but this would be a mid-term change.