This is Niantic’s opportunity to produce Ingress as it was intended to be. They have a bigger development team this time around. They’ve made their mistakes with Ingress Classic, learned from them, and tested them out in Pokémon GO. The code base is five years old certainly they want to update things. Fix What Once Went Wrongīeing Niantic’s first game, they inevitably made some decisions during development that, given the chance, they’d do differently today.

For example, instead of building GPS improvements or anti-cheating code for one game or the other, Niantic can build them into the core AR engine, and both games benefit. This means that some improvements will benefit both games without duplication of labor. This update allows Niantic to unify code that is common between Ingress and Pokémon GO. This allows it to continue to grow as mobile technology advances. The Ingress Prime client is essentially a complete re-write on the Unity platform, like Pokémon GO. Niantic had a problem: Ingress would not be able to continue to evolve with mobile platforms while built on dead tech. Two months after the acquisition announcement, Microsoft discontinued RoboVM. Xamarin’s Mono C♯ compiler and related technologies interested Microsoft, but the Java tech… not so much. Xamarin acquired RoboVM in October 2015, and Microsoft, in turn, acquired Xamarin four months later. Probably the most compelling reason for the new Ingress client is the fact that Ingress Classic is powered by RoboVM, a technology which was used to write apps in Java that could be run on Android or iOS. With all the news about the forthcoming Ingress Prime, it’s worth taking a moment to ask, “Why is Niantic creating Ingress Prime anyway? What’s wrong with the Ingress we have?” New Engine

Spyparty engine