I'd like to implement banner-ads in my new app and stumbled across two possibilitys of doing this.
The first one is using the Android SDK: com.google.ads.*
The second one is using Google Play Services: com.google.android.gms.ads.*
I googled a lot and read the documentation but I found no resources which state the differences between both solutions.
What is the difference between both and which one is the best if I simply want to add banner-ads in my app?
Direct to the point,
The main difference is that if you use Google Play Services one then you will use Google play service APIs. If you use other modules of Google Play like maps, location, gcm, play games then you can use com.google.android.gms.ads.* but if you don't use other Services then use com.google.ads.*
Their behavior is same...
As Selvin did not post his comment as an answer I'll answer this question by myself:
Use the Google Play Services com.google.android.gms.ads.*
Don't use the Android SDK for Ads because it is deprecated:
Deprecated. On August 1, 2014, Google Play will stop accepting new or
updated apps that use the old standalone Google Mobile Ads SDK v6.4.1
or lower. You must upgrade to the Google Play version of the Mobile
Ads SDK by then.
Google Mobile Ads SDK
Related
Google Android is making some strange updates to the API/SDK related to Play Services. They have deprecated the Drive.SCOPE_APPFOLDER option and advice developers to stop using it.
See the docs here: https://developers.google.com/drive/android/deprecation
At the same time, their most recent examples (updated 20 days ago) on how to implement Play Services Saved Games use this scope and do not offer an alternative to using it.
See it here: https://github.com/playgameservices/android-basic-samples/blob/bd72ba919a8a840dec33e83def5e366816367a42/CollectAllTheStars2/src/main/java/com/google/example/games/catt2/MainActivity.java#L310
What we as developers using the Play Services Saved Games API should do to replace this scope?
And what the heck is happening with the Google Play Services ecosystem in recent years?
Things that just work are changed to confuse, not work, or be more complicated than previous versions (i.e. the new Saved Games API).
Direct answer is DriveScopes.DRIVE_APPDATA (com.google.apis:google-api-services-drive:v3-rev197-1.25.0).
GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_GAMES_SIGN_IN)
.requestScopes(Scope(DriveScopes.DRIVE_APPDATA))
.build()
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 have the legacy application which actively use "com.google.android.gms.location.LocationClient" but in the new GooglePlayServices version there is no such class!! https://developer.android.com/google/play-services/index.html "...If you were previously using LocationClient, call the APIs in the com.google.android.gms.location package instead..." said there.
As I understand there is no option to force an old version of Google Play Services with custom application on the device, am I wrong?
Does it mean that I should rewrite some portion of application?
Is there any method to run app with old version of Google Play Services library on the device?
All Google Play Services are backward compatible - as long as you compile with Google Play Services 6.1 or below, you can continue to use LocationClient.
However, that does mean you will not get any of the new APIs, performance improvements, or other features available only in the newer versions of Google Play services so you should definitely consider moving over to the new API as soon as possible.
I am considering using Xamarin.Android and MvvmCross on an enterprise device that does not have Google Play Services or any other Google apps/services (i.e. Google Maps).
Does MvvmCross have any dependencies on Google Play Services or other Google apps/services that may not exist on an enterprise device?
No. The only time you would need to install the Google Play Services component is if you use a feature like Maps, Cloud Messaging, or In-app purchases.
MvvmCross is very modular and you include only the features you need primarily via plugins.
As mentioned by #Kiliman, MvvmCross has no dependencies on Google Play.
To get you started here are two good links:
1) Writing a first App
2) Video on using MvvmCross and Android (iOS and Windows as well)
I have a DfpAdView that I'm using according to the documentation here:
https://developers.google.com/mobile-ads-sdk/docs/dfp/fundamentals#android
I've been using the GoogleAdMobAdsSdk-6.4.1. I just updated Google Play Services to version 13, and it seems that the AdMob SDK has been integrated into Google Play Services in this version. However, DFP is not supported as mentioned here:
https://developer.android.com/google/play-services/ads.html
Note: The SDK doesn’t currently support DFP, Ad Exchange or Search Ads for Mobile Apps but support is coming soon.
I have to use GooglePlayServices for the Maps SDK, but it breaks the required DFP ad that I'm using. Do I need to remove the DFP ad in favor of something else, or do I change the build order so that the AdMob jar takes precedence over the GPS library where package/class names conflict (is that possible?)
The best solution for now (if you are using DFP and one of the other Google Play services) is to excise the Admob classes from the Google Play Services library and use the Admob-6.4.1 SDK.
Not ideal, but I suspect DFP support will be delivered soon.
Alternate is t hold off on upgrading to the new GPS library until DFP support is available. Depends on your urgency.