Tithi Mondal

Article5 min readUpdated

Micro Interactions: Using App Animation Without Hurting UX

Micro interactions explained with real app examples: button feedback, loading animation and page changes, and the cases when animation hurts users.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Micro Interactions: Using App Animation Without Hurting UX: cover illustration

A user taps "Add to cart" on a grocery app. Nothing seems to happen. She taps again. Now the cart has two packets of atta instead of one. The app did add the item the first time, but it gave no sign.

A tiny animation would have prevented this: the button changes to "Added", and the cart icon bumps once. That small response is a micro interaction. A micro interaction is a short, focused response to one user action. It tells the person what just happened.

What are micro interactions, and what are they for?

A micro interaction does one of four jobs: it confirms an action, shows that something is in progress, guides attention to a change, or makes a state clear. If a motion does none of these jobs, it is decoration.

Examples you already know:

  • A heart icon that fills with colour when you like a post.
  • A toggle switch that slides from off to on.
  • A pull-down gesture that shows a spinner while the list refreshes.
  • A field that shakes slightly when a wrong OTP is entered.
  • A tick that draws itself after a payment finishes.

Each one answers a silent question from the user: "Did that work?" Fast, clear answers make an app feel easy. Missing answers make it feel broken.

How long should an animation last?

Most interface animations feel right between 150 and 300 milliseconds. Below 100 milliseconds, the change looks like a jump. Above 400 milliseconds, the user starts to wait. These are general guidelines, and the right value depends on the size of the movement.

A rough guide:

Type of changeTypical duration
Button press, toggle, checkbox100 to 200 milliseconds
Small element appearing or fading150 to 250 milliseconds
Bottom sheet or page transition250 to 350 milliseconds
Large, full-screen change300 to 400 milliseconds at most

Make things enter slightly slower than they leave. A pop-up that appears in 250 milliseconds and disappears in 150 feels responsive. Use easing, which means the movement starts or ends gently instead of at constant speed. Your developer will know this as an easing curve, and you can name it in your handoff notes. See my Figma developer handoff checklist.

How should button feedback work?

Button feedback should tell the user three things quickly: the app received the tap, the app is working, and the result. The first response must appear within about 100 milliseconds, or the user will tap again.

A simple sequence for "Pay ₹499":

  1. On press, the button darkens slightly or shrinks a little.
  2. After the tap, the label changes to "Paying" with a small spinner, and the button cannot be tapped again.
  3. On success, a tick appears and the screen moves on.
  4. On failure, the button returns, and a message explains what to do.

I go deeper into the full set of states in button states and feedback design. For payment screens in particular, see UPI payment UX and checkout design. For button wording, see call to action button design.

What makes a good loading animation?

A good loading animation shows that progress is happening and gives some idea of what is loading. The choice depends on the wait time.

  • Under 1 second: show nothing, or a very light change. A spinner that flashes for half a second is worse than none.
  • 1 to 3 seconds: show a skeleton screen, which is a grey outline of the content that will appear. It keeps the layout steady.
  • Over 3 seconds: show a progress bar or a clear message, such as "Finding rides near you". Add a way to cancel.

For a food app on a slow 4G connection in a small town, a skeleton list of restaurant cards feels faster than a blank screen with a spinner, even if the real wait is the same. I cover more cases in empty states, loading and error screens and food delivery app UI and UX design.

When does animation hurt?

Animation hurts when it slows the user down, hides information, or strains the device. It also hurts people who are sensitive to motion. Many apps over-animate because motion looks impressive in a design presentation.

Watch for these problems:

  • Long transitions. A 700 millisecond screen change is fine once and painful the twentieth time.
  • Blocking animation. The user cannot tap until a logo animation finishes.
  • Constant motion. Looping banners, bouncing icons and moving backgrounds pull attention away from the task.
  • Heavy effects on cheap phones. Large blur, shadows and layered animation can make a low-end Android phone stutter. See designing for low-end phones and slow networks.
  • Motion that makes people feel unwell. Large parallax, spinning and zooming can cause discomfort for some people.

Phones have a setting called "reduce motion". When a user turns it on, your app should replace large movement with a simple fade or no animation. Mention this in your handoff. See accessibility in app and web design.

What should I animate, and what should I leave still?

Animate things that change state, and leave stable things still. A good test: if you remove the animation, does the user lose information? If yes, keep it. If no, you can probably remove it.

Worth animating:

  • A new item moving into a list, so the eye follows it.
  • A deleted item sliding away, with an "Undo" option.
  • A field showing an error.
  • A progress step moving forward in a multi-step flow.
  • A screen change that shows where the user came from, such as sliding in from the right.

Leave still:

  • Logos on every screen.
  • Decorative backgrounds.
  • Text that is being read.
  • Anything that repeats forever.

On a learning app, a small progress ring that fills after each lesson is a useful reward. A confetti burst after every single tap is not. I discuss progress and reward patterns in edtech app UI and UX design in India.

How do I hand off animation so developers build it correctly?

Describe each micro interaction in plain words, with a trigger, a change, a duration and an end state. A prototype video helps, but a written line removes doubt.

A good note reads like this: "Trigger: tap on Like. Change: heart fills with red and scales to 120 percent, then returns to 100 percent. Duration: 200 milliseconds. Reduce motion: fill only, no scale."

Prototype the key moments in Figma so you can feel the timing before it is built. I do this in the last stage of my process, described in mobile app design process. If you want a designer to plan the small details of your app, see mobile app design or get in touch.

Frequently asked questions

What is an example of a micro interaction?

A heart icon that fills with colour when you tap it is a common example. A toggle sliding on, or a tick drawing after payment, are others.

How long should a UI animation take?

Most small animations feel right at 150 to 300 milliseconds. Longer than 400 milliseconds usually makes users wait.

Do animations slow down an app?

They can, especially heavy effects on low-end phones. Keep animations simple, avoid large blurs, and test on a mid-range Android phone.

What is the reduce motion setting?

It is a phone setting that lets people turn off large movement on screen. Apps should respect it by using a fade or no animation instead.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.