We totally do get to say that in this case. This game inherits issues that have been present in Ingress for years. Years! Ingress gets away with it most of the

We totally do get to say that in this case. This game inherits issues that have been present in Ingress for years. Years! Ingress gets away with it most of the time because it's not operating in a worst-case scenario where the backend has to suddenly scale from limited beta to millions of active users, so fewer of these bugs present. The actual architecture work underneath is poor; client code should not crash, softlock, or lose frames because of a temporary connectivity issue. But TBH, that is probably not about how much the engineering team is paid, it's about what culture they have. Nintendo's console development teams would never ship something with this many catastophic bugs. Niantic has probably decided that the way they're doing things is "industry standard" (within the context of mobile and their particular silo) and does not need substantial improvement. Edit: How poor is this code, you ask? It does not let me rename my Pokemon. A race condition occurs where it tries to pop up the Android keyboard and close it at the same time.