驾驶体验和导航
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
驾驶员体验和导航功能是移动服务软件包的一部分，该软件包可将 Google 地图体验嵌入到驾驶员应用中。
您可以使用驾驶员体验和导航功能做些什么？
对于驾驶员体验和导航，您可以使用 Navigation SDK 和 Driver SDK 来调整驾驶体验，以适应您的配送模式。使用 Navigation SDK 在应用中创建精细导航体验，以便实时引导司机。您还可以自定义导航体验，使其与应用的外观和风格相符，并通过优化路线和下车点来增强驾驶员的整体工作流程。
使用 Navigation SDK 自定义驾驶体验，并使用 Driver SDK 通过 Consumer SDK 预定任务概览和车队跟踪功能可视化显示驾驶员位置和路线进度。
为何要使用驾驶员体验和导航？
如果您管理送货车队，那么为了满足消费者的期望，提高送货的可预测性和司机的生产效率至关重要。驾驶员体验和导航功能可帮助您更高效地为驾驶员规划路线，避免延误和漏送，并提高驾驶员的满意度。
- 提高司机满意度：您的应用可帮助司机在完成一天的工作时感到一切尽在掌握，并及时了解相关信息。借助熟悉的 Google 地图导航，您的司机无需学习新的地图界面。您还可以自定义体验，以强化品牌形象。
- 提高司机任务效率：通过反映实时路况的路线，引导司机前往正确的地点。对于需要快速上手工作的新手司机、兼职司机或季节性司机，这些信息尤其有用。此外，您还可以提供特定于配送服务的自定义路线和地图元素。
- 提高配送可预测性：借助嵌入 Google 地图体验的应用，您可以更加放心地让司机遵循预期的路线规划。让司机在您的应用内工作还可以提高您收到的位置信号的质量。
运作方式
以下图表显示了驾驶员体验和导航的所有组件之间的操作顺序。Driver SDK 会将位置更新信息传达给 Fleet Engine 后端。Navigation SDK 会向驾驶员显示精细导航路线（以及其他导航信息）。您的后端会处理与 Fleet Engine 的所有其他配送通信，例如创建和更新车辆及任务。
按需行程
下图显示了按需行程的操作顺序。它分为两个主要部分：一是司机向 Fleet Engine 启用位置信息共享的当天开始时间；二是使用 Fleet Engine 组件简化行程管理的视图。如需详细了解行程流程，请参阅按需行程文档中的什么是行程？。
计划任务
下图显示了预定任务的操作顺序。这包括单个司机的典型配送工作日矩阵，以及如何使用 Fleet Tracking 库在 Fleet Engine 系统中处理其工作。
注意：您的系统可以使用货件跟踪或车队跟踪。借助配送跟踪功能，Fleet Engine 会过滤配送和司机信息，以便客户仅看到与其配送相关的有用信息。
如何使用驾驶员体验和导航
本部分介绍了一种实现包含导航功能的驾驶员体验的方法。为便于说明，此示例先从前端实现开始。您可以先将 SDK 集成到您的司机应用中，也可以先将 Fleet Engine 与后端集成以创建任务和车辆，然后开始实现。
- 将 Driver SDK 集成到您的司机应用中。Driver SDK 会向 Fleet Engine 服务发送实时位置信号。Driver SDK 封装了 Navigation SDK。如需了解详情，请参阅 Driver SDK 用户指南，了解按需行程（Android、iOS）和预定任务（Android、iOS）。
- 将 Navigation SDK 的功能集成到您的司机应用中。Navigation SDK 是一个库，可为您的司机提供自定义导航功能，例如精细导航路线、自定义路线和自定义地图元素。如需查看完整的开发者文档，请参阅使用 Google 地图进行导航。
- 使用 Fleet Engine 管理任务和车辆状态。Fleet Engine 是一种移动后端服务，可通过发出 REST 或 gRPC 调用与 Fleet Engine 通信。如需了解详情，请参阅 Fleet Engine 文档。
推荐内容
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-31。
[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eDriver experience and navigation, part of Google Maps Mobility services, enables you to create custom navigation for delivery drivers using the Navigation and Driver SDKs.\u003c/p\u003e\n"],["\u003cp\u003eThis solution helps improve driver satisfaction by offering familiar Google Maps navigation with custom branding and real-time traffic updates for enhanced productivity.\u003c/p\u003e\n"],["\u003cp\u003eIt also leads to better delivery predictability through optimized routing, location tracking, and integration with Fleet Engine for task management.\u003c/p\u003e\n"],["\u003cp\u003eThis solution utilizes the Navigation SDK for a custom turn-by-turn navigation experience and the Driver SDK to share driver location and route progress with Fleet Engine for tasks or fleet tracking.\u003c/p\u003e\n"],["\u003cp\u003eTo implement, integrate the Driver and Navigation SDKs into your driver app and manage tasks/vehicles via Fleet Engine using REST or gRPC calls.\u003c/p\u003e\n"]]],[],null,["The Driver experience and navigation capability is\npart of the Mobility services packaging that embeds the Google Maps experience\ninto your driver application.\n\nWhat can you do with driver experience and navigation?\n\nWith driver experience and navigation, you use both the Navigation SDK and\nDriver SDK to tune the driving experience to suit your delivery model. Use the\nNavigation SDK to create a turn-by-turn navigation experience in your app to\nguide drivers in real-time. You can also customize the navigation experience to\nmatch the look and feel of your app and enhance drivers' broader workflows with\noptimized routes and drop off locations.\n\nCustomize the driving experience with the Navigation SDK, and use the Driver SDK\nto enable your driver locations and route progress to be visualized through the\n[Consumer SDK scheduled tasks\noverview](/maps/documentation/mobility/journey-sharing/scheduled) and [Fleet\nTracking](/maps/documentation/mobility/operations/fleet-tracking') capabilities.\n\nWhy use driver experience and navigation?\n\nWhen you manage a delivery\nfleet, it's crucial to improve your delivery predictability and driver\nproductivity to meet consumer expectations. Driver experience and navigation\nhelps you more efficiently route your drivers, avoid delays and missed\ndeliveries, and improve your driver's satisfaction.\n\n- **Improve driver satisfaction:** Your app can help drivers feel in control and informed as they accomplish a day of tasks. With the familiar Google Maps navigation, your drivers don't have to learn a new map interface. You can also customize the experience to reinforce your brand.\n- **Improve driver task productivity:** Guide your drivers to the right spot with routes that reflect real-time traffic. This information is especially useful for new, part-time, or seasonal drivers who need to quickly ramp up to their tasks. In addition, you can provide custom routes and map elements specific to your delivery service.\n- **Improve delivery predictability:** With an app that embeds the Google Maps experience, you can have more confidence that your drivers follow expected route plans. Keeping your drivers within your application also improves the quality of location signals you get.\n\nHow it works\n\nThe following diagrams shows the sequence of operations between all components\nof Driver experience and navigation. The Driver SDK communicates location\nupdates to the Fleet Engine backend. The Navigation SDK presents turn by turn\ndirections (and other navigation information) to the driver. Your backend\nhandles all other delivery communication to Fleet Engine, such as creating and\nupdating vehicles and tasks. \n\nOn-demand trips\n\nThe following diagram shows the sequence of\noperations for on-demand trips. It's divided in two key parts, the start\nof the day when drivers enable location sharing to Fleet Engine, and a\nsimplified view of trip management using Fleet Engine components. For a\ndetail view of the trip process, see [What is a\ntrip?](/maps/documentation/mobility/fleet-engine/journeys/trips) in the **On-demand trips** documentation.\n\nScheduled tasks\n\nThe following diagram shows the sequence of\noperations for scheduled tasks. This includes a matrix of a typical shipment\nworkday for a single driver along with how their work is handled in the\nFleet Engine system using the Fleet Tracking library.\n\n**Note**: Your system can use both shipment tracking or\nfleet tracking. With shipment tracking, Fleet Engine filters shipment and\ndriver information so that a customer see only information relevant to their\nshipment.\n\nHow to use driver experience and navigation\n\nThis section describes one way you can implement a driver experience with\nnavigation. For ease of explanation, this example starts with the frontend\nimplementation first. You can start implementation either by integrating the\nSDKs into your driver app first, or by integrating Fleet Engine with your\nbackend for task and vehicle creation.\n\n1. **Integrate the Driver SDK into your driver app** . The Driver SDK sends real-time location signals to the Fleet Engine service. The Driver SDK wraps the Navigation SDK. For details, see the Driver SDK user guides for On-demand trips ([Android](/maps/documentation/mobility/driver-sdk/on-demand/android), [iOS](/maps/documentation/mobility/driver-sdk/on-demand/ios)) and Scheduled tasks ([Android](/maps/documentation/mobility/driver-sdk/scheduled/android), [iOS](/maps/documentation/mobility/driver-sdk/scheduled/ios)).\n2. **Implement features of the Navigation SDK into your driver app** . The Navigation SDK is a library that provides customized navigation capabilities to your drivers, such as turn-by-turn instructions, customized routes, and customized map elements. For full developer documentation, see [Navigation with Google Maps](/maps/documentation/navigation-sdk).\n3. **Manage tasks and vehicle state with Fleet Engine** . Fleet Engine is the Mobility backend service that can communicate with Fleet Engine by making either REST or gRPC calls. For details, see the [Fleet Engine documentation](/maps/documentation/mobility/fleet-engine).\n\nRecommended content"]]
