[null,null,["最后更新时间 (UTC)：2025-07-27。"],[],[],null,["# Device targeting for asset delivery (beta)\n\nDevice targeting lets you deliver different versions\n(e.g. resolutions, etc.) of the same asset to devices based on their\nhardware. For example, you may choose to deliver low resolution assets\nto lower end devices to improve performance, and deliver high resolution\nassets to higher end devices to improve graphic quality - all without\nincurring any increase in overall game size by only delivering the\nnecessary assets to users' devices. This builds upon the concept of\nasset packs in Play [Asset Delivery](/guide/app-bundle/asset-delivery).\nAs you'll see later, you have the power to define the group criteria (for\nnow based on RAM, specific device models, available system features, and system on chip).\n\nDevice targeting configuration file\n-----------------------------------\n\nTo get started with device targeting, create a device targeting configuration\nfile. Instructions can be found in the [documentation for device targeting](/google/play/device-targeting).\n\nUse device targeting for your asset packs\n-----------------------------------------\n\nOnce you have created your configuration file, you can subdivide your asset\npacks by device groups.\n\nThe exact steps required are different depending on whether you are building\nyour app with the Android Gradle Plugin or with the Play Unity Plugin. Before\nproceeding, select your build setup: \nAndroid Gradle Plugin Play Unity Plugin\n\nTake the **existing** asset pack\ndirectories created and post-fix the appropriate folders\n(as described below) with `#group_myCustomGroup1`, `#group_myCustomGroup2`, etc.\nWhen using the asset packs in your app, you won't need to address folders by\npostfix (in other words, the postfix is automatically stripped during the build\nprocess).\n\nAfter the previous step, this might look like: \n\n ...\n .../asset-pack-name/src/main/assets/level#group_myCustomGroup1/\n .../asset-pack-name/src/main/assets/level#group_myCustomGroup2/\n ...\n\nIn this example, you would reference `asset-pack-name/assets/level/`\nwithout any postfixes.\n\nDevices in `myCustomGroup1` will receive all the assets under\n`level#group_myCustomGroup1/`, while devices in `myCustomGroup2` will\nreceive all the assets under `level#group_myCustomGroup2/`.\n\nDevices that don't belong to either `myCustomGroup1` or `myCustomGroup2` will\nreceive an empty `asset-pack-name` pack.\n\nThis is because devices that don't match any device group will receive the\ndefault variant of your asset pack, which includes everything that is either\ninside the `level#group_other` folder or not inside any directory with a\n`#group_suffix`.\n| **Note:** If a device matches multiple groups, it will be served the content for the group that is defined first in the XML file. The order you define groups in the XML file is your priority order.\n| **Important:** It's not possible to prevent **any** variant of your asset pack from being delivered to certain devices. Non-targeted devices will always receive the default variant."]]
