問題描述

當您在 Eclipse 中創建一個 android 項目時，您必須選擇使用哪個平臺進行編譯.您可以選擇 API 17 (Android 4.2) 或 Google API (API 17).

When you create an android project in Eclipse, you have to choose which platform to compile with. You can choose API 17 (Android 4.2) or Google APIs (API 17).

據我了解，Google API 是 API 17 (Android 4.2)，但具有地圖庫支持和 USB 開放庫.那么如果 Google API 和 Android 一樣，但功能更多……為什么不每次都選擇它呢?

From my understanding, Google APIs is API 17 (Android 4.2), but has the maps library support and usb open library. So if Google APIs is the same as Android, but with more features... why wouldn't you choose it everytime?

Google API 有缺點嗎?我看到的每個在線教程，他們都使用 API 17(非 Google API).我一直很好奇為什么他們手動將其更改為那個，而不是只使用其中包含更多內容的那個.

Is there a downside to Google APIs? Every tutorial online I see, they use API 17 (Non Google APIs). I'm always curious as to why they manually change it to that instead of just using the one that has more in it.

推薦答案

當您使用 Google API 運行時，您的應用將構建為在已安裝 Google 服務(地圖、USB 等)的設備上運行.如果您絕對需要這些服務，則應針對 Google API 構建，但您的應用將無法在未經 Google 認證的設備上運行(即未安裝 Google Play).

When you run with Google APIs, your app is built to run on a device which has the Google services installed on it already (Maps, USB etc). If you absolutely require these services, you should build against Google APIs, but then your app will not run on device which aren't certified by Google (that is, don't have Google Play installed).

如果您確實想在沒有 Google Play 的設備上運行，并且您的應用不需要任何 Google 服務 100% 存在，那么您應該針對普通的 Android API 進行編譯.

If you do want to run on device without Google Play, and your app does not require any of the Google Services to be 100% present, then you should compile against the normal Android APIs.

請參閱此文檔了解更多關于 Google 對認證設備的期望.

See this document for a bit more on what Google expects from certified devices.

這篇關于為什么在 Eclipse 的 SDK 中選擇 Android API 而不是 Google API?的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！