You can provide prototypes for playtests in various ways: via file upload (APK), App Store/TestFlight link, or by entering a URL (e.g., for Figma prototypes or browser game).
For URL-based tests, you can choose between:
Secure Browser: Uses an in-app browser that hides the URL bar to maintain link confidentiality. Ideal when players shouldn't easily access the URL. This guide explains its function, limits, and tips for further securing URL-based playtests.
Default Browser: Opens the URL in the player's standard device browser (Chrome, Safari). The URL is visible and copyable; suitable when confidentiality isn't a priority or standard browser features are needed.
All PlaytestCloud players operate under a strict NDA, and comprehensive security measures safeguard every playtest (learn more on our Security Page). This guide focuses on the specific technical functionality, limitations, and security considerations when using the Secure Browser or Default Browser options with prototypes or games accessed directly in a browser.
Secure Browser Functionality
The Secure Browser option keeps your game or prototype URL from being displayed within the specialized browser players use during the playtest.
Players interact with your content via an in-app browser within the PlaytestCloud application. This browser automatically opens the URL you provided when players start their playtest and does not display a URL address bar.
This prevents players from easily viewing or copying the prototype URL directly from the browser window.
Player view in a Secure Browser playtest: The test URL's content is shown, but the URL itself is hidden from the UI. Standard browser controls (reload, back/forward) are available via a hidden menu at the top.
Understanding Secure Browser limitations
While the Secure Browser effectively hides the URL from the user interface, its protection is focused at the UI level.
The Secure Browser option focuses on preventing casual viewing or copying of the URL from the interface. It is not designed to block all possible technical methods for identifying the underlying URL accessed by the application, as loading the content still requires standard network connections.
Recommended Steps for Extra Security (for URL-based tests)
For prototypes requiring security measures beyond UI concealment, consider implementing these additional steps:
Password-Protect Your Prototype. Most prototyping tools (like Figma) allow you to add password protection to shared links. This ensures that even if someone obtained the URL, they would still need the password to access the content. Check your specific tool's documentation for instructions on how to enable this feature and include the password in the in-game tasks section.
Take Down Content After Testing. Once your playtest is complete, simply disable the sharing link or remove the content from the hosted URL. This invalidates the link after the required testing period, preventing any further access.
Alternative: Moderated Playtesting
Need extra security for sensitive content? Consider Moderated playtests. You'll be on a live video call with the player as they use your game or prototype, allowing you to directly oversee the session, ensure access only happens with you present, and watch their interactions as they happen.