And finally, they would need to jump through all of the necessary security reviews and audits for a second time where the app was already launched.īut before any of that, they had to prove the concept. Then, they would need to rewrite the app as it was changing, because it was constantly being updated. First, they would need to retrain the team on a new language, platform, and approach to the user interface. Rebuilding Google Pay on Flutter didn’t come without its challenges. Whereas building out features on both Android and iOS required double the effort, Flutter would only require about 1.2 times as much work. While it meant a heavy upfront investment of engineering resources, it would allow the team to unify their engineering leadership, shift their work away from endlessly patching holes, and increase the speed and efficiency of their client development for faster response and implementation times.Ībove all, migrating to Flutter would enable fast, resource-efficient scaling of Google Pay around the world. The team initially tested Flutter as an Add-to-app possibility, but the opportunity to rewrite the whole app was too big to ignore. So instead, they opted to invest in a cross-platform framework that would enable them to do more with less: Flutter. That meant they would not only need to hire more iOS engineers, they would need to continue building every feature twice - once for Android, and once for iOS. To make things even more challenging, many of those new regions had a large number of iOS users, while their existing users were almost exclusively Android. But to do that, they relied on 1.7 million lines of code between their Android and iOS apps - an amount that didn’t feel sustainable as Google Pay continued to expand to new countries, each of which would require its own unique features. With 100 million users in dozens of countries, Google Pay allows users around the world to pay, save, manage expenses, and more.

Gpay for android