Ringkasan tugas terjadwal SDK Driver
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Driver SDK adalah toolkit aplikasi seluler dan komponen mendasar Fleet
Engine. Dengan SDK ini, aplikasi pengemudi Anda dapat mengelola tugas kerja dan
mengaktifkan kemampuan navigasi dan perutean pengemudi.
Sebelum memulai
Panduan ini mengasumsikan bahwa Anda telah membaca hal berikut:
Apa itu Driver SDK untuk tugas terjadwal?
Driver SDK mengomunikasikan lokasi kendaraan dan update tugas ke Fleet Engine sehingga Fleet Engine dapat mengelola kendaraan pengiriman dan tugas serta perhentian pengiriman yang ditetapkan. Pada intinya, SDK menggunakan pemroses peristiwa untuk mengirimkan update lokasi dan koordinat lintang/bujur, beserta segmen rute dan tujuan saat ini dari Navigation SDK ke Fleet Engine saat pengemudi Anda mulai mengemudi.
Mengapa menggunakan Driver SDK untuk tugas terjadwal?
Driver SDK mempermudah integrasi dengan Fleet Engine untuk mendapatkan update rute pengemudi. Dengan SDK ini, pengemudi Anda dapat menggunakan satu aplikasi untuk mengelola tugas dan mendapatkan panduan navigasi seperti yang mereka lakukan saat menggunakan Google Maps versi konsumen, tetapi tanpa harus beralih ke aplikasi lain.
Yang dapat Anda lakukan dengan Driver SDK untuk tugas terjadwal
Gunakan Driver SDK untuk tugas terjadwal guna mengomunikasikan hal berikut dengan Fleet Engine:
- Posisi real-time kendaraan pengiriman di peta.
- Koordinat lintang/bujur untuk perhentian.
- Jarak yang tersisa ke halte.
- Perkiraan waktu tiba di halte.
- Rute yang harus dilalui kendaraan sebagaimana disediakan oleh Navigation SDK.
Cara kerja Driver SDK untuk tugas terjadwal
Driver SDK bergantung pada Navigation SDK untuk informasi dan tujuan rute. Bersama dengan informasi dari Navigation SDK, Driver SDK terintegrasi dengan aplikasi pengemudi Anda dan menyediakan aliran pembaruan lokasi, koordinat lintang/bujur, jarak yang tersisa, dan ETA ke Fleet Engine.
Semua pembaruan data kendaraan lainnya harus dikirim ke backend pelanggan, yang
meneruskan data ke Fleet Engine.
Cara menggunakan Driver SDK untuk tugas terjadwal
Pilih platform Anda untuk melihat cara mulai menggunakan Driver SDK.
Langkah berikutnya
Lihat dokumentasi untuk platform tempat Anda ingin menyiapkan Driver SDK:
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-31 UTC.
[null,null,["Terakhir diperbarui pada 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/)"]]
