🎓 Lesson 8: Interactions, States & Widgets

Why Interactivity Matters

Think about the last time you actually learned something online versus the last time you just clicked "Next" until a course let you go. The difference is almost always interaction. When a learner does something — reveals an answer, chooses a path, drags a label into place — their brain switches from passive skim to active work. That's not a nice-to-have. Doing is how adults remember.

Up to now your course has been well-designed and responsive, but it's mostly one-directional: you present, the learner reads. This lesson adds the second half of the conversation — the learner acting, and the course responding. In the all-new Adobe Captivate All-New you build that response out of three ideas that stack neatly on top of each other:

Figure 1 — Three layers of interactivity that build on each other: states, interactions, then widgets.

States: One Object, Many Looks

A state is simply how an object looks (and behaves) in a particular situation. The same button can wear several outfits: one for resting, one for when the mouse hovers over it, one for after it's been clicked. You design each look once, and Captivate swaps between them automatically as the learner interacts. It's the difference between a flat picture of a button and something that clearly invites a click.

Here are the states you'll meet most often on buttons and interactive components:

The exact list Captivate offers can vary by component and by version — Adobe adds and renames things — so treat the table as the reliable shape and check what states your selected component actually exposes in its Visual Properties. In the mock below, notice the small state chips: those are how you switch which look you're editing.

Figure 2 — All-new Captivate (a simplified mock-up, not a real screenshot): switching a button's state chips to design each look — here the Hover state is being edited.

💡 A little goes a long way. You don't need a wild animation on every state. A button that just darkens slightly on hover and shows a checkmark once visited already feels dramatically more responsive than a flat rectangle. Restraint reads as polish.

Interactions: "On Click, Do This"

States change how one object looks. Interactions connect objects so that acting on one affects another. The everyday example — and the one you'll build today — is click-to-reveal: a learner clicks a button, and a hidden panel of content appears. Behind the scenes you've told Captivate a tiny rule: "on click of this button, show that group."

In the all-new Captivate you set this up by selecting an interactive object (like a button), opening its interaction settings, and choosing an action — commonly things like Show, Hide, Go to slide, Jump to URL, or Play/Pause media. You pick the action, then pick its target. That's the whole loop:

Figure 3 — A click-to-reveal interaction is one small rule: a trigger (On Click) plus an action (Show a target).

Read that again and notice there's no code anywhere — just a trigger and an action, chosen from menus. This is the core pattern behind most of the interactivity you'll ever build: something happens (trigger), so Captivate does something (action). Hotspots ("click the fire extinguisher to learn about it"), show/hide toggles, and buttons that jump between slides are all this same idea with different targets.

Where does the really deep logic live — the "if the learner's score is at least the passing mark, show the certificate, otherwise send them back" kind of branching? That's the territory of variables and conditional actions, which today are strongest in Captivate Classic Classic. We give them an honest tour in Lesson 18. The all-new tool keeps gaining logic features release to release, so check your current version — but for now, know that simple show/hide/jump interactions cover a huge amount of what real courses need.

Widgets & Interactive Components

Sometimes you don't want to wire an interaction from scratch — you want a familiar pattern that just works. That's what widgets (also called interactive learning components) are: pre-built, ready-to-drop interactions you customize with your own content. They save you time and give learners interface patterns they already recognize.

The exact library shifts as Adobe updates the tool, but the classics you'll reach for again and again include:

You add a widget the same way you add any component — from the toolbar, choose Components (or Interactions, depending on the release), pick the interactive component, and drop it on the slide. Then you replace the placeholder text and images with yours, and the interaction is already wired. Because these are real components, they inherit your theme (Lesson 6) and reflow responsively (Lesson 7), so they look on-brand and behave on a phone without extra fuss.

Purposeful, Not Just Busy

Here's the trap every new author falls into at least once: discovering interactions and putting them everywhere. A slide where the learner must click six mystery tiles to read one paragraph isn't engaging — it's a chore wearing a costume. Interactivity earns its place only when it does a job.

Before you add an interaction, ask one question: "What does the learner get from doing this that they wouldn't get from just reading it?" If the honest answer is "nothing," make it plain content. Good reasons to make something interactive include:

• Retrieval — a reveal that makes them predict before they see the answer
• Chunking — an accordion or tabs that hides complexity until it's needed
• Exploration — hotspots that let learners follow their own curiosity
• Practice — drag-and-drop or matching that turns knowing into doing
• Pacing — a "Next" button that keeps learners in control of their own speed

💡 Accessibility peeks in here too. Interactive elements need to work for someone using a keyboard or a screen reader, not just a mouse. Keep that in the back of your mind now; we make it a first-class, checklist-driven habit in Lesson 14.

🎯 Try It: Make It React

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

Your course just crossed a line: it now responds. You gave a button real states, wired a click-to-reveal with nothing but a trigger and an action, and met the widget library that makes richer interactions a drag-and-drop away. Just as important, you learned the discipline of asking "what's this for?" before adding a single click. That judgment is what separates a busy course from a good one.

❓ Common Questions at This Stage

🔭 Looking Ahead

In Lesson 9, you'll add another dimension entirely — media: audio narration, video, and Captivate's genuinely impressive interactive video, where questions and overlays live right on the video's timeline. You'll learn to use media so it helps learning instead of drowning it.

✅ Before the Next Lesson

• Make sure your click-to-reveal and button states work in Preview
• Write this lesson's journal prompt — the one interaction your course truly needs, and its purpose
• If you have a short audio clip or video handy, keep it nearby — you'll use one next lesson

📚 Additional Resources

• Course Glossary — every term in plain language (see State, Interaction, Widget)
• Quick-Reference Cheat Sheet — including the component/block quick list
• Adobe eLearning Community — see interactive examples other authors have built