· 4 min read
Tuning what you feel
Latency, haptics and the weight of a transition: the details people never mention and always notice.
Ask someone why they prefer one app to another and they will usually talk about features. Watch them use both and a different story appears. They hesitate less in one. They trust its gestures. It seems to keep up with them. Most of that is feel, and feel is made of details too small to see one at a time.
Latency is the first material
A response that arrives within about a tenth of a second reads as instant; much beyond that, people start to notice the wait. Direct manipulation is stricter still. When a finger drags something across the screen, every frame counts: at 60 frames a second the budget is about 16.7 milliseconds, and on a 120Hz display it is closer to 8. Miss it and the content trails behind the finger, which is the quickest way to make software feel cheap.
So we treat latency as a design material rather than an engineering afterthought. Slow work moves off the main thread. Interfaces respond straight away and reconcile afterwards. Heavy layouts are measured on the slowest device we support, not the fastest one on the desk.
Motion with weight
Animation is not decoration; it explains what just happened. A sheet that rises from the bottom tells you where it went when it leaves. We prefer springs to fixed curves because springs can be interrupted: catch something mid-flight and it carries its momentum into your hand instead of finishing a canned move first. And we keep it short. Anything a person waits on more than once a day should be quick enough to forget.
Haptics, sparingly
A well-placed tap from the haptic engine confirms what the eye might miss: a toggle landing, a threshold crossed, a list settling into place. Used everywhere, haptics turn into noise. We use them where they carry information, match their strength to the moment, and stay within the platform’s own vocabulary so they mean what people already expect.
How we check
Feel cannot be reviewed in a screenshot. We test on real hardware, in the hand, at a normal pace and at an impatient one, and we watch other people use it. If someone has to think about an interaction, it isn’t finished.
The name of the studio is a reminder of this. People touch software long before they think about it, and what they feel is what stays with them.