Using Native Browsers in Your Test


At a Glance

Some mobile website or prototype issues can be resolved by using the native browser setting. Learn more about what you can do by using this feature in your test.

The default option for most mobile website and prototype tests is to use the UserTesting browser. This in-app browser has a few limitations such as not supporting:

  • Tabbed browsing
  • Menu options like sharing, bookmarking, etc..
  • Android browser is locked in portrait orientation
  • Deep linking to 3rd party apps

In rare cases, you may also notice that a prototype or website appears slightly different in our browser compared with other browsers.

A workaround for any of these issues is to enable native browsers in your draft so contributors can use a different browser on their phone.


A native browser refers to Safari (iOS), Chrome (Android), or the default browser on the contributors’ phone. We recommend using this setting if you notice there might be an issue with our in-app browser and your website. However, when a native browser is enabled, contributor view can not be used. If you notice the issue persists even with native browsers enabled, this might mean there’s an issue with the website or prototype settings. 

Please note that interactive path flows will not be available if you use this setting, and in iOS tests, we will no longer be able to record where contributors tap on their phone screen.  

Additionally, if you need to update this setting on an already launched test, you will need to create a copy of it and relaunch a new study.

Please provide any feedback you have on this article. Your feedback will be used to improve the article and should take no more than 5 minutes to complete. Article evaluations will remain completely confidential unless you request a follow-up. 

Was this article helpful?
0 out of 0 found this helpful