Jun 22, 2012, 11:23:29 PM6/22/12
I have a specific question that should truly be targeted towards a
Google Maps/Latitude android development bug/enhancement tracker, but I
don't know of any such forum. If someone can point me in that
direction, I would be very grateful. To that audience, I wonder, would
it be possible to NOT disable auto check-in within the Latitude app just
because a user turns off their location reporting in settings.
Here's the issue- many android Latitude users have found a 3rd party
client app to update their Google Latitude location instead of using
Latitude detection for a number of reasons. In the essence of
preserving the 3rd party location, these users also turn off location
reporting within the Latitude app. And because of this, the auto
check-in feature will not function. Even though, Google/Latitude is
fully aware of their updated location, and fully aware of their setup to
auto check-in to such a venue. I don't see why Google would prohibit
this from just seamlessly occurring.
Would or could this be put on the plate of the 3rd party developers thru
this or another API ? I hope not, but it would be what it is...
or even, an entirely different solution to this problem. Add some
sense-able logic to the Latitude app such as: if the app reads the
current location of a Latitude user which is minutes fresh and extremely
accurate, why on earth does Latitude over-write it with a city level
1500m inaccurate location value? Users would not have to turn off Latitude detection is it wasn't so horrible. At least, minimally, don't over-write a new and accurate location value.
But that all leads to my real question....more specifically for this
audience. Where is Google Location APIs going with their whole Google
Location wave of technology? Is Latitude being thrown out for a new
Google+ version? Will Latitude be integrated with Google+ ? How will
this all shape up because I don't want anyone wasting their time
developing for this if that is the case. Thanks