Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 37 ยท Interactions and Animation

Interaction Principles: Scroll, Hover and Click

Learn the three families of web interactions, triggers, targets and states, and how Wix and Webflow expose them. Includes runnable trigger and state stand-ins.

An interaction is a cause and an effect: something happens (the trigger), and something on the page changes (the animation). Both Wix and Webflow let you build interactions visually, without writing code, but they name things differently and expose different levels of control. Before you open either editor, it helps to have one clear mental model that fits both.

This lesson gives you that model. You will learn the main trigger families, what can be animated, how states work, and when an effect helps the visitor rather than annoys them.

Wix and Webflow are hosted products. They cannot run on this site, so the editor menus are described in words and the runnable examples are small JavaScript stand-ins that mimic the ideas (triggers, states, timing). They are labelled as stand-ins every time.

The trigger, target, effect model

Every interaction has three parts:

  1. Trigger: what starts it. Examples: the page loads, an element scrolls into view, the pointer hovers, a click, a keypress, a tab change.
  2. Target: which element (or group of elements) moves.
  3. Effect: what changes: position, size, opacity, rotation, color, blur, or a class.

Webflow shows this literally in its Interactions panel: you pick a trigger (for example "Mouse hover" on an element), then build an animation for the target. In Wix, the Studio editor and the classic Editor expose the same ideas through Animations (entrance, scroll, hover, click effects) and through Interactions in Studio, where you choose a trigger and effect on an element.

Trigger families

Think of triggers in four families.

Family Typical use Notes
Load Hero text fading in Runs once; keep it short.
Scroll into view Cards that appear as you reach them Most common on landing pages.
Scroll progress Parallax, progress bars, pinned sections Ties animation to scroll position, not time.
Pointer and click Hover lift on buttons, menu open/close Hover does not exist on touch devices.

The last row matters: phones and tablets have no hover. Any information that appears only on hover must also be reachable by tap, or the touch visitor never sees it.

Time-based versus scroll-based

A time-based animation plays for a fixed duration after it is triggered, for example "fade in over 0.6 seconds". A scroll-based animation is mapped to a scroll range: at 0% of the range it is at the start, at 100% it is at the end, and scrolling back plays it in reverse. Webflow calls this "while scrolling in view" (progress mapped to the scroll). Wix offers scroll effects such as parallax, reveal and fade in its animation panel.

Choose time-based for small confirmations (a button press) and scroll-based for storytelling sections where the visitor controls the pace.

States: the idea behind hover and active

Many "interactions" are really state changes. A button has a default state, a hover state, a pressed state and a focus state. In Webflow's Style panel you can switch the element to those pseudo-states and restyle it, with no interaction object at all. A transition (duration and easing) then smooths the change. Wix does the same for buttons through the design panel's state tabs (regular, hover, disabled).

Use states and transitions for simple feedback. Reach for the Interactions panel only when you need sequences, multiple targets or scroll mapping.

Try a stand-in that models trigger, target and effect as plain data so you can see how a visual editor might store an interaction.

JS Stand-in: an interaction as data

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Touch-safe hover

Because hover is missing on touch devices, good builders treat hover as an enhancement. The next stand-in decides which interaction to use from the device capabilities.

JS Stand-in: hover or tap?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

When animation helps

Motion works when it answers a question the visitor has:

  • Where did that come from? A menu sliding from the edge explains where it lives.
  • Did that work? A button that dips slightly when pressed confirms the click.
  • What is related? Items that stagger in together look like one group.

It hurts when it delays content, moves constantly, or hides meaning. Operating systems expose a "reduce motion" setting, and both platforms let you respect it: Webflow lets you disable specific interactions on small breakpoints and for reduced-motion preferences through the interaction settings and custom CSS, and Wix lets you remove animations per breakpoint in Studio. Always test with motion switched off.

Common mistakes

  • Animating everything. When every section fades in, nothing stands out.
  • Long delays. Text that appears two seconds late feels broken, not elegant.
  • Layout-moving effects. Animating width or margin can shift other content (layout shift). Prefer opacity and transforms (see Easing and Motion Performance).
  • Hiding links behind hover with no tap alternative.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which three parts make up every interaction?

    A trigger starts the interaction, the target is the element that changes, and the effect is what changes.
  2. 2. Why should hover-only content have a tap alternative?

    Phones and tablets cannot hover, so those visitors would never see content that only appears on hover.
  3. 3. Which animation type ties progress to scroll position instead of time?

    Scroll-based animations map a scroll range to the animation progress, so scrolling back reverses them.
  4. 4. For a simple button hover color change, what is usually enough?

    States plus a transition handle simple feedback; save timelines for sequences and multiple targets.

Summary

  • An interaction is a trigger, a target and an effect.
  • Triggers fall into load, scroll into view, scroll progress and pointer/click families.
  • Use states and transitions for simple feedback; use the interaction tools for sequences.
  • Treat hover as an enhancement because touch devices cannot hover.
  • Motion should explain or confirm, never delay or distract.

Next: Webflow Interactions and Timelines