Bookings across Google
Allowing major verticals to accept bookings across Google
Making it easy to book services across Google
Google is interested in building experiences focusing on transactions, believing that not only will it help address an unmet user need, but will drive re-engagement in our core products. The Placesheet is a compelling entry point for this experience as it enables users on all of Google to both discover availability and complete the booking action. I teamed up with another talented designer
to help deliver a v1 experience. We took a look at overall query volume, existing patterns and the competitive landscape within this space.
Today's mesh of transactional UI's
Competitive landscape + common themes
Ultimately, solving for a myriad of vertical specific use cases
I need to make dinner reservations tonight
I'd like to book a class at the nearby yoga studio
We needed a scalable system for an ever-growing list of verticals
Leveraging available and competitive patterns, we then prioritized work based on query volume. We then developed a template flow that could scale between several verticals, to include dining, fitness, beauty/wellness, hotels, events and services.
UI + placement explorations
A standardized UI that doesn't clash
Thus, an E2E transactions framework was born
Icon-driven actions didn't scale well between locales, and didn't allow for customized strings for specific verticals. We decided on text only to allow for more string real estate and for internationalization and wrapping to occur 90% of the time without breaking the framework. Ultimately, our v1 was a mobile-optimized MVP. It currently supported on web and mobile web. More verticals supported over time.
Finalized entry point + service selection UI
Checkout details + confirmation states