Designing a Rise Course that's *actually* Mobile-Friendly

This Behind the Build is less about adding a flashy effect and more about making better design calls for a very real constraint. A learner opening training on a phone may be standing on the job, short on time, and scanning for the next correct step.

Behind the Build: Design a Mobile-Friendly Rise Course with Me!

Start with an honest mobile check#

Here’s the uncomfortable question from the video:

“When you’re designing in Rise, how often do you actually check the mobile view?”

For a lot of us, the answer is: not often enough.

Rise courses are responsive by default, which is helpful. But responsive doesn’t automatically mean comfortable. A layout can collapse onto a phone screen and still be too long, too dense, too image-heavy, or too hard to scan under pressure.

Before redesigning anything, ask the practical project question first:

1. Who is actually taking this course?
2. Are they expected to use it on desktop, tablet, or mobile?
3. Is mobile a primary use case or just a backup?
4. Are they learning something new, or referencing steps in the moment?

That distinction matters. If your client and audience are truly desktop-first, you don’t need to feel guilty for prioritizing desktop. But if people may be opening the course from a phone while working, mobile deserves to drive the design.

Pick a realistic mobile use case#

First, let’s consider what types of jobs might need mobile-ready training:

• Healthcare staff
• Nurses, doctors, and EMTs
• Technicians
• Electricians
• Retail employees
• Cashiers and store managers
• Construction workers
• Delivery workers
• Sales teams

For the concept in the video, the chosen direction was healthcare: an emergency response guide for healthcare staff.

That immediately changed the design priorities. This can’t be a leisurely course someone takes with coffee at a desk. It needs to be:

• Fast to scan
• Step-based
• Usable under stress

Those three points became the north star for the whole Rise course. If a design choice doesn’t support one of them, it probably needs to go.

Design for scanning, not studying#

When someone is using a phone for training, it may not be their preference. They may be opening the course because they need a quick answer, a reminder, or a process check.

That means the writing and layout need to work differently than a desktop course.

Use these constraints as your checklist:

1. Keep text concise.
2. Avoid run-on paragraphs.
3. Use short, clear chunks.
4. Pull key numbers, warnings, or actions into stronger hierarchy.
5. Use list form when the content is procedural.
6. Cut decorative extras that don’t support the task.

The “less fluff” part can sting a little, especially if you enjoy adding images, transitions, and small visual embellishments (like us!). But on mobile, decorative content can quickly become friction.

A good test is to ask:

Is this image or visual treatment helping someone act faster, or is it just making them scroll more?

If the learner is moving through steps in a process, scrolling may be necessary. If they’re scrolling through a long gallery because a desktop layout stacked awkwardly on mobile, that’s a different story.

Be picky about interactions#

Rise gives you plenty of ways to present content, but not every interaction feels the same on a phone. For a mobile-first course, the interaction choice should serve the learner’s context.

As you plan your lessons and blocks, look for patterns that stay clean when narrowed to a phone screen:

• Short checklists
• Color-coded sections
• Minimal text blocks
• Step-by-step sequences
• Key stats or actions with strong hierarchy

Be more cautious with interactions that create extra tapping, hidden information, or long stacked content on mobile. Hidden information is not automatically bad, but in an emergency-response-style guide, the learner may not have patience for hunting.

This is also a good reason to use Rise’s preview function intentionally while you build. Don’t wait until the course is done to check mobile. Preview early, then preview again after any section where you’ve used larger text, multiple images, or a more complex interaction.

Watch your headings on small screens#

Large headings can look beautiful on a desktop. But on mobile, oversized heading text can collapse into awkward line breaks:

• Too many short lines
• Words stacked one after another
• Headings that take over the whole screen
• Reduced readability right where you wanted emphasis

For this build, responsive text is one of the explicit design considerations. The goal is still to make important information stand out, but not at the cost of clarity.

A practical approach:

1. Write the heading in plain language first.
2. Preview it on mobile.
3. If it breaks badly, shorten it before styling around it.
4. Save the bold visual emphasis for the most important words, numbers, or steps.

Mobile-friendly design often rewards restraint. A slightly smaller, cleaner heading can be more effective than a dramatic one that turns into a puzzle on a phone.

Choose a calmer visual direction#

The first visual research pass looked at EMT and emergency response imagery. As expected, a lot of it was intense: red and blue palettes, emergency lights, action-heavy photography, and high-stress scenes.

That may be accurate to the field, but accuracy is not the only design goal. If the course is meant to support people in stressful moments, the visuals should not add more stress.

So, the design direction shifted:

• Reduce bright, high-contrast emergency red
• Lean into calmer blues and greens
• Use confident, grounded portraits of healthcare workers
• Be mindful with photography and decorative elements
• Avoid imagery that makes the experience feel more chaotic

This is a great reminder for any Rise build: visual inspiration should be filtered through the learner’s emotional context.

A dramatic image may look impressive on a mood board, but if it makes the page feel urgent, noisy, or heavy, it may work against the learning goal.

Use inspiration, but keep the board focused#

We love to create moodboards in FigJam, using sites like Pinterest as a quick source for visual direction. But when it comes to mobile-first courses, try not to go overboard. For this build, we limited our design inspo to three images.

That’s a useful constraint for tight timelines. You don’t always need a giant moodboard. Sometimes you need just enough direction to make consistent decisions.

In this case, one early image stood out because it had:

• Strong contrast
• Calming blues and greens
• A background treatment that felt interesting
• A slightly psychedelic feeling

But that last point raised a useful caution. A psychedelic or spinning visual style might communicate chaos, but for healthcare staff under stress, it could also amplify the wrong feeling.

The design question became: how do we capture energy and clarity without making the learner’s world feel like it’s spinning?

That’s the kind of judgment call that makes a mobile-first Rise course feel designed, not just resized.

Don’t abandon desktop completely#

Even with a mobile-first goal, the desktop version still matters.

The build’s priority is mobile, but the course should still look polished and usable on desktop. That’s a practical best practice, especially when you don’t fully control how learners will access the course after launch.

The trick is to avoid designing something that only works in one direction. If your mobile version is clean, concise, and well-organized, the desktop version usually benefits too. You may have a little more breathing room on larger screens, but the same content discipline still helps.

A simple mobile-first Rise planning checklist#

As you build your next mobile-friendly Rise lesson, use this quick checklist:

1. Define whether mobile is primary, secondary, or unlikely.
2. Name the learner’s real context: on the job; under stress; between tasks; or at a desk.
3. Write the course priority in one sentence, like “fast to scan, step-based, usable under stress.”
4. Cut long paragraphs.
5. Choose blocks and interactions that minimize hunting and unnecessary tapping.
6. Preview headings and key sections on mobile early.
7. Question every decorative image: does it help, or does it add unnecessary scroll?
8. Keep the desktop view clean, even if mobile is the main focus.

Mobile-friendly Rise design is not about making a smaller desktop course. It’s about meeting your learners where they are.

For your next Rise build, challenge yourself to pick one lesson and design it to be mobile-first from the start. Keep the text short, the steps obvious, and the visual design calm enough to support the task at hand.