Feedback is a tool, not decoration
When you tap something in the physical world, you feel it move, hear it click, or see it change. Apps have to recreate that confirmation on a flat piece of glass. Small animations, short vibrations and quiet sounds can do this well. They tell people their action was received, show where something went, and make an interface feel responsive.
The problem starts when feedback becomes an end in itself. An app where every tap triggers a bounce, a buzz and a chime quickly becomes tiring. A useful test for any effect is to ask what information it carries. If the answer is “none, it just looks lively,” it is a candidate for removal.
Animation
What animation does well
Motion can explain relationships. A screen sliding in from the right suggests that you moved deeper into the app, and sliding back out suggests you returned. A card that shrinks toward a tab bar icon shows where it went. A loading spinner or progress bar reassures people the app has not frozen. In each case, the motion answers a question the person might otherwise have.
Keep it short and purposeful
Animations that run for too long make an app feel slow, even when it is not. Short transitions, often a fraction of a second, are generally enough. Avoid animations that block interaction, so that people can tap again before the effect finishes. Never make people sit through a decorative animation every time they perform a routine action, since what is charming the first time is irritating the fiftieth. This is part of what makes an app feel fast, a quality discussed under app performance.
Respect reduced motion
Some people feel dizzy or uncomfortable with large movements, zooming, or parallax scrolling. Phones offer a setting to reduce motion, and apps should honor it. Replace sliding and scaling with simple fades or instant changes, and make sure the interface still communicates what happened without the movement. Treating this as part of respecting display settings keeps your app comfortable for more people.
Haptics
Haptic feedback means small vibrations from the phone, and a well-tuned one can feel like a physical button. It works best for brief confirmations: toggling a switch, reaching the end of a picker, completing a payment step or snapping an item into place.
Some cautions apply.
- Use a small vocabulary. Different patterns should mean different things, and too many become noise.
- Do not vibrate for routine taps. Constant buzzing is tiring and drains the battery slightly more, which is relevant to battery drain.
- Remember that haptics are not guaranteed. Devices vary, and many people turn them off, so no important information should be conveyed by vibration alone.
- Avoid alarming patterns for minor events. A strong buzz suggests something urgent.
Sound
Sound is the most intrusive kind of feedback because it affects people around the user too. Phones are used on trains, in meetings, in bed beside a sleeping partner and in classrooms. Many people keep their phones silent, so sound should never be the only way to learn something.
If your app plays sounds, consider these points.
- Follow the device’s silent and volume settings without exception.
- Do not start audio automatically when the app opens.
- Offer a clear way to mute sounds inside the app.
- Keep effects short, soft and distinct from system alerts, so they are not mistaken for incoming messages.
- Provide a visual or written equivalent for anything important, including for people who are deaf or hard of hearing.
When feedback becomes pressure
Feedback can also be used to hold attention. Celebratory sounds, confetti, flashing lights and escalating vibrations after a small action can create a feeling of reward that encourages people to repeat it. In moderation this is harmless fun. Used heavily, particularly alongside daily streaks or random rewards, it moves from helping to nudging, and it can contribute to the kind of design people later regret.
A good question for designers is whether the feedback serves the user’s goal or the app’s desire for engagement. Restraint here connects to the broader idea of ethical app design: using the senses to inform rather than to pull.
Notifications deserve the same care. Sounds and vibrations for alerts should be tied to things people genuinely want to know, and people should have easy control over them through their notification settings.
Accessibility and sensory comfort
Some people are sensitive to flashing, strobing or rapidly repeating patterns. Avoid effects that flash more than a few times per second, and give people a way to turn off animated effects. Others rely on screen readers, which announce changes by speech, so make sure state changes are available in text as well as in motion. Many of the accessibility features built into phones already respond to these needs when apps are built to respect them.
A practical way to decide
For each effect in your app, work through these questions.
- What does this tell the user that they would not otherwise know?
- Would the interface still make sense if the effect were turned off?
- How often will someone see it? Anything repeated all day should be subtle.
- Can it be disabled, and does it respect system settings?
- Would it be acceptable in a quiet room, or at midnight?
A good habit is to build the interface without effects first, then add them one at a time, only where they fix a real confusion. Test the result by using the app yourself for a full day. Anything that bothers you by afternoon will probably bother others sooner.
Feedback that is calm, brief and optional leaves people feeling in control. Done well, it is almost invisible, which is often the sign it is working.