Mark M. |
how can I help you today?
|
David Z. |
HI Mark, I've been developing an app that validates if the user is inside certain location, I have used polygon options and followed your chapter on Mapping with Maps V2 to develop de app. What I am not sure about is if is really necessary to update my app to use the Fused Location provider. I'm currently using the one you use in the chapter and I'm making all kinds of validations to see of the user has Google Play Services an has location enabled in the phone, I'm also using Google Maps util library to see if the user is inside the polygon I created in the map
|
Mark M. |
well, Maps V2 uses the fused location provider under the covers
|
Mark M. |
IIRC, their APIs to tell you the user's location were deprecated, as Google would prefer that you use the fused location APIs directly
|
Mark M. |
but, it's been a while since I poked around this area of Maps V2
|
David Z. |
Well, I'm not using any deprecated method to achieve the solution I'm using onLocationChanged achieve it and making the LocationManager to update the location as soon as posible
|
Mark M. |
Maps V2 itself has (or perhaps "had") ways to use the location that it used internally
|
Mark M. |
I thought that was what you were referring to
|
Mark M. |
you are certainly welcome to continue using LocationManager if you wish
|
Mark M. |
since you have already invested in getting Play Services set up (both compile-time and runtime), adding the fused location provider is easier than if you were starting from scratch
|
Mark M. |
but, if you have existing working code, and you do not feel you need the fused location provider, you should be fine
|
David Z. |
Thanks, it had been troubling me for a while! Also, I was wondering if you have a section in your book that talks about sessions, like logging in and out to an app and that stuff
|
David Z. |
Oh, ok. Well, thanks for everything
|