Mobile-first training for frontliners without laptops

The L&D team builds a beautiful course in Articulate Storyline. The store manager opens it on the front-of-house tablet and the layout breaks. The frontliner gives up after the second module. Two thirds of franchise frontline workers do not have a personal work laptop, and the courses being assigned to them were built for screens those workers will never touch. Mobile-first is not a polish item — it is the difference between a 90% completion rate and a 40% one. ## What "mobile-first" actually means The term gets thrown around loosely. In the franchise context, mobile-first means three concrete things: 1. **The course renders on a phone or tablet without a layout break.** Text wraps, video scales, quiz buttons are tappable with a thumb, the back button is reachable. Not a desktop course shoved into a small viewport. 2. **The interaction model fits the device.** Drag-and-drop is fine on a tablet, frustrating on a phone. Long text answers are fine on a laptop, brutal on mobile. The course design changes for the device. 3. **The completion path is finishable in shift-length attention.** Frontliners do training in 5 to 10 minute windows between tasks. A module that requires 25 uninterrupted minutes will not get finished on a phone. It might get started ten times. If any of those is missing, the course is not mobile-first; it is desktop-with-a-mobile-CSS-pass. ## Why this is harder than it sounds Most LMS platforms were built in the 2010s for desktop e-learning. Their mobile experience is a wrapper around a course that was designed for a laptop. The course technically loads on a phone — buttons render, video plays — but the design assumes a 1280-pixel canvas, a mouse, and twenty minutes of focus. When you assign that course to a frontliner with a 6-inch screen and three minutes between customers, completion rates collapse. The L&D team blames "engagement"; the actual cause is that the platform is asking the wrong device to do the wrong thing. A platform built mobile-first inverts the assumption. The default canvas is 375 pixels wide. The default interaction is a tap. The default module length is 3 to 5 minutes. The same content displays cleanly on a desktop because the desktop view is the upgrade path, not the baseline. ## What changes in course design Mobile-first changes how courses are built: - **Text density drops.** A paragraph that reads fine on a laptop is overwhelming on a phone. Break paragraphs into 2-3 sentence blocks. - **Video clips shorten.** A 12-minute video is a wall on mobile. Cut it to three 4-minute segments with knowledge checks between. - **Quizzes become tap-friendly.** Multiple-choice with large hit areas. No matrix questions, no drag-and-drop on phones, no text inputs longer than a sentence. - **Images carry weight.** A frontliner reads less and looks more on mobile. A diagram or annotated photo communicates faster than three paragraphs. - **Module length compresses.** 3 to 5 minute modules. The frontliner finishes one between tasks, picks up the next during a break. These are not nice-to-haves. They are the design constraints that make the course finishable. ## The browser question The second mobile-first decision is no app installation. Frontliners cannot be required to install an app on their personal phone — most will not, some are not allowed by household device policy, and IT cannot push apps to BYOD devices. The only viable distribution is a browser-based course that opens from a link or QR code. Tap, train, finish. No app store, no install, no "please update your app" friction. Aristotl's training experience is entirely browser-based for this reason — no app required, mobile-first by default, the same URL works on a phone, a tablet, or a desktop. ## What to test before rollout Before rolling a new course to the network, test it on the actual devices frontliners will use: 1. The cheapest Android phone in market in your operating regions. If the course works there, it works everywhere. 2. The store-issued tablet, in landscape and portrait. 3. Browsers: Chrome, Safari, Samsung Internet. iOS Safari and Android Chrome cover ~90% of frontline traffic. 4. Both Wi-Fi and 4G. The course should not require corporate-grade bandwidth. If the test fails on any of those, the course will fail in production. Test before you rollout. ## What completion rates look like when this is right Mobile-first courses, designed for shift-length attention, browser-based, on devices the frontliner already has, hit completion rates in the 85-95% range. Mobile-shoved-desktop courses sit in the 30-50% range. The gap is not motivation. The gap is the design.

Ready to put this into practice?