3 ms·
The 60 fps thing is super weird to me. Do people really care if their website/mobile app is 60 fps? Who are these people? The only place I could possibly imagi
by ForHackernews 12y ago
The 60 fps thing is super weird to me. Do people really care if their website/mobile app is 60 fps? Who are these people?
The only place I could possibly imagine that mattering is for fast-twitch video games, or theoretically videos (though most of those are still 24 or 30 fps).
- shawndumas 12y agoAnything that maximises engagement increases impact/growth/revenue. When apps are joy-inducing people engage with them more. Jank works against joy.
- danabramov 12y ago>The only place I could possibly imagine that mattering is for fast-twitch video games, or theoretically videos It's about scrolling and animations. In videos it 24fps is enough because you have motion blur. In fact higher frame rate makes videos seem unnatural.. >Do people really care if their website/mobile app is 60 fps? Who are these people? People who prefer native apps to webapps. Quite a lot of them actually.
- mcmillion 12y agoYes. Anything less than this becomes perceptible and starts to make the UX feel janky or sluggish. That is a huge turn-off for a lot of users, even if they can't pin down the exact cause being low framerate. And framerate in UI is a different beast compared to video. A menu animation running at 24fps feels much choppier and sluggish than a video running at 24fps.
- teamhappy 12y agoNo. The amount of fames you need depends on the distance an object moves per frame. I really don't want to argue about this so I figured I just let you experience it yourself: http://jsbin.com/qizatugepo/1/edit?js,output http://jsbin.com/qizatugepo/1/edit?js,output Frame drops are a different story entirely. The swap_control_tear extension for OpenGL takes care of that to some degree though.
- MrScruff 12y agoTypically in a mobile app I'm flick scrolling at speed through lists. So the maximum distance travelled per frame is pretty high.
- teamhappy 12y agoSame here. I was trying to point out that frames per second alone isn't a useful metric for "animation quality." Ideally, you'd want to compare the frames per second to how many pixel something moves per second (or something similar). Having said that, shooting for your monitors refresh rate isn't a bad idea — it's just that you could use those cycles (and watts) for something else. And even worse, if your app is running at 60 fps most of the time but drops to 30 fps every now and then, then it's gonna look a lot worse than the one that runs at 30 fps consistently.
- untog 12y ago60fps is more of a label than a measurement. Not 60fps, but "60fps", which translates to "as fast as native app transitions".
- mbrubeck 12y agoWhen you're manipulating things with a mouse and keyboard, maybe not. When you're directly scrolling/dragging/pressing things with your fingers on a touch screen, jank and latency and frame rate make a huge difference in how you perceive the device's response to your actions.
- jwmerrill 12y agoIf you could run at a perfectly consistent 24 fps, that would probably often be okay. But the typical failure mode is not running at a perfectly consistent lower frame rate; instead, it's variable length pauses with the tail of them being painfully long.
- d0m 12y agoValid question, not sure why you are getting down-voted. It's mostly related to the animations. I.e. scrolling, dragging. This is what makes the experience amazing. But also, it's because every time you do a costly operation, ti freezes the screen and the user loses control. This is a solved problems in so many environment, frustrating that it's not there yet while developing cordova apps.