It's very important to measure your game’s power consumption because it can have a direct effect on a user’s experience playing your game. You would be really surprised how many developers still aren't doing this today.
In the previous blog, we looked at examples of FPS measured using GameBench tools and how they can be interpreted to understand the quality of a gaming session objectively. Before going into additional metrics and how we can spot good/bad gaming sessions, it's a good time to dig into some of the more complex nuances in game testing — janks and frametimes.
Both of these metrics are computed based on the frame timestamps that are stored in the web dashboard. These additional metrics are only available for Android devices for now.
In the previous blog, we looked at the definition of FPS and what tools you can use to measure it on Android and iOS devices. In this blog, we will look at examples of FPS measured using GameBench tools and how they can be interpreted to understand the quality of a gaming session objectively. Before going into additional metrics and how we can spot good/bad gaming sessions, I would like to introduce you to the typical workflow for using the tools to give you more context for the next blog.
Frame rate (also known as Frames Per Second or (FPS) is one of the best metrics you can capture to quantify the visual fluidity of a game. In most scenarios, the higher the frame rate, the better the experience for the gamer. In this blog, we will look at the definition of FPS and the best methods to retrieve frame rates for games on both Android and iOS.