I am trying to integrate Youtube to my android app, where I need to upload videos to users account. From the Youtube developer it seems there are two versions to do so.
Version 3.0(Experimental)
Version 2.0
So Should I use 3.0 Version for Production Apps as it is been marked Experimental?
I would highly recommend using YouTube Data API v3. Even though it's classified as experimental, it's pretty stable and will be supported strongly. V2 will be deprecated and there will be only limited support. Most of developers are using V3.
Related
I will be developing an app that uses Google Vision API in order to scan barcode. I am successfully able to write and test the app. However, I found out that the API has to be supported for Android's ICS i.e. version 4 and above. I am using Google Play Services 8.4 version. Will I be able to use this app? I have just created a prototype of app only.
In short is there any relationship between google play services and android version? If yes where can I find it. Thanks.
you may refer to this link in order to know more regarding google play services and android versions. https://developers.google.com/android/guides/setup
Here is what I was looking for. I wanted to check if version 8.4 of google play services is available for android 2.3 or not.
I'm building a simple android app that uses Google maps api to display map and navigation. As you may know Google maps need Play services Library to run on client android phone. i want my app to run in much older android OS's(14,15,..)
Problems:
1- Clients need to install or activate Play services app.
2- then Clients have to update play services app to the latest version to use my app with google maps.
3- how to make app to run in older androids? just by specifying min sdk ?
so in order to solve first and third problem i've no idea but for the second one :
building project with older Play service dependencies may help but i dont know how to do this or even it helps or not.
it'll appreciate if guys offer any solutions !
Thank you all.
What are the recommended practices for maintaining the widest backwards compatibility of an Android app while depending on Google Play Services?
Here are the pointers I was able to aggregate concerning backwards compatibility, including those that use Google Play Services.
The Google Maps Android API uses OpenGL ES version 2 to render the map. The least Android API version that has support for this is API 8 or Android 2.2 .
Compile against the oldest version of Google Play Services that contains the APIs that you need. As further discussed in this thread, refrain from using wildcards like 5.+ because that updates to the latest play services. Instead use a widely used version like com.google.android.gms:play-services:5.0.89.
Use the V4 support library to verify and request permissions.
com.android.support:support-v4:23.0.1
You might also check some additional insight from this SO thread.
I have gone through some of the links that difference between the Google API and android API.I have not got clear explanation.Anyone Can you help me please?
Answer for your question is below
The google API includes
->Maps and other Google-specific libraries.
The Android one only includes
->core android libraries.
There is a huge set of google apis for using all google web services !
google maps
google search
google app engine
google signin
... (see google products: https://developers.google.com/products/?csw=1)
Android API is part of the Android SDK (software development kit) and is to develop android applications.
You can note that Android API may be considered as a part of google APIs because it authored by google.
Google API is for developing Google-based services such as Google Maps.
Android API is for developing Android apps.
google API:-
it uses all google specific libraries like google map,search engine,sign in.
Android API:-
it is also a part of google API.
it uses all core android libraries.
Android sdk holds Android API.
refenter link description here
I was reading this tutorial http://www.androidhive.info/2015/02/android-location-api-using-google-play-services/ and I find it amazing that this one and many others never state what versions they support.
There must be a simple list which contains what libraries are for what api versions, not just Google Play library but for everything else, from reading file paths to camera api. An example would be just the camera api 2, which is for api version 21 and above. A nice list listing all of this would be very helpful!
It's extremely time consuming tracking down all of this information.
I would say that there is one - in packages documentation you can easily filter by API number.
Official Android APIs have their API number define on official Android documentation like #sebap123 said.
Google Play Services isn't part of Android itself. It's a complimentary add-on. Google Play Services runs on Android 2.3 or higher. All new GPS APIs included in GPS will run on all these devices that have GPS(Android 2.3 or higher). Unlike new Android APIs that only run on new version of Android.
Is the Google Play Services SDK R15 available to download anywhere? The "ChromeCast SDK" was "released" Monday, according to hundreds of news sites. Those same news sites claim Android app developers are "hard at work implementing ChromeCast functionality." Is the SDK appearing in anyone's SDK Manager?
How are Android app developers implementing ChromeCast functionality when the SDK isn't available and the API has changed dramatically? The DayFrame developers supposedly already updated their app to the new API, which seems suspicious to me...
Edit - As per the announcement post, SDK15 is now available.
As per the Chromecast Android API reference:
These APIs are currently not available for development. They require Google Play services 4.2, which began rolling out to devices worldwide on February 3rd. Once the update to devices is complete, the corresponding Google Play services library (revision 15) will be available for you to begin using these APIs.
Certain developers have been given early access to the SDK directly from Google to allow early development, but general availability of SDK R15 is still to come. You can still read through the Developers Guide and the Android Sender App Development Guide and prepare your application, design, and resources appropriately, but the actually integration of the SDK and testing cannot occur until Google releases it officially after the full rollout of Google Play Services 4.2.