Driver SDK for scheduled tasks
Stay organized with collections
Save and categorize content based on your preferences.
This is the guide for scheduled tasks. I kept these separate for two reasons:
It's easier for a user to "choose their model" and stick with it.
Scheduled tasks supports a "trusted client" scenario for both iOS and Android
although it's only documented on Android.
It seems like a different set of topics, beyond setup
Android guides have 4.0 and 5.0 migrations guides as well as google play data disclosure guide
We can later on add a nice intro page for the Driver SDKs for each model,
bespoke to each use case.
The engineering teams here sometimes only publish to one or the other, so
that'll make it easier for LMFS-ey vs ODRD-ey people to update just their side
of the equation.
If we do includes, let's please put the includes directory for this content
under ios (closer to the host page) and not in the global includes directory.
Another idea is to split out 2 guides here one for setup and the other for
getting started, where setup includes the first three topics for each model.
Key topics for this model:
- minimum requiremenst
- maven config
- project config
- dependencies
- init the SDK
- Enable location updates
- disable location updates
- trusted model use cases
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 2025-08-27 UTC.
[null,null,["Last updated 2025-08-27 UTC."],[[["\u003cp\u003eThis guide focuses on scheduled tasks for iOS and Android, offering a model-specific approach for easier user navigation.\u003c/p\u003e\n"],["\u003cp\u003eScheduled tasks uniquely support a "trusted client" scenario for enhanced security, documented for Android and applicable to iOS.\u003c/p\u003e\n"],["\u003cp\u003eAndroid guides include migration guides for versions 4.0 and 5.0, along with Google Play data disclosure guidelines for comprehensive support.\u003c/p\u003e\n"],["\u003cp\u003eContent is structured for flexibility, allowing teams to update their specific sections, such as LMFS or ODRD, independently.\u003c/p\u003e\n"],["\u003cp\u003eThe guide covers key topics like minimum requirements, configuration, dependencies, SDK initialization, and location updates, with a focus on "trusted model" use cases.\u003c/p\u003e\n"]]],[],null,["# Driver SDK for scheduled tasks\n\nThis is the guide for scheduled tasks. I kept these separate for two reasons:\n\n1. It's easier for a user to \"choose their model\" and stick with it.\n\n2. Scheduled tasks supports a \"trusted client\" scenario for both iOS and Android\n although it's only documented on Android.\n\n3. It seems like a different set of topics, beyond setup\n\n4. Android guides have 4.0 and 5.0 migrations guides as well as google play data disclosure guide\n\n5. We can later on add a nice intro page for the Driver SDKs for each model,\n bespoke to each use case.\n\n6. The engineering teams here sometimes only publish to one or the other, so\n that'll make it easier for LMFS-ey vs ODRD-ey people to update just their side\n of the equation.\n\nIf we do includes, let's please put the includes directory for this content\n*under* ios (closer to the host page) and not in the global includes directory.\n\nAnother idea is to split out 2 guides here one for setup and the other for\ngetting started, where setup includes the first three topics for each model.\n\nKey topics for this model:\n\n- minimum requiremenst\n- maven config\n- project config\n- dependencies\n- init the SDK\n- Enable location updates\n- disable location updates\n- trusted model use cases"]]
