Foldwren

Microinteractions: the small moments that make apps feel good

What microinteractions are, how feedback on taps, toggles and pull to refresh makes an app feel responsive, and why restraint matters.

Tap a button and it dips slightly. Flick a switch and it slides across and changes colour. Pull a list down and a little indicator turns before fresh content drops in. These are microinteractions: tiny, single purpose moments where the app responds to something you did.

Nobody downloads an app for them. But an app without them feels dead under the finger, and people notice that even when they cannot say why.

What is a microinteraction, exactly?

It is a small piece of feedback tied to one action. Most have the same anatomy:

  1. A trigger. The person taps, swipes, drags or types. Sometimes the system triggers it, such as a message arriving.
  2. A response. Something visibly, audibly or physically changes.
  3. A result. The new state stays put: the switch is on, the item is saved.

The purpose is communication. A physical button clicks when you press it. A screen is a flat sheet of glass that gives nothing back unless someone designs it to. Microinteractions replace the click.

Feedback on taps

This is the most basic kind and the most important. Every tappable thing should acknowledge a touch the instant it happens.

  • Buttons darken, lighten or shrink a fraction while pressed.
  • Icons fill in or change colour when selected, such as a heart for a favourite.
  • Submit buttons switch to a working state, then a tick when done.

Without this, people wonder whether the tap landed, and they tap again. On a "Pay now" button, that doubt is a real problem.

Phones can also give a tiny vibration, known as haptic feedback. A light tick when you flip a switch or a soft thud when you reach the end of a list makes the screen feel physical. Use it for a few meaningful moments, such as confirming a payment or a completed action. An app that buzzes at every touch is tiring.

Toggles, switches and other controls

Controls should show their state clearly and change it visibly.

A good toggle slides, changes colour and settles, all in a fraction of a second. The movement tells you which way it went. The colour tells you where it is now.

Other controls benefit in the same way:

  • Checkboxes that draw their tick instead of just appearing.
  • Quantity steppers where the number visibly counts up as you tap plus.
  • Add to cart buttons where the item appears to hop into the cart icon, and the cart count ticks up.

That last one is a good example of animation doing real work. It answers "did that go in?" and "where did it go?" in one small motion.

Pull to refresh and other gestures

Pull to refresh is so familiar that people try it on almost any list. Drag down, feel a little resistance, see an indicator, let go, and new content arrives.

It works because the feedback follows the finger continuously. As you drag, the screen stretches with you. Past a certain point, something changes to show that letting go will trigger a refresh. That constant response is what makes gestures feel natural.

The same principle applies to:

  • Swiping a row to reveal "Delete" or "Archive", with the colour and icon appearing as you swipe.
  • Dragging items to reorder, where the item lifts slightly and the others shuffle aside.

One warning about gestures. They are invisible until someone finds them. Always provide a visible way to do the same thing, such as a menu or a button, and treat the gesture as a shortcut.

Why restraint matters

Here is where projects go wrong. Once a team discovers animation, it is tempting to make everything bounce, slide and sparkle. The first time, it is delightful. By the twentieth, it is in the way.

Some rules we hold to:

  • Keep it quick. Most feedback should be over in a fraction of a second. If people have to wait for an animation to finish before they can carry on, it is too long.
  • Give it a job. Each one should confirm an action, show a change of state, or explain where something went. If it does none of those, it is decoration.
  • Save celebration for real milestones. A burst of confetti after a first completed booking is charming. Confetti every time someone saves a form is not.
  • Respect motion settings. Both iPhone and Android let people ask for reduced motion, because movement on screen makes some people feel unwell. Your app should honour that with simpler fades or no animation.

Where to spend the effort

You cannot polish everything, and you should not try. Put your attention where people spend their time.

  1. The main action. The button people press most, such as "Book", "Order" or "Send". Make its pressed, working and done states feel right.
  2. Anything involving money. Clear, unhurried confirmation that a payment went through.
  3. State changes people need to trust. Toggles, saved items, sent messages.
  4. Errors. A gentle shake of a field or a clear colour change, paired with a plain message.

When reviewing a design or a test build, try each of these on a real phone and ask one question: did the app clearly tell me what just happened? If the answer is yes without anything feeling slow or showy, the microinteractions are doing their job.

Your order