Hello, I am currently investigating mapping solutions for larger scale website. We also need to develop a companion app for Android that will have mapping capabilities. I have a few questions that i would like to resolve before we can decide on a direction to progress in:
1) Looking at the native map api, there seems to be functionality missing that we would need, such as finding directions between two points and geocoding. Has this functionality been intentionality missed out due to Terms of Service restrictions? or is it in the road map for future api releases? 2) We understand that we could make the app as a browser based app and use the functionality of the javascript v3 libs or even just use the web services to get the data we need to keep the app in line with the desktop version. But reading around the forums, it has been speculated that mobile apps are going to fall into rate limiting problems due to mobile providers ip masking for individual phones (ie lots of phones on one ip, as far as google maps is concerned). Does anyone know what the state of play is here? I am a little confused about the recommended direction App developers are meant to take when building Android map based apps. The options seem to be, make a native app with missing functionality / workarounds or make a browser based app that has all the functionality of the desktop version, but the interaction experience and visual quality of the app is poor in the browser compared to the native solution; any suggestions here? thanks for your time! David. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
