Panoramica dei viaggi on demand dell'SDK Driver
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
L'SDK Driver è un toolkit per app mobile e un componente fondamentale di Fleet
Engine. Con questo SDK, l'app per i conducenti può gestire le corse assegnate e
attivare le funzionalità di navigazione e itinerario per i conducenti.
Prima di iniziare
Questa guida presuppone che tu abbia letto quanto segue:
Che cos'è l'SDK driver per le corse on demand?
L'SDK Driver comunica la posizione del veicolo e gli aggiornamenti del viaggio a Fleet Engine, in modo che Fleet Engine possa monitorare i veicoli e i viaggi assegnati. Fondamentalmente, l'SDK utilizza un listener di eventi per inviare aggiornamenti della posizione e coordinate di latitudine/longitudine, insieme al segmento di percorso e alla destinazione correnti dall'SDK Navigation a Fleet Engine quando l'autista inizia a guidare.
Perché utilizzare l'SDK driver per le corse on demand?
L'SDK Driver consente una più facile integrazione con Fleet Engine per gli aggiornamenti
dei percorsi dell'autista. Con questo SDK, l'autista può utilizzare una sola app per gestire
gli incarichi e navigare come farebbe con la versione consumer di Google
Maps, ma senza dover passare a un'altra app.
Cosa puoi fare con l'SDK Driver per le corse on demand
Utilizza l'SDK Driver per i viaggi on demand per comunicare quanto segue con Fleet
Engine:
- La posizione in tempo reale di un veicolo su una mappa.
- Coordinate di latitudine/longitudine dei waypoint del viaggio fornite dall'SDK Navigation.
- Distanza rimanente dal prossimo waypoint.
- Orario di arrivo stimato al waypoint successivo.
- Il percorso che il veicolo deve seguire, come fornito dall'SDK Navigation.
Come funziona l'SDK Driver per i viaggi on demand
L'SDK Driver dipende dall'SDK Navigation per le informazioni sul percorso e
la destinazione. Insieme alle informazioni dell'SDK Navigation, l'SDK Driver si integra con la tua app per i conducenti e fornisce a Fleet Engine un flusso di aggiornamenti della posizione, coordinate di latitudine/longitudine, distanza rimanente e ETA.
Tutti gli altri aggiornamenti dei dati del veicolo devono essere inviati al backend del cliente, che
trasmette i dati a Fleet Engine.

Come utilizzare Driver SDK per le corse on demand
Seleziona la tua piattaforma per scoprire come iniziare a utilizzare il Driver SDK.
Passaggi successivi
Consulta la documentazione della piattaforma su cui vuoi configurare Driver
SDK:
Salvo quando diversamente specificato, i contenuti di questa pagina sono concessi in base alla licenza Creative Commons Attribution 4.0, mentre gli esempi di codice sono concessi in base alla licenza Apache 2.0. Per ulteriori dettagli, consulta le norme del sito di Google Developers. Java è un marchio registrato di Oracle e/o delle sue consociate.
Ultimo aggiornamento 2025-08-31 UTC.
[null,null,["Ultimo aggiornamento 2025-08-31 UTC."],[[["\u003cp\u003eThe Driver SDK is a toolkit for building driver apps that seamlessly integrate with Fleet Engine for trip management and navigation.\u003c/p\u003e\n"],["\u003cp\u003eIt enables real-time location sharing, route updates, and trip progress communication between the driver app and Fleet Engine.\u003c/p\u003e\n"],["\u003cp\u003eBy using the Driver SDK, drivers can manage assignments and navigate within a single app, enhancing efficiency and convenience.\u003c/p\u003e\n"],["\u003cp\u003eThe SDK relies on the Navigation SDK for routing information and works in conjunction with it to provide a comprehensive solution for on-demand trips.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can find platform-specific setup instructions and further details in the provided Android and iOS documentation.\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 assigned trips 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#on-demand-trips).\n- [The data model for on-demand trips](/maps/documentation/mobility/fleet-engine/essentials/trip-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 on-demand trips?\n\nThe Driver SDK communicates vehicle location and trip updates to Fleet Engine so\nthat Fleet Engine can track the vehicles and their assigned\ntrips. 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 on-demand trips?\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 on-demand trips\n\nUse the Driver SDK for on-demand trips to communicate the following with Fleet\nEngine:\n\n- A vehicle's real-time position on a map.\n- Latitude/longitude coordinates for the trip waypoints provided by the Navigation SDK.\n- Remaining distance to the next waypoint.\n- Estimated time of arrival to the next waypoint.\n- Route the vehicle needs to take as provided by the Navigation SDK.\n\nHow the Driver SDK for on-demand trips 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 on-demand trips\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| 7 | **Set the trip details** | For more information, see [Set the trip details](./android/trip-details). |\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| 6 | **Set the trip details** | For more information, see [Set the trip details](./ios/trip-details). |\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/minimum-requirements)\n- [iOS](./ios/minimum-requirements)"]]