Is there a way to download Google Play Services SDK R15? - 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.

Related

Google play services and relation with android version

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.

How to decide on the version of google play services to use in the application when using any google play services api?

We are going to integrate Google SignIn (by replacing Google Plus Login). For Google SignIn the minimum google play services version required is 8.4. If I go by the documentation of Google, then they have mentioned using version 9.2.1. But a lot of our app users are on slow connection networks and since 9.2.1 is relatively new, it is possible that a lot of these users will not have this update installed on their devices. So my question is that for any api which requires google play services, which version to use?
1) The latest version (9.2.1 in the case of Google signin) - Google suggests to use the latest version because it has bug fixes. But again, if I use the latest version, then some of my users can miss this functionality. Here I can check the google play services version and prompt the user for update (Not sure if all the users will update).
2) Minimum version (8.4 in the case of Google signin) - Now since this is a minimum version required, more number of users will have this version installed on their devices.
So, what is the best way to decide on the version when using any of the
Google Play services api?
P.S. I understand that Google Play services update happens every few days, and most of the users will have the updated services. But my concern is for those users, who are on a slow network connection. Because I can achieve the same functionality by just using a lower version of Google Play Services.
I think it is always good to go with latest versions, but if you have any other concerns you can use the older Google Play Services.
And As far as I know Google Login com.google.android.gms:play-services-auth:8.4.0.
You can use play-services-auth:8.3.0 also with help of google-services:2.1.2,
classpath 'com.google.gms:google-services:2.1.2'
compile 'com.google.android.gms:play-services-auth:8.3.0'
But remember you need to use all other play services should compatible with google-services:2.1.2 and all dependencies should have the same version (8.3.0).

How to implement google maps with best possible backward compatibility in an android?

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.

Why is Google API 2.3 required and cannot use default Android 2.3 for USB IOIO?

The top answer to this question (ADK and Eclipse woes - com.android.future and USBAccessory?) solved my issue (in a specific case), but I wondered why I needed to use the Google API and not the default Android API for implementing a IOIO board via USB. Why does this feature exist in the Google API 2.3.3 and not Android API 2.3.3 (since the android operating system is capable of supporting it... did the Android API developers just not add some additional functionality that makes the IOIO plugin tick?), and why is it not required to use the Google API for 4.2? Is this likely specific to the IOIO interface code I am using (https://github.com/ytai/ioio/wiki/Downloads#client-software-and-ioio-application-firmware-images)?
I would like to further understand the reason behind this so that I can better predict if I encounter a similar issue in the future with other libraries.
I do not have an idea about the USB issue you've mentioned. I just want to clarify why you need to use Google APIs instead of normal Android API in some cases.
Android code is open-source which means anyone can have access to it and can compile the code to make their own android enabled devices. Most of the device manufacturer choose Google's proprietary licensed version of Android which includes some of the Google services inbuilt which are closed source and are not included in the android source code.
These services include Google Play Store, Google Maps, Gmail, Admob etc. So if you want to use any of the Google services/features(which are not included in the usual Android features), you have to use Google APIs, which have support for these features.
An actual device running on Android OS may or may not support these features, depending upon the availability of Google Services in the installed ROM (These can be installed later if you have root access). For example Nokia X series won't support any Play Store, Google map or Google gaming services feature.
I suppose this is true in your case too.
PS: The above info is from my own experience and is not supported by any of the articles mentioned anywhere. Feel free to add references in the comments if you know any article supporting the facts.

Google TV SDK for Android

Is the Google TV SDK for Android available now to download ?
Per the FAQ:
How do I get the Google TV SDK for
Android?
The Google TV SDK add-on will be freely available to developers.
Please sign-up on www.google.com/tv to stay informed about availability.
If you visit www.google.com/tv there's a "Developers" link at the top. The developers page simply says "More information coming soon" and links to a page where you can sign up to receive updates about availability.
So it appears the answer is no, you cannot currently get it.
Edit (8/23/2011): Google has released what it is referring to as a "preview version" of the Google TV SDK add-on. You can find instructions for setting up a development environment here and you can read the announcement on the Android Developers Blog.

Categories

Resources