> Niantic was founded by engineers from Google. It seems a bit ridiculous that with all the expertise and funding they have, they couldn't even provide a stable

> Niantic was founded by engineers from Google. It seems a bit ridiculous that with all the expertise and funding they have, they couldn't even provide a stable backend architecture. It's not that difficult to scale an api using Google's app engine or aws. That's like saying "they have Google engineers, therefore they must have Google funding and they should be able to smart things out." AFAIK, Ingress was built on app engine, and had huge scaling issues. > The app could at least cache some of the info of your pokemon as well as the locations of nearby stops and gyms. Then only the status of those gyms and nearby pokemon would need to be synchronized when you reopen it. It's not clear how much faster that would be. The majority of the RPC time is probably due to network latency issues, not the amount of data being fetched. That said, without slapping a profiler on it, you can't tell either way.