A while back, I was at a rave (Tidal Rave). It was getting late, I wanted to get home, and I needed to let my friend know I was leaving.
Anyone who's been to a festival, carnival or any other packed crowd knows what happens to mobile coverage. It collapses. You can't make a normal call, and even a message over data struggles to get out.
I sent a Snapchat anyway. It sat there, stuck on "pending." I kept the chat open for a while, as if staring at it would push it through. It didn't.
A few minutes later, I heard a soft click and felt a little bump in my hand. The message had gone. I didn't need to look at the screen, because the sound and the vibration had already told me.
That moment is what this article is about.
This is part 2 of a four-part series on what makes digital products feel delightful. In part 1, I argued that good products go beyond looks and shape how you feel, and that much of this comes from what I called velocity and invisible mechanics. This part turns to the senses: feedback, transitions and motion that feel personal, as if the people who built the app really thought about you.
I use almost every major social app, and the best of them share a trick: they make the interface behave like a physical object. It responds to touch, it moves in ways that make sense, and it obeys something like physics. I call this sensory cohesion: sight, sound, touch and motion all telling you the same story at the same time.
It pays off in two concrete ways.
It lowers cognitive load. A sound or a vibration carries meaning without demanding your full attention. I didn't have to keep checking my phone at the rave. My hand told me the message had gone.
It makes things feel faster. When an app answers every action straight away, it feels responsive even if the work behind it is slow. Tap the heart on an Instagram post, and it fills in instantly, before the server has confirmed anything. The feedback arrives first, and the reality catches up.
Here are three ways the best apps achieve this.
1. Haptic and micro-sound feedback
Haptics are the small, crisp taps your phone makes when you scroll a picker wheel, hit the end of a list, or get an error. They turn a digital event into a physical one.
They tend to fall into three groups:
- Notification: the outcome of a task, like success, warning or failure. Think of the double tap when Apple Pay goes through, or the sharp buzz that comes with a failed Face ID attempt.
- Impact: something physical-feeling happened, like a pull-to-refresh snapping into place or a card landing where you dropped it.
- Selection: you moved through a set of values, like the tick-tick-tick of a date picker.
Games have used this for decades. In EA Sports FC 26, the PlayStation controller rumbles when you're fouled or hit the post. The DualSense goes further: its adaptive triggers stiffen as you draw a bow, so you feel the tension rather than just seeing it.
The rule of thumb is that feedback must answer something. Every haptic or sound should trace back to an action you took or an event that matters to you. Use it decoratively or at random, and it turns into noise. Users learn to ignore it, or worse, turn it off.
2. Continuity of motion
In a well-made interface, elements don't just appear and vanish. They grow out of where they came from, and they go back there.
Tap a card, and it expands into a full-screen view. Swipe down, and it shrinks back into the same thumbnail. Open an app on your iPhone, and it zooms out of its icon. Close it, and it falls back into that exact spot. You never lose track of where you are, because the interface shows you the path instead of cutting between scenes.
The principle is simple: things should leave the way they came in. If a view grew from a button, it should shrink back into that button, not fade out somewhere else.
3. Spring physics over fixed timing
Most basic animations run on a fixed clock. The transition takes 300 milliseconds whether you flick hard or nudge gently. That's why they can feel mechanical.
Spring-based animations work differently. They model a weight on a spring, so the motion picks up the speed of your finger. Flick a bottom sheet hard, and it flies up and settles with a slight overshoot. Drag it slowly, and it follows at your pace. Springs can also be interrupted: grab an element mid-animation, and it responds right away, with no waiting for the animation to finish.
You've felt this every time you've scrolled past the end of a list on iOS. The content stretches, resists, then snaps back. Nothing on screen tells you you've hit the end. Your thumb feels it.
Phones used to be flat glass: you tapped, and something changed on screen. Now they can tap you back. Dedicated haptic engines, richer sound and physics-based animation have given apps a body, and the best teams use it to tell you what's happening before you think to look.
That's what happened at Tidal Rave. In a crowd with no signal, I didn't need to see the message go through. I felt it.
See you in part 3, where we'll explore empathy at edge cases.