According to the chart in TFA, charges apply to the web based Maps API. Android has a separate API, even if in the end the API's are based on the same base map data. A few things to consider on Android: - There's the element of handset manufacturers that went through the exercise of going under the umbrella of Google Experience. There are certain expectations there I am sure, including the ability to leverage no-charge apps into handset sales. No more of these, if devs face charges as users merrily zoom around in their subclasses of MapView... - There's the element that the Google Maps app for Android has developed beyond the capabilities of the corresponding API. With the introduction of usage charges, the expectation at the end of devs would be that the Maps API was going to be brought up to and maintained at the level of the user experience that the Google Maps app offers, 3D effects and all. Not that we'd have any choice, unless we could go with OSM, come to think of it.
Switching topics... Aside from that, you probably should soldier on with the Maps API approach. In general, iframing maps (as your corporate hacks envisions as far as I can tell) is, or is expected to be a thing of the past, both on Bing as well as Google Maps. On Oct 27, 11:53 am, Mike Wolfson <mwolf...@gmail.com> wrote: > So anyone know how this effects Android? > > I just started using Android Maps, after fighting a battle with corporate > (who wanted to use Bing Maps in a WebView, Ugh). Google Maps being free > was a big selling point. > > Just wondering if they are planning on enforcing this on Android as well? -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to android-discuss@googlegroups.com. To unsubscribe from this group, send email to android-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
