Comments on The Radioactive Yak: How to Build Location-Based Apps That Don't Suck

Pls share inhouse with the google MyTracks team. T...

2011-06-28T01:59:02.006+01:00

Pls share inhouse with the google MyTracks team. They have a decent app but need to improve their ability to identify your location. App can take 5-10 minutes to obtain GPS location. Unacceptable. The app has been flakey on gingerbread.

Hi Reto, first of all thanks very much for this po...

2011-06-25T16:53:32.869+01:00

Hi Reto,
first of all thanks very much for this post! A couple of minor things I found while going through the code, correct me if I am wrong: 1) the method "getLocationUpdateRequester" in the "PlatformSpecificImplementationFactory" class doesn't have a clause for pre-Froyo devices, and 2) the implementation for the "requestLocationUpdates" method in the "FroyoLocationUpdateRequester" class is missing (or it should extend the LegacyLocationUpdateRequester class).

Can you please please please tell me where to find...

2011-06-24T20:59:39.796+01:00

Can you please please please tell me where to find the solution to downloading all exchange folders with the android mail app that is preinstalled on phones? It gives me the option to select them.. but i cannot see the mail that is filtered into them.
Please and thanks

Nice one! I find so many apps I use just aren'...

2011-06-24T11:57:14.999+01:00

Nice one! I find so many apps I use just aren't designed for the flakey, or lack of 3G (on the tube), that London provides. It is good to see somebody addressing this :-)

Awesome Post from awesome Reto.

2011-06-24T10:14:06.195+01:00

Awesome Post from awesome Reto.

Oh, never mind me. I just noticed that you don'...

2011-06-23T23:03:22.266+01:00

Oh, never mind me. I just noticed that you don't updated bestAccuracy when you get an out of date piece of location information. It does work as you describe, sorry about that!

I think there is a bug in your code. You say, &quo...

2011-06-23T23:02:13.339+01:00

I think there is a bug in your code. You say, "If there is one or more locations available from within the allowed latency, we return the most accurate one. If not, we simply return the most recent result." But that isn't what your code does. If there is no location data recent enough, it doesn't return the most recent; it simply returns randomly one of the pieces of information it has. The problem is the "&& bestAccuracy == Float.MAX_VALUE" clause. Once a single provider is accepted, this becomes false, so later providers will be ignored if they are older than minTime, even if they are newer than the value that was previously accepted.

It's a minor bug but it seems worthwhile to be pedantic in example code. It'd be nice to see this fixed in your example and in the androdid-developers.blogspot.com posting (which is where I originally saw it).

Looking forward to reading this! First thing tomor...

2011-06-23T22:57:12.574+01:00

Looking forward to reading this! First thing tomorrow morning! :)

Score! That's a gripe of mine too, waiting for...

2011-06-23T22:55:25.807+01:00

Score! That's a gripe of mine too, waiting for Places or Maps to get my location. Glad I wasn't alone! Hah

Thanks Reto, I'm currently writing a Live Bus ...

2011-06-23T22:45:41.041+01:00

Thanks Reto, I'm currently writing a Live Bus Schedule App, and have been running into some location road blocks. Your post is very timely!

I can't wait to read your post on the Android Dev Blog, and put some of these good practices to work.

Awesome dude! :D

2011-06-23T22:43:48.304+01:00

Awesome dude! :D