On Thu, Nov 25, 2010 at 9:15 AM, String <[email protected]> wrote: > I agree, that's what the rationale probably is. But it bugs me just a > bit to equate an app using geolocation with "giving their location > out". I've got a couple of apps with educational value that I now > can't offer to kids because the app has an option to use your > location. It doesn't give it out to anybody, it just uses it > internally.
If it an option, not mandatory, you could go the route of a plug-in APK that handles the location stuff. Gets the location permissions out of your main app, too, which may have some benefits. Of course, there is more headache involved with two APKs, particularly since I'm dubious about having the plug-in APK on the Market (seems to cause too much confusion amongst users, getting the plug-in and wondering why it does not work without the main app). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
