If your product requires a locked user environment, for instance to prevent cheating or students copying answers from a secure test environment, Learnosity can recommend some approaches.

Secure Browser

Learnosity doesn't specifically provide a secure browser, as there are a multitude of these out in the market, but we can point towards a number of secure browsers that are in active use by our client base today, primarily:

• Respondus - https://www.respondus.com/
• Safe Exam Browser - https://www.safeexambrowser.org/

OS-specific options also exist for iOS, Windows and others.

In the above cases, there's no integration work to do here - these secure browsers are installed and used on the users' desktop or laptop computer, and function in exactly the same way as any other browser (Chrome, Firefox, etc.) but with reduced ability to copy, paste, change to another application or similar behavior. There's no work required to get Learnosity to "work" within these kind of environments, as it's simply another additional browser, and these are used in our client implementations around the world.

For other secure browsers not listed above, there should be no technical blockers, unless the secure browser specifically restricts or allowlists what JavaScript can be executed, or limits certain JavaScript functionality which we may rely on. In those cases, you may need to investigate and test to ensure that both Learnosity, and your whole end-user application outside of Learnosity, perform as expected.

Active/Focus tracking

While many of our clients ask about secure browser functionality, it's only an ideal solution for controlled hardware (test centres, for example) or similar controlled environments. In a lot of cases, for instance, in classroom scenarios, or bring your own device (BYOD) scenarios, trying to enforce secure browser usage can be problematic. As an alternative, Learnosity does offer softer event based tracking, in our live progress reporting and through event handlers on our Assessment player.

In this scenario, through live progress reporting, we can ensure that an in-classroom instructor can have visibility of whether or not their students have moved to another application or tab, or through Assessment player events, add on-page business logic to, for instance, pause when a student onfocuses, or forcibly save/submit if a student unfocuses a number of times, after a warning. These more permissive, but still powerful, ways to monitor and react to student behavior can provide a lot of the power you need to prevent cheating for more formative tests, without the inherent difficulties associated with secure browsers.