Using Native Browsers in Your Test

This article applies to: UserTesting 

On this page:

• In-app browser
• About native browsers
• Enable native browsers

In-app browser 

• 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

About native browsers

• Native browser refers to Safari (iOS), Chrome (Android), or the default browser on the contributor's phone.
• Use this setting if there’s an issue with the in-app browser and your website.
• Contributor view is unavailable when native browser is enabled.
• If issues persist even with native browsers enabled, it may indicate a problem with the website or prototype settings.
• If you need to update this setting on an already launched test, you'll need to create a copy of it and relaunch a new study.

Note: 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. 

Enable native browsers 

• In rare instances, you might notice that a prototype or website looks slightly different in our browser compared to 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.
  

Related content