Your app is not slow. It just feels slow.
There's a world between a recent iPhone on fiber Wi-Fi and a mid-range phone in the subway. Users don't judge your code…
Spotify does an enormous number of things. Playlists. Podcasts. Search. Downloads. Suggestions. Lyrics. AI. Notifications.
And yet the app often gives a very natural sense of smoothness. Why ?
Because Spotify works hard on the perception of speed. And that's a very important topic in mobile.
The user measures feeling, not performance
In reality, the user doesn't measure performance technically. They mainly measure the feeling.
For example : when someone wants to play a song, a few seconds of loading can already completely break the experience. The emotional moment disappears.
Spotify understood this perfectly. So the app preloads content, anticipates certain actions, avoids unnecessary transitions, keeps consistent navigation, drastically limits visible friction.
Result : the user moves forward almost without thinking.
The interface you forget
And often, that's exactly what creates great UX. Because an excellent interface isn't necessarily the one you notice. It's often the one you completely forget while using it.
Spotify isn't trying to impress visually every second. The app mainly tries to never break the user's rhythm.
This philosophy maps exactly to the "deference" principle in Apple's Human Interface Guidelines : the interface must step back behind the content.
Never break the rhythm
Google's Material Design guidance puts a mobile transition at around 300 ms, with smaller animations at 150-200 ms, and notes that past 400 ms a transition begins to feel slow (Material Design, 2026).
Those numbers sit on top of much older work on perception. The classic thresholds — still the standard reference — are 0.1 second, 1 second and 10 seconds : "0.1 second is about the limit for having the user feel that the system is reacting instantaneously", while "1.0 second is about the limit for the user's flow of thought to stay uninterrupted" (Nielsen, 1993, after Miller, 1968). The key difference between an app that feels fast and one that does not is usually which side of that 1-second line its common actions fall on.
Because a user doesn't come to admire your menu. They come to listen to music.
The idea sounds simple. But plenty of apps still forget it today.
Is your app breaking the user's rhythm without you knowing ? Book a 30-minute call to identify the invisible smoothness breaks in your product.
