Purchase using existing payment method
Flows that involve purchases should be as simple and short as possible, to
minimize attention needed from drivers.
Be sure to follow the
guidelines for purchase flows.
Sample flow
| User action |
Where action is performed |
Step count after action |
| The user is using your app. They decide to make a purchase. |
Landing template (not shown) |
1 |
| The user selects a parking location from a curated list of nearby or
recently booked locations. |
List template
|
2 |
| The user views parking location details and reserves the spot; the
purchase takes place in the background. |
Pane template
|
3 |
| The user sees confirmation and selects Navigate. |
Message template
|
4 |
| A separate navigation app opens and routing begins. |
Switch to navigation app
|
1 (new task) |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-23 UTC.
[null,null,["Last updated 2024-07-23 UTC."],[[["In-car purchase flows should be straightforward and require minimal driver attention, ideally concluding within 3 steps inside the app."],["Apps should streamline the purchase process by offering curated parking location lists, background purchase handling, and clear confirmation messages."],["Upon purchase confirmation, initiate navigation using a seamless transition to a dedicated navigation app, ensuring a clear task separation for the driver."]]],[]]