The Indianized version of Google Pay has cornered the largest chunk of India’s UPI market, piggybacking the username-based P2P payment system. Launched as Tez, Google rebranded the app to Pay following the global consolidation of its payment solutions, though the app retained its distinct functionality that contrasts with its stateside counterpart. About two years into its existence, the app is now getting a design change under Google’s refreshed material guidelines, tidying up some of its UI elements.
Left: Old home screen. Right: New home screen.
The app’s welcome screen has been overhauled with a cleaner look, doing away with the Nearby payments option and decluttering the suggestions section. In the header region, the user’s name and the associated UPI ID are now gone, and only the display picture now sits in the right corner. The opposite side is occupied by an icon to trigger the QR code scanner, which was previously listed in a clunky overflow menu. The New payment option now has its own floating action button at the bottom, which takes you to a revamped search area.
Left: Old search screen. Right: New search screen.
Google’s Material Design elements are abundantly present in the search section that is now neatly ordered under three tabs — Businesses, People, and Bills & Transfers. The older interface arranged everything on a single page, adding to its clutter. Additionally, some icons have been flattened and the search bar has changed its shape to match other Google apps.
Tabbed menu of the ‘New payment’ section.
The profile section has also undergone a similar cleansing treatment, which now judiciously utilizes the header area. Your personal details, a custom QR code, and your reward earning’s total are accessible from the same screen, while all scattered menu options have been put together under Settings.
Left: Old profile page. Right: New profile page.
All these changes appeared for our tipster on the stable Google Pay app version 47.0.001_RC02 (APK Mirror). However, even that release still shows me the older UI, suggesting we’re looking at a server-side change.