Google is preparing a significant redesign for its Wallet application, aiming to streamline access to frequently used passes and cards. The update, currently in development and revealed through analysis of the latest app version, shifts the focus to a “starred” or “favorite” system, allowing users to pin their most-used payment methods and passes directly to the home screen. While the changes promise a more efficient user experience, the implementation introduces an extra step for accessing less frequently used items.
Currently, Google Wallet displays payment cards at the top of the screen, followed by a lengthy list of loyalty cards, transit passes, and other digital assets. The upcoming redesign retains the payment card prioritization but alters the presentation of passes. Instead of a single, scrolling list, passes will now populate a two-column grid layout, with a “View more” button positioned lower on the screen. This button doesn’t immediately reveal all passes. instead, it leads to an intermediary landing page.
This landing page features a search bar and settings options, and crucially, *another* button labeled “View more passes.” Only by tapping this second button does the user finally gain access to a complete list of all their stored passes. The design choice introduces a two-step process where previously all passes were directly accessible. The purpose of this layered approach appears to be reducing clutter on the main screen, but it adds a layer of friction for users who need to access passes beyond their designated favorites.
The redesign also introduces management features. The “View more passes” screen allows users to reorder their passes and sort them alphabetically or by the date they were last used. Archived passes are segregated into a dedicated section at the end of the list. This provides a degree of organization not currently available in the existing Google Wallet interface.
The core of the redesign revolves around the “star” button, functioning as a favorite or pin feature. Users will be able to designate up to four cards and passes as favorites, ensuring they are prominently displayed on the home screen. The system will likely, though not definitively confirmed, offer suggestions for favorites based on usage patterns, though the initial implementation appears to automatically select four passes for the user. This automated selection could be a point of contention for users who prefer to curate their own preferred selection.
This isn’t the first indication of Google’s intent to overhaul the Wallet experience. , reports surfaced detailing Google Wallet’s adoption of Material 3, Google’s expressive design language. This earlier update included a redesigned logo, larger pass “pills” (the visual representations of passes), and a floating action button. These changes, combined with the current redesign, suggest a broader effort to modernize and improve the usability of Google Wallet.
The move towards a more curated experience aligns with a broader trend in mobile app design, where developers are prioritizing quick access to frequently used features. However, the added steps required to access less common passes raise questions about the overall efficiency of the new interface. The success of the redesign will depend on how effectively Google balances the desire for a streamlined home screen with the need for easy access to all stored passes.
Beyond the user interface changes, Google continues to expand the functionality of Google Wallet. Developers are able to customize passes with predefined and developer-defined fields, offering a degree of flexibility in how information is presented. This customization extends beyond the card face, allowing for template overrides and tailored experiences.
The redesigned Google Wallet, as currently observed in the app’s code, represents a significant shift in how users interact with their digital cards and passes. While the “starred” system and grid layout promise a more focused experience, the added steps to access all passes could prove to be a trade-off. The update is not yet live, and Google has not provided a specific release date. Further testing and user feedback will likely shape the final implementation before it is rolled out to the public.
