Visão geral das tarefas programadas do SDK do Driver
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O SDK Driver é um kit de ferramentas de apps para dispositivos móveis e um componente fundamental do Fleet
Engine. Com esse SDK, o app do motorista pode gerenciar tarefas de trabalho e
ativar recursos de navegação e rotas para motoristas.
Antes de começar
Este guia pressupõe que você já leu o seguinte:
O que é o SDK Driver para tarefas programadas?
O SDK do driver comunica a localização do veículo e as atualizações de tarefas ao Fleet Engine para que ele possa gerenciar os veículos de entrega e as paradas e tarefas de entrega atribuídas. Basicamente, o SDK usa um listener de eventos para enviar atualizações de localização e coordenadas de latitude/longitude, além do segmento de rota atual e do destino do SDK Navigation para o Fleet Engine quando o motorista começa a dirigir.
Por que usar o SDK Driver para tarefas programadas?
O SDK Driver facilita a integração com o Fleet Engine para atualizações nas rotas do motorista. Com esse SDK, o motorista pode usar um único app para gerenciar
tarefas e navegar como faria com a versão para consumidor do Google
Maps, mas sem precisar mudar para outro app.
O que você pode fazer com o SDK Driver para tarefas programadas
Use o SDK Driver para tarefas programadas e comunique o seguinte ao Fleet
Engine:
- Posição em tempo real do veículo de entrega em um mapa.
- Coordenadas de latitude/longitude da parada.
- Distância restante até a parada.
- Hora estimada de chegada na parada.
- O trajeto que o veículo precisa fazer, conforme fornecido pelo SDK Navigation.
Como o SDK do Driver para tarefas programadas funciona
O SDK Driver depende do SDK Navigation para informações de trajeto e destino. Junto com as informações do SDK Navigation, o SDK Driver se integra ao app do motorista e fornece ao Fleet Engine um fluxo de atualizações de local, coordenadas de latitude/longitude, distância restante e ETAs.
Todas as outras atualizações de dados do veículo precisam ser enviadas ao back-end do cliente, que
transmite os dados ao Fleet Engine.
Como usar o SDK do Driver para tarefas programadas
Selecione sua plataforma para saber como começar a usar o SDK Driver.
A seguir
Consulte a documentação da plataforma em que você quer configurar o SDK
Driver:
Exceto em caso de indicação contrária, o conteúdo desta página é licenciado de acordo com a Licença de atribuição 4.0 do Creative Commons, e as amostras de código são licenciadas de acordo com a Licença Apache 2.0. Para mais detalhes, consulte as políticas do site do Google Developers. Java é uma marca registrada da Oracle e/ou afiliadas.
Última atualização 2025-08-31 UTC.
[null,null,["Última atualização 2025-08-31 UTC."],[[["\u003cp\u003eThe Driver SDK is a toolkit that enables driver apps to manage work assignments and navigation within Fleet Engine.\u003c/p\u003e\n"],["\u003cp\u003eIt facilitates communication between the driver app and Fleet Engine, sharing location and task updates for efficient delivery management.\u003c/p\u003e\n"],["\u003cp\u003eKey features include real-time location tracking, route optimization using the Navigation SDK, and seamless integration with driver workflows.\u003c/p\u003e\n"],["\u003cp\u003eTo get started, developers need to integrate the Driver SDK (Android or iOS) and configure their Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eFor platform-specific setup instructions and further details, refer to the Android and iOS documentation provided.\u003c/p\u003e\n"]]],[],null,["The Driver SDK is a mobile app toolkit and a fundamental component of Fleet\nEngine. With this SDK, your driver app can both manage work assignments and\nenable driver navigation and routing capabilities.\n\nBefore you begin\n\nThis guide assumes you have read the following:\n\n- [Fleet Engine essentials](/maps/documentation/mobility/fleet-engine/essentials).\n- [The data model for vehicles](/maps/documentation/mobility/fleet-engine/essentials/vehicles-intro#scheduled-tasks).\n- [The data model for scheduled tasks](/maps/documentation/mobility/fleet-engine/essentials/tasks-intro#data-model).\n- [How to set up Fleet Engine](/maps/documentation/mobility/fleet-engine/essentials/set-up-fleet).\n- [How to create and use vehicles in Fleet Engine](/maps/documentation/mobility/fleet-engine/essentials/vehicles).\n\nWhat is the Driver SDK for scheduled tasks?\n\nThe Driver SDK communicates vehicle location and task updates to Fleet Engine so\nthat Fleet Engine can manage the delivery vehicles and their assigned delivery\nstops and tasks. At its core, the SDK uses an event listener to send location\nupdates and latitude/longitude coordinates, along with the current route segment\nand destination from the Navigation SDK to Fleet Engine when your driver begins\ndriving.\n\nWhy use the Driver SDK for scheduled tasks?\n\nThe Driver SDK enables easier integration with Fleet Engine for updates to the\ndriver's routes. With this SDK, your driver can use a single app to manage\nassignments and navigate as they would using their consumer version of Google\nMaps but without having to switch to another app.\n\nWhat you can do with the Driver SDK for scheduled tasks\n\nUse the Driver SDK for scheduled tasks to communicate the following with Fleet\nEngine:\n\n- Delivery vehicle's real-time position on a map.\n- Latitude/longitude coordinates for the stop.\n- Remaining distance to the stop.\n- Estimated time of arrival to the stop.\n- Route the vehicle needs to take as provided by the Navigation SDK.\n\nHow the Driver SDK for scheduled tasks works\n\nThe Driver SDK depends on the Navigation SDK for the routing information and\ndestination. Together with the information from the Navigation SDK, the Driver\nSDK integrates with your driver app and provides Fleet Engine with a stream of\nlocation updates, latitude/longitude coordinates, remaining distance, and ETAs.\nAll other vehicle data updates must be sent to the customer backend, which\nrelays the data to Fleet Engine.\n\nHow to use the Driver SDK for scheduled tasks\n\nSelect your platform to see how to start using the Driver SDK. \n\nAndroid\n\n|---|----------------------------------------------|----------------------------------------------------------------------------------------------------|\n| 1 | **Get the Driver SDK for Android** | For more information, see [Get the Driver SDK](./android/minimum-requirements). |\n| 2 | **Configure a Google Cloud console project** | For more information, see [Configure a Google Cloud console project](./android/configure-project). |\n| 3 | **Declare dependencies** | For more information, see [Declare dependencies](./android/dependencies). |\n| 4 | **Create authentication tokens** | For more information, see [Create authentication tokens](./android/authenticate). |\n| 5 | **Initialize the Driver SDK** | For more information, see [Initialize the Driver SDK](./android/initialize-sdk). |\n| 6 | **Get the vehicle ready** | For more information, see [Get the vehicle ready](./android/vehicle-ready). |\n\niOS\n\n|---|----------------------------------------------|------------------------------------------------------------------------------------------------|\n| 1 | **Get the Driver SDK for iOS** | For more information, see [Get the Driver SDK](./ios/minimum-requirements). |\n| 2 | **Configure a Google Cloud console project** | For more information, see [Configure a Google Cloud console project](./ios/configure-project). |\n| 3 | **Create authentication tokens** | For more information, see [Create authentication tokens](./ios/authenticate). |\n| 4 | **Initialize the Driver SDK** | For more information, see [Initialize the Driver SDK](./ios/initialize-sdk). |\n| 5 | **Get the vehicle ready** | For more information, see [Get the vehicle ready](./ios/vehicle-ready). |\n\nWhat's next\n\nSee the documentation for the platform on which you want to set up the Driver\nSDK:\n\n- [Android](./android/)\n- [iOS](./ios/)"]]
