Responsive Design
Summary
The "front-end" areas of LearningBuilder, those that make up the "Practitioner" interface, all use a mobile-friendly responsive design.
Administrative features that are frequently used by client users, such as the various review queues, use a responsive design unless there are specific technical details that have delayed the implementation.
Administrative features that are primarily used by system administrators, including most of the Workflow configuration tools, may not use a responsive design. In many cases, the complexity of the tools and/or the lack of a realistic mobile use case, have not made the responsive redesign cost effective.
Responsive Design Tracking
| Feature or Area | Responsive? | Notes |
|---|---|---|
| Front End → Login page |  Yes | |
| Front End → Assessments | Yes | |
| Front End → Registration | Yes | |
| Front End → My Account | Yes | |
| Front End → Payment System | Yes | |
| Front End → Registration | Yes | |
| Front End → Vouchers | Yes | Viewing and purchasing Vouchers are both responsive interfaces |
| Admin → Activity List |  No | |
| Admin → Activity Offerings | Yes | |
| Admin → Audit/Eligibility Queues | Mobile-first | Configuration allows administrators to control which columns appear at which screen sizes. |
| Admin → Content Management | No | |
| Admin → Edit Assessment | No | |
| Admin → Edit Learning Plan | No | |
| Admin → Edit Workflow | No | The "Edit Workflow" screen is very complex and is most frequently used by LearningBuilder analysts. |
| Admin → Members | Mobile-first | Configuration allows administrators to control which columns appear at which screen sizes. (Applies to all instances of the /wiki/spaces/DOCS/pages/517931029 framework) |
| Provider → Activity List | No | |
| Responsible Party → 3rd Party Payments | No | Server-side paging is currently incompatible with the client-side table frameworks we use for responsive design. |
| Responsible Party → Supervisee List | Yes | |
| Responsible Party → Supervisee Learning Plans | No |
"Responsive design" means that the page automatically adjusts to the size of the screen to avoid horizontal scrolling. In most cases, this means that the data that are displayed, and the capabilities offered by a given page, are the same regardless of device used to view that page.
Certain pages or features may have a "mobile first" design that specifically targets mobile use cases. For example, some of the configurable data queues have the ability to display different columns at different screen sizes so that less relevant data can be omitted from smaller screens.
Related articles