在Android上，ANDROID_ID是恒定的设备上的用户配置文件（请参阅discussion这里）。这似乎并非是对ARC的情况，但ARC是很新的，希望这种情况将会改变。

On Android, the ANDROID_ID is constant for a user profile on a device (see discussion here). This does not appear to be the case on ARC, but ARC is very new and hopefully this will change.

另外，值得一提的 - 在问候设备标识与ARC - 是Android的序列号不可用电弧，该无线网络的MAC地址是当前不可用（是的，我已经看到人们谈论使用该器件标识），以及product模型信息不可用。

It is also worth noting - in regards to device identification with ARC - that the Android serial # is not available on ARC, that WiFi MAC address is not currently available (yes, I've seen people talk about using this for device id), and product model information is not available.

动机：我知道这是不是现在建议，但我认为很多应用程序都使用ANDROID_ID，以确定他们的服务器数据库设备

Motivation: I know it is not now recommended, but I think a lot of apps use the ANDROID_ID to identify devices in their server database.

ANDROID_ID的Andr​​oid上的行为意味着，如果用户卸载你的应用程序，然后重新安装它，你就会知道，并可能如。重新同步其数据到设备。如果用户安装的应用程序的两个应用程序，你知道他们是相同的设备（和用户配置文件）上。

The behavior of ANDROID_ID on Android means that, if a user uninstalls your app and then re-installs it, you would know and could eg. re-sync their data to the device. And if a user installs two apps of your apps, you know they are on the same device (and user profile).

推荐答案

在我的经验 - 使用ARC运行时42.4410.288.23在Chrome 41.0.2272.118米（稳定）在Windows上 - 一个新的ANDROID_ID针对每一个应用程序安装生成。

In my experience - using ARC runtime 42.4410.288.23 on Chrome 41.0.2272.118 m (stable) on Windows - a new ANDROID_ID is generated for every app install.

因此​​，举例来说，如果你卸载你的应用程序，然后重新安装它，它会看到一个新的ANDROID_ID。

So, for example, if you uninstall your app and then re-install it, it will see a new ANDROID_ID.

我应该测试这个在Chromebook上，因为这是支持部署在这个时候的唯一平台，但我没有Chromebook的可用。

I should test this on a Chromebook, since that is the only platform supported for deployment at this time, but I don't have a Chromebook available.