Mobile Game Graphics Quality Adaptation: Strategies and Implementation

Mobile games usually provide four graphics quality levels—Power Saving, Smooth, Fine, and Ultra—and need to select an appropriate default level for each device before the player can adjust settings.

Two common adaptation methods are used: a planner‑maintained configuration table that maps device identifiers (iOS device IDs or Android CPU names) to a default quality level, and programmatic matching where the game determines the quality based on GPU or CPU characteristics.

Many projects combine both approaches, using a server‑controlled switch to decide whether to read the configuration table or fall back to code‑based logic; a whitelist can force specific devices to a chosen level.

On iOS, code adaptation typically groups Apple A‑series chips into ranges, while Android groups GPUs (Qualcomm, Mali‑G) and falls back to CPU name matching when necessary. Special handling is required for devices such as Apple M‑series chips or Android devices with missing CPU information.

Testing involves covering devices listed in the table, verifying fallback logic for uncovered models, and ensuring that the default quality is applied both at login (when the RPC switch is received) and after the switch is toggled.

The combined strategy improves accuracy compared with using only a table or only code, but still requires extensive device testing and occasional manual adjustments to maintain a reasonable default quality for new hardware.