Geek Answers Handbook

Why did you choose the Android API through the Google API in the Eclipse SDK?

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 API (API 17).

As far as I understand, the Google API is API 17 (Android 4.2), but it has library map support and an open usb library. Therefore, if the Google API matches Android, but with a lot of features ... why don't you choose it every time?

Is there a flaw in the Google API? Every online tutorial that I see uses API 17 (not the Google API). I always wonder why they change manually, instead of just using the one that has more.

+4
source share
3 answers

When you work with the Google APIs, your application is designed to work on a device that already has Google services installed (Maps, USB, etc.). If you absolutely need these services, you should create an anti-Google API, but then your application will not work on a device that is not certified by Google (that is, Google Play is not installed).

If you want to run the device without Google Play, and your application does not require that none of the Google services is 100% present, you must compile it with the usual Android APIs.

See this document a little more about what Google expects from certified devices.

+7
source

Some of the cheap Android phones that are not certified Android phones (those that do not have Google Play) will not support apps compiled against google api. Therefore, if you do not need the functionality provided by the google api, just create against android api

+2
source

The Google API includes some additional things, such as Maps. This is optional, and some people do not want to download extra stuff. The examples use a version other than the API in case the user downloading the sample did not download the Google API.

+1
source

More articles:


All Articles