在谷歌的Android API地方 - API_KEY针对个人用户
我已经通过Android的文件和相关的Android应用程序使用Places API的其他博客了。到处都是它建议使用API_KEY调用REST服务。该API_KEY是整个项目/应用程序相同的。在每天有1000个请求的限制。
I have gone through the Android documentation and other blogs related to using the Places API in an Android application. Everywhere it suggests to use the API_KEY to call the REST service. The API_KEY being the same throughout the project/application. There is a limitation of 1000 requests per day.
现在，如果我的应用程序由许多用户安装，那么请求限制将如果使用相同的密钥被大家很容易疲惫。
Now if my application is installed by many users, then the request limit will be easily exhausted if the same key is used by everyone.
会有一些方法来生成个人用户的API_KEY。但我怎么能照顾它在我的code？
There would be some way to generate the API_KEY for individual user. But how can I take care of it in my code?
您可以提升到每天100,000次请求配额如果您确认您的身份：
You can have the quota raised to 100,000 requests a day if you verify your identity:
谁已通过API控制台验证他们的身份是用户
每24小时10万个请求。信用卡是必需的
核查，通过启用控制台计费。我们问你的
信用卡纯粹以验证您的身份。您的信用卡将不
收取使用Places API而从。
Users who have verified their identity through the APIs console are allowed 100 000 requests per 24 hour period. A credit card is required for verification, by enabling billing in the console. We ask for your credit card purely to validate your identity. Your card will not be charged for use of the Places API.
您会发现这个信息，并更多，如果你去谷歌API的控制台中，选择的服务的，点击的定价的上链接的 Places API的的行。
You'll find this information and more if you go to the Google APIs Console, select Services and click on the Pricing link on the Places API line.
100,000请求一天了很多，应该足够了，除非你的应用程序是非常受欢迎的。而且我不认为创建多个用户生成多个API密钥将有可能不违反谷歌的条款和政策。
100,000 requests a day is a lot and should be sufficient unless your app is extremely popular. And I don't think that creating several user to generate several API keys will be possible without violating Google's terms and policies.