Overview
Bridge supports the latest two versions of the most popular desktop browsers for Bridge. Many users also rely on mobile devices, especially when they are enrolled in courses or programs.
Bridge engineering teams develop the Bridge platform using flexible, responsive web design. Bridge works well in the primary browsers for both iOS and Android; other browsers may not be supported across all devices. Some critical functions such as course authoring require larger screens and are supported with a minimum screen size of 1024px.
What is Limited Browser Support?
Bridge engineering will reactively address critical issues that affect the most recent version of the native browser on iOS and Android devices.
Key Terms
- Native browsers: Safari (iOS) and Browser (Android)
- Reactive: Quality assurance teams test against each fully-supported browser before every release. For mobile browsers, support teams respond to problems reported by Bridge users.
- Critical issue: An issue that makes an important feature or function unusable.
- Most recent version: If there’s a more recent version of the mobile browser and updating solves the problem, that solution will be suggested as the solution.
How quickly will qualifying mobile-browser issues be fixed?
Bridge treats qualifying mobile browser issues as bugs. Engineering teams triage these bugs by severity and resolve them on the following schedule:
| Severity | Description | Resolution Time |
|---|---|---|
| Level 1 | User can't access Bridge | Resources will be assigned immediately and work uninterrupted until the problem is solved. |
| Level 2 | Users can’t use a core feature; no workaround exists | Resources will be assigned within two hours and will work uninterrupted until the problem is solved. |
| Level 3 | Users can’t use a core feature, but a workaround exists | Resources will be assigned within two business days and will develop and deploy a fix within two full release cycles. |
| Level 4 | All other issues affecting only mobile browsers | The problem will be reviewed within five business days, assessing impact, resource availability, and development priorities. A given problem may not be fixed when the impact is minor, when the affected workflow is seldom used, or when a workaround exists. |
Caveats
Screen Size and Orientation
Devices with a minimum screen size of 1024px will give users the best user experience in Bridge. Devices can be used in either portrait or landscape mode.
Bridge Admin and Authoring Tools
The mobile experience on Bridge has been optimized for the employee view. However, mobile devices do have limitations involving some admin and authoring tools. These items include, but are not limited to, importing and exporting files, viewing and downloading reports, and course creation and authoring.
SCORM Courses with Flash Content
Flash does not work natively in mobile browsers. To view SCORM courses in a mobile device, courses need to be published in an HTML5 format.
Partners and Third-Party Tools
Many customers use third-party tools in Bridge, including LTI apps. Partner networks are encouraged to build tools that work well in mobile browsers, and any reported problems will be reported back to them. Some third-party tools will work better than others on mobile, and some may not work at all.
Bridge Perform
The Bridge Perform web application is not fully responsive at this time. Engineers are basing all new development on responsive-design best practices. This initiative will take some time to touch all parts of Bridge Perform. In the meantime, Perform features will function best when viewed on a larger screen.