I have to admit, embarrassedly, that I was looking at the wrong Maps API Terms. Thanks for pointing me in the correct direction regarding Maps.
There is nothing in the Android Google Maps API Terms that says you must make your applications free that use the Maps API. So paid apps look okay, although there are some restrictions on exactly what type of apps you can develop with the Maps API (see section 8.7). There's still section 8.3 that says you can't sell the Service but I guess that means we can't sell Google's service but we can sell our applications that use the service. My original post asked about the Google AJAX APIs as well. Is there an Android equivalent to Maps for using those APIs as well? Is it even acceptable to use a Google AJAX API from Android? - dave On Nov 1, 5:27 pm, Andrei <gml...@gmail.com> wrote: > http://code.google.com/android/add-ons/google-apis/maps-api-signup.html > 5.4 says you can use it for commercial purpose > > On Nov 1, 5:14 pm, davemac <davemac...@gmail.com> wrote: > > > I've been reading the Terms of Service for the Google APIs, both Maps > > and AJAX APIs. I have questions regarding future consequences of using > > these APIs in mobile apps that get distributed, hopefully, to many > > thousands or millions of devices. > > > Both say that the services must be available for free, so I'm assuming > > that means you cannot charge a fee for an Android app that uses these > > services, unless you arrange something special with Google. Which > > appears to be Google Maps API Premier, an advanced service that uses a > > page-view-counter-based calculation to determine charges, and is not > > cheap. Which pretty much says you'd need to charge a subscription fee > > if you're going to charge at all. If you don't charge now and suddenly > > get hit with a bill from Google, your free app must remain free > > (according to Android Terms) so you're out of luck? I suppose it might > > be possible to include a Terms of Service with the application that > > says the user assumes all responsibility for any charges related to > > use of the Google APIs, but that doesn't seem likely to succeed. I > > think it would be difficult to manage. I also suppose that you could > > ask Google to block requests that use your API key until you can get a > > new version out with a fee attached. > > > Google also says they could charge for the use of the API in the > > future. This is stated specifically in the AJAX APIs doc, and > > indirectly in the Maps doc (Google can change the terms at any time). > > Since the API key that is used when calling APIs belongs to the > > Android developer, that tells me we could potentially be on the hook > > for Google charges. The Terms say that we can decide to stop using the > > APIs. Which is fairly easy when you're running a web site, much > > different when your application is deployed to thousands or millions > > of devices. Especially if you've distributed the application for free, > > and with an expiration date as required of later than October 22, > > 2033. > > > I'm nervous now about using Google APIs in Android apps and wondered > > if anyone else has thought about this. Should Google APIs be avoided? > > At least until developers have some legal protection? > > > - dave > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
