I'm currently using Google maps API and directions API for getting routes, however there is a limitation upto 2500 requests per day. so while searching for a way, got confused after i came across this link..
Google Maps Mobile SDK for Business: Android
Can anyone please explain the difference between this sdk and google maps API..?
its basically a software development kit that makes use of the google maps api and helps you in development of apps that use those apis... if request limitation is an issue try other opensource apis like argcis or tomtom etc
In order to use the individual SDK such as map, you would require a key. That key is persistent, meaning once you have one, you can keep using that same key in your app manifest, regardless of how many copies of the same app you have.
However, there is a daily limit imposed on how much keys can be requested per day from google to prevent abuse. With that said, I don't think you would have a problem of requesting one. If it is given out for today, just wait till tomorrow and the limit would be refreshed.
As for the Enterprise version, you get more support over the normal version. The main differences is that you get the Business SDK as a static library rather than one using the Google Play Services. That is all.
Related
I was trying to debloat my system from all Google Apps, including Play Services...but I noticed something wrong about position.
Almost all gps/navigation apps use the location provided by play services, and without it, they aren't locking the position (of course).
Is there any workaround about this? And why apps do not use the so cool location Manager? It's kinda frustrating.
The reason is how Google manages Android. They do make the manual pages so they can say whatever in them to throw you to their fishing net. For example see the huge note in top of Location and Maps manual.
Note: This is a guide to the Android framework location APIs in the
package android.location. The Google Location Services API, part of
Google Play Services, provides a more powerful, high-level framework
that automates tasks such as location provider choice and power
management. Location Services also provides new features such as
activity detection that aren't available in the framework API.
Developers who are using the framework API, as well as developers who
are just now adding location-awareness to their apps, should strongly
consider using the Location Services API.
To learn more about the Location Services API, see Google Location
Services for Android.
As you can see, the developers are directed to NOT use Android framework APIs. But why you think Google does not develop Android instead? Because using Google APIs will tie you to Google so you can't live without it. It is a way of creating addiction.
In addition, this also helps Google to collect location information every time your app requests location. So basically Google feeds on your apps location data like a leech.
Google really balanced Android in a way that other companies can use the OS. But the OS will be useless unless you install Google services. It is somewhat evil perhaps (but who will notice that right?), but a win/win scenario, for Google that is.
To answer your question, no the app's which were coded to use Google API services can not function without it.
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'm working on a mobile app project that uses Google Places APIs and have some questions:
From my research in Google documentation, they allow FREE and UNLIMITED use of their Google Places API data when used by Android devices. Currently, my development team is accessing Google Places Web Services API for all API calls. For the Android devices, should I have them change to use Google Places API for Android in order to take advantage of this?
I read in Google's API policy that they may allow for caching of API data (with limitations - i.e. you must refresh every 30 days, etc) if you want to increase performance of your code and/or use in offline mode, etc. However, it says you must get their permission for caching from Google. I cannot find how or where to request this permission. Would be helpful if you can point me in the right direction with a form or a link or something.
Appreciate any help. Thanks.
Simply stated, we have a considerable number of users who noticed that "reported map problems" do not update on the Android Maps API in a timely fashion.
For example, when a missing address, new road, or any other issue is submitted via the "Report a Problem" interface on the Desktop Google Maps, is seems to update on the desktop versions and the main Google Maps application for Android quickly. However, the map database used for the 2.0 API do not seem to receive these updates for a much longer period; updates can take many days or even weeks.
Our Android application is used by Emergency first-responders who spend a great deal of time driving to locations. Due to this, they routinely find incorrect information or new road development that they would like to submit and see reflected on our application, but historically, their updates only appear on the Maps App and the Desktop Maps.
I recognize that any user submitted errors must be validated by the Google team, but it appears that the Android API maps exhibit a substantially longer lag between updates than any of the other products. We are frequently asked by our clients why this is the case, and I don't have any answer.
Is there any API hook to allow API users to report errors to maps, or is there some other protocol that would be more effective here? These users are a great resource for map updates, and it seems odd that this ability is apparently missing from the API, unless it was omitted intentionally to prevent some sort of abuse?
Also, are there any general guidelines for the update process for map data on the Android API relative to the other products? Specifically, is there a time frame that users should expect to see their updates shown on the API maps, when errors are submitted via the Desktop maps?
We've been mitigating this by allowing users to overlay their own markers for updated roads, but obviously an updated map is the preferred solution.
Thank you very much.
I have an Android geolocation application released into the market named apna ilaka.
It is using Android API level 2.1. In order to allow a user to add places I would like to display a Google map with which the user could find different locations and would be able to add place indicators and information.
Following are my questions :
Do I really need to change my Android API level to Google API level in config path?
Since my app is already in market if I upload this new apk on market will it create any issue in updating the software on user side?
You only need to update the API level of you app if you want to use any api that are higher than the currently set level.
Supporting multiple API levels can be tricky but it isn't a nightmare, check out this great post by google on this subject:
http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html
I guess you are talking about "Google API" versus "Android API"? If you need Google Maps you will need to use "Google API" as it contains the Maps libraries. Otherwise you could not use Maps classes when developing/compiling.
No, as far as I know you should not have any problems.