Thursday, July 21, 2016

Pokemon GO observations

I've been experimenting with Pokémon GO on an iPhone 6+. It's fun to play.

* The maps are pretty darn accurate, especially the trails. I'm discovering trails I didn't know were there. 

* Considering that the developers want us to have the PoGo app open all the time, it would be nice, if we could use it to navigate our way somewhere, when we're walking. I use RunKeeper to track my walks with the dog. It records miles, geotags interesting photos I take along the way, and also connects with Lose It! to relay calories burned. Would be nice if this app could do that.

* It is unbelievably frustrating, when the game gets into a mode where it will no longer accept any kind of screen input. The only thing you can do is kill the app. This has happened a few times during each one of my walks. A related issue, is that PoGo restarts itself, after switching back from another app, probably because it needs more resources than are available, when the other app runs. It appears to be reliably repeatable, when activating the camera app, then switching back to PoGo. 

* After considerable time experimenting with Pokemon Go, it seems clear that the app doesn't know how to play well with other apps. It appears to suck up all available resources (probably memory). This causes other apps, that are attempting to run in the background, to run out of resources and fail, so that they have to restart when they are brought back to the foreground. An app like RunKeeper, that needs to capture position occasionally, is forced to stop, and can't do its tracking job, with no data. Update: A newer phone with more memory doesn't have this problem very often.