Hacker News Reader

Comment by discardorama | Hacker News Reader

They don't cache images (of Pokestops) client-side. This has got to be one of the bigger inefficiencies of this client. Aggressive client-side caching can relieve a lot of load on the server.

View on HN

That's only on the network side. Playing the game you get a feel that the entire codebase is a cesspool.

Everyone I talk to who's also played Ingress sees history repeating itself. They've experienced the same bugs, lack of communication, shutting down services making the game better instead of improving said game and whatnot.

I really, really wish Niantic fixes its technical, management and communication problems. The game has so much potential but at this point I lost almost all hope they'll be able fully exploit it.

This was my biggest surprise when I started playing the game. There are two pokestops outside my office which were the ones I most often visited. And every single time, it had to load from scratch despite absolutely zero changes in image or information. Can't understand why they wouldn't cache that on my phone. Little things like that add up.

Well, perhaps. But presumably the images from the pokestops can also be delivered by a CDN with a simple key lookup, and can be outside all of their spatial databases and primary logic servers.

The graph they showed was of spatial queries. That's not going to be affected by lookups of images for pokestops.

Reply on news.ycombinator.com