blocks|key|20661|text|WorkManager看起来像是谷歌对Evernote的Android-Job库的回应，但有一些改进。它使用JobScheduler，Firebase+JobDispatcher和AlarmManager，就像Android-Job一样，这取决于设备的API级别。它们对标签的使用看起来非常相似，为作业/工作分配约束也足够相似。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|20662|我感到兴奋的两个特性是:能够链接工作和能够在有约束的工作中投机取巧。第一个将允许工作(工作)被分解，并且对我来说更加模块化。有了更多的模块化工作，每项工作可能会有更少的限制，从而提高了他们更早完成的机会(机会主义)。例如，大多数处理工作可以在满足具有网络约束的工作之前完成。|20663|因此，如果您对当前的调度器实现感到满意，并且我提到的两个功能没有增加价值，那么我现在还看不到进行转换的巨大好处。但是如果你正在写一些新的东西，使用WorkManager可能是值得的。|20664|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

WorkManager just seems like Google's answer to Evernote's Android-Job library, but with a few improvements. It uses JobScheduler, Firebase JobDispatcher and AlarmManager just like Android-Job depending on the device's API level. Their usage of tags looks pretty much the same and assigning constraints to jobs/work are similar enough.

The two features that I am excited about are: being able to chain work and the ability to be opportunistic on work with constraints. The first will allow work (jobs) to be broken up and more modular for me. And with more modular work, each piece of work may have fewer constraints improving the chance they will complete earlier (opportunistic). For example, the majority of processing work can complete before the work with a network constraint needs to be met.

So if you're happy with your current scheduler implementation and the two features I mentioned don't add value, I don't see a huge benefit to making the switch just yet. But if you're writing something new, it'll probably be worth it to use WorkManager.

blocks|key|22190|text|WorkManager使用JobScheduler服务来调度作业。如果设备不支持JobScheduler，则使用Firebase+JobDispatcher服务。如果Firebase+JobDispatcher在设备上不可用，它将使用AlarmManager和BroadcastReceiver。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|22191|因此，使用WorkManager，您不需要担心向后兼容性。除此之外，它还允许定义运行作业所需满足的约束，例如定义网络约束、电池电量、充电状态和存储容量。|22192|它允许任务链接和将参数传递给作业。|22193|http://www.zoftino.com/scheduling-tasks-with-workmanager-in-android|22194|entityMap|0|LINK|mutability|MUTABLE|url^0|0|B|D|C|14|C|1T|D|2K|D|39|C|3M|H|0|5|B|0|0|0|1V|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|L|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|K]]]]

<code>WorkManager</code> uses <code>JobScheduler</code> service to schedule the jobs. If <code>JobScheduler</code> is not supported by the device, then it uses Firebase <code>JobDispatcher</code> service.
If Firebase <code>JobDispatcher</code> is not available on the device, it will use <code>AlarmManager</code> and <code>BroadcastReceiver</code>.

So with <code>WorkManager</code>, you don't need to worry about backward compatibility. In addition to this, it allows for defining constraints, which need to be met in order for the job to be run, such as defining network constraints, battery level, charging state and storage level.

It allows task chaining and passing of argument to the job.

<a href="http://www.zoftino.com/scheduling-tasks-with-workmanager-in-android" rel="noreferrer">http://www.zoftino.com/scheduling-tasks-with-workmanager-in-android</a>

blocks|key|20748|text|WorkManager位于JobScheduler和AlarmManager之上。WorkManager根据用户的设备API级别等条件选择要使用的正确API|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|20749|WorkManager是一个简单但非常灵活的库，它有很多额外的好处。其中包括：|20750|+-Support+for+both+asynchronous+one-off+and+periodic+tasks.
+-Support+for+constraints+such+as+network+conditions,+storage+space,+and+charging+-status+
+-Chaining+of+complex+work+requests,+including+running+work+in+parallel.
+-Output+from+one+work+request+used+as+input+for+the+next.
+-Handles+API+level+compatibility+back+to+API+level+14.
+-Works+with+or+without+Google+Play+services.
+-Follows+system+health+best+practices.
+-LiveData+support+to+easily+display+work+request+state+in+UI.|code-block|syntax|javascript|20751|entityMap^0|0|1S|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

WorkManager sits on top of JobScheduler and AlarmManager. WorkManager picks the right APIs to use, based on conditions like the user's device API level

WorkManager is a simple, but incredibly flexible library that has many additional benefits. These include:

<pre><code> -Support for both asynchronous one-off and periodic tasks.
 -Support for constraints such as network conditions, storage space, and charging -status 
 -Chaining of complex work requests, including running work in parallel.
 -Output from one work request used as input for the next.
 -Handles API level compatibility back to API level 14.
 -Works with or without Google Play services.
 -Follows system health best practices.
 -LiveData support to easily display work request state in UI.
</code></pre>

blocks|key|20759|text|在我的测试中，在用户关闭我的应用程序后，JobScheduler可以继续运行服务，但我找不到使用WorkManager的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|20760|我在一台运行Oreo+Android+8.0.0+(API+26)的Nexus+5X上进行了测试。我可能只是走运，这个设备/操作系统的组合可以在杀死应用程序后继续服务。我相信它可能是特定于设备的，因为我在https://stackoverflow.com/a/52605503/2848676+to+Android.+Is+WorkManager+running+when+app+is+closed?的回答中读到了这一点。“您可以在dontkillmyapp.com上找到不同原始设备制造商行为的完整列表。”|offset|length|20761|注意:我观察到，当用户关闭应用程序时，JobService需要几秒钟甚至几分钟才能重新启动。|20762|为了让JobScheduler推出一个在应用程序死亡后仍然存在的服务，请按如下方式创建该服务：|20763|++++JobScheduler+jobScheduler+=+(JobScheduler)applicationContext.getSystemService(Context.JOB_SCHEDULER_SERVICE);
++++ComponentName+componentName+=+new+ComponentName(applicationContext,+ScannerAsJobService.class);
++++JobInfo+jobInfo+=+new+JobInfo.Builder(JOB_ID,+componentName)
++++++++++++.setPersisted(true)++//+relaunch+on+reboot
++++++++++++.setMinimumLatency(1)
++++++++++++.setOverrideDeadline(1)
++++++++++++.build();
++++int+result+=+jobScheduler.schedule(jobInfo);|code-block|syntax|javascript|20764|ScannerAsJobService用当前信息更新一个通知，包括服务是否在“后台”(我引用这个信息是因为对“后台”有不同的定义，但这一条准确地反映了应用程序是否不再运行)：|style|CODE|20765|import+android.app.ActivityManager;
import+android.app.Notification;
import+android.app.NotificationChannel;
import+android.app.NotificationManager;
import+android.app.PendingIntent;
import+android.app.job.JobParameters;
import+android.app.job.JobService;
import+android.content.Context;
import+android.content.Intent;
import+android.graphics.Color;
import+android.os.Build;
import+android.os.Handler;

import+androidx.annotation.RequiresApi;

import+java.util.Date;
import+java.util.Timer;
import+java.util.TimerTask;

public+class+ScannerAsJobService+extends+JobService+{
++++private+static+final+String+TAG+=+"ScannerAsJobService";

++++private+static+final+String+NOTIFICATION_CHANNEL_ID+=+"ll_notification_channel";

++++final+Handler+workHandler+=+new+Handler();
++++Runnable+workRunnable;

++++@Override
++++public+boolean+onStartJob(JobParameters+params)+{
++++++++workRunnable+=+new+Runnable()+{
++++++++++++@Override
++++++++++++public+void+run()+{
++++++++++++++++//+See+https://stackoverflow.com/questions/45692181/android-job-scheduler-schedule-job-to-execute-immediately-and-exactly-once
++++++++++++++++(new+Timer()).schedule(new+TimerTask()+{
++++++++++++++++++++@Override
++++++++++++++++++++public+void+run()+{
++++++++++++++++++++++++String+message+=+"Time:+"+%2B+(new+Date()).toString()+%2B+"+background:+"+%2B+appIsInBackground();

++++++++++++++++++++++++//+https://stackoverflow.com/a/32346246/2848676
++++++++++++++++++++++++Intent+intent+=+new+Intent();

++++++++++++++++++++++++PendingIntent+pendingIntent+=+PendingIntent.getActivity(ScannerAsJobService.this,+1,+intent,+0);

++++++++++++++++++++++++Notification.Builder+builder+=+new+Notification.Builder(ScannerAsJobService.this);

++++++++++++++++++++++++builder.setAutoCancel(false);
++++++++++++++++++++++++builder.setTicker("my+ticker+info");
++++++++++++++++++++++++builder.setContentTitle("my+content+title");
++++++++++++++++++++++++builder.setContentText(message);
++++++++++++++++++++++++builder.setSmallIcon(R.drawable.my_icon);
++++++++++++++++++++++++builder.setContentIntent(pendingIntent);
//++++++++++++++++++++++++builder.setOngoing(true);+++//+optionally+uncomment+this+to+prevent+the+user+from+being+able+to+swipe+away+the+notification
++++++++++++++++++++++++builder.setSubText("my+subtext");+++//API+level+16
++++++++++++++++++++++++builder.setNumber(100);
++++++++++++++++++++++++if+(Build.VERSION.SDK_INT+>=+Build.VERSION_CODES.O)+{
++++++++++++++++++++++++++++setupNotificationChannel(NOTIFICATION_CHANNEL_ID);
++++++++++++++++++++++++++++builder.setChannelId(NOTIFICATION_CHANNEL_ID);
++++++++++++++++++++++++}
++++++++++++++++++++++++builder.build();

++++++++++++++++++++++++NotificationManager+manager+=+(NotificationManager)+getSystemService(NOTIFICATION_SERVICE);
++++++++++++++++++++++++manager.notify(93423,+builder.build());

++++++++++++++++++++++++Log.d(TAG+%2B+"+Notification+message:+"+%2B+message);

++++++++++++++++++++}
++++++++++++++++},+1+*+1000,+5+*+1000);

++++++++++++++++jobFinished(params,+true);
++++++++++++}
++++++++};
++++++++workHandler.post(workRunnable);

++++++++//+return+true+so+Android+knows+the+workRunnable+is+continuing+in+the+background
++++++++return+true;
++++}

++++//+https://stackoverflow.com/a/45692202/2848676
++++@RequiresApi(api+=+Build.VERSION_CODES.O)
++++private+void+setupNotificationChannel(String+channelId)+{
++++++++NotificationManager+mNotificationManager+=+(NotificationManager)+getSystemService(Context.NOTIFICATION_SERVICE);

++++++++//+The+user-visible+name+of+the+channel.
++++++++CharSequence+name+=+getString(R.string.my_channel_name);

++++++++//+The+user-visible+description+of+the+channel.
++++++++String+description+=+getString(R.string.my_channel_name);

++++++++int+importance+=+NotificationManager.IMPORTANCE_LOW;

++++++++NotificationChannel+mChannel+=+new+NotificationChannel(channelId,+name,+importance);

++++++++//+Configure+the+notification+channel.
++++++++mChannel.setDescription(description);

++++++++mChannel.enableLights(true);
++++++++//+Sets+the+notification+light+color+for+notifications+posted+to+this
++++++++//+channel,+if+the+device+supports+this+feature.
++++++++mChannel.setLightColor(Color.RED);

++++++++mChannel.enableVibration(true);
++++++++mChannel.setVibrationPattern(new+long[]{100,+200,+300,+400,+500,+400,+300,+200,+400});

++++++++mNotificationManager.createNotificationChannel(mChannel);
++++}

++++/**
+++++*+Source:+<a+href="https://stackoverflow.com/a/39589149/2848676">https://stackoverflow.com/a/39589149/2848676</a>
+++++*+@return+true+if+the+app+is+in+the+background,+false+otherwise
+++++*/
++++private+boolean+appIsInBackground()+{
++++++++ActivityManager.RunningAppProcessInfo+myProcess+=+new+ActivityManager.RunningAppProcessInfo();
++++++++ActivityManager.getMyMemoryState(myProcess);
++++++++boolean+isInBackground+=+myProcess.importance+!=+ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND;
++++++++return+isInBackground;
++++}

++++@Override
++++public+boolean+onStopJob(JobParameters+params)+{
++++++++//+returning+true+schedules+the+job+for+retry+(we're+using+it+to+implement+periodicity+since
++++++++//+JobInfo.Builder.setPeriodic()+didn't+work
++++++++return+true;
++++}
}|20766|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/52605503/2848676|1|https://stackoverflow.com/questions/50682061/android-is-workmanager-running-when-app-is-closed|2|https://dontkillmyapp.com/^0|0|2U|18|0|46|1F|1|61|H|2|0|0|0|0|0|J|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]|$D|1B|E|1C|1|1D]|$D|1E|E|1F|1|1G]]|A|$]]|$1|F|3|G|5|6|7|1H|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1I|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1J|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1K|8|@$D|1L|E|1M|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|L|7|1N|8|@]|9|@]|A|$M|N]]|$1|U|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]|14|$5|X|Y|Z|A|$10|15]]]]

In my testing, JobScheduler could continue running a service after the user closes my app but I could find no way to do that with WorkManager.

I tested on a Nexus 5X running Oreo Android 8.0.0 (API 26). I may have just gotten lucky that this device/OS combination could continue the service after killing the app. I believe it might be device specific because of what I read in this answer <a href="https://stackoverflow.com/a/52605503/2848676">https://stackoverflow.com/a/52605503/2848676</a> to <a href="https://stackoverflow.com/questions/50682061/android-is-workmanager-running-when-app-is-closed">Android. Is WorkManager running when app is closed?</a>. "You can find a complete list of different OEM behaviors on <a href="https://dontkillmyapp.com" rel="nofollow noreferrer">dontkillmyapp.com</a>."

NOTE: I observed that when the user closed the app, it took several seconds or even minutes for the JobService to restart.

To make JobScheduler launch a service that survives app death, created the service as follows:

<pre><code> JobScheduler jobScheduler = (JobScheduler)applicationContext.getSystemService(Context.JOB_SCHEDULER_SERVICE);
 ComponentName componentName = new ComponentName(applicationContext, ScannerAsJobService.class);
 JobInfo jobInfo = new JobInfo.Builder(JOB_ID, componentName)
 .setPersisted(true) // relaunch on reboot
 .setMinimumLatency(1)
 .setOverrideDeadline(1)
 .build();
 int result = jobScheduler.schedule(jobInfo);
</code></pre>

<code>ScannerAsJobService</code> updates a notification with current information, including whether the service is "in the background" (which I quote because there are different definitions of "background" but this one accurately reflected whether the app was no longer running):

<pre><code>import android.app.ActivityManager;
import android.app.Notification;
import android.app.NotificationChannel;
import android.app.NotificationManager;
import android.app.PendingIntent;
import android.app.job.JobParameters;
import android.app.job.JobService;
import android.content.Context;
import android.content.Intent;
import android.graphics.Color;
import android.os.Build;
import android.os.Handler;

import androidx.annotation.RequiresApi;

import java.util.Date;
import java.util.Timer;
import java.util.TimerTask;

public class ScannerAsJobService extends JobService {
 private static final String TAG = "ScannerAsJobService";

 private static final String NOTIFICATION_CHANNEL_ID = "ll_notification_channel";

 final Handler workHandler = new Handler();
 Runnable workRunnable;

 @Override
 public boolean onStartJob(JobParameters params) {
 workRunnable = new Runnable() {
 @Override
 public void run() {
 // See https://stackoverflow.com/questions/45692181/android-job-scheduler-schedule-job-to-execute-immediately-and-exactly-once
 (new Timer()).schedule(new TimerTask() {
 @Override
 public void run() {
 String message = "Time: " + (new Date()).toString() + " background: " + appIsInBackground();

 // https://stackoverflow.com/a/32346246/2848676
 Intent intent = new Intent();

 PendingIntent pendingIntent = PendingIntent.getActivity(ScannerAsJobService.this, 1, intent, 0);

 Notification.Builder builder = new Notification.Builder(ScannerAsJobService.this);

 builder.setAutoCancel(false);
 builder.setTicker("my ticker info");
 builder.setContentTitle("my content title");
 builder.setContentText(message);
 builder.setSmallIcon(R.drawable.my_icon);
 builder.setContentIntent(pendingIntent);
// builder.setOngoing(true); // optionally uncomment this to prevent the user from being able to swipe away the notification
 builder.setSubText("my subtext"); //API level 16
 builder.setNumber(100);
 if (Build.VERSION.SDK_INT &gt;= Build.VERSION_CODES.O) {
 setupNotificationChannel(NOTIFICATION_CHANNEL_ID);
 builder.setChannelId(NOTIFICATION_CHANNEL_ID);
 }
 builder.build();

 NotificationManager manager = (NotificationManager) getSystemService(NOTIFICATION_SERVICE);
 manager.notify(93423, builder.build());

 Log.d(TAG + " Notification message: " + message);

 }
 }, 1 * 1000, 5 * 1000);

 jobFinished(params, true);
 }
 };
 workHandler.post(workRunnable);

 // return true so Android knows the workRunnable is continuing in the background
 return true;
 }

 // https://stackoverflow.com/a/45692202/2848676
 @RequiresApi(api = Build.VERSION_CODES.O)
 private void setupNotificationChannel(String channelId) {
 NotificationManager mNotificationManager = (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE);

 // The user-visible name of the channel.
 CharSequence name = getString(R.string.my_channel_name);

 // The user-visible description of the channel.
 String description = getString(R.string.my_channel_name);

 int importance = NotificationManager.IMPORTANCE_LOW;

 NotificationChannel mChannel = new NotificationChannel(channelId, name, importance);

 // Configure the notification channel.
 mChannel.setDescription(description);

 mChannel.enableLights(true);
 // Sets the notification light color for notifications posted to this
 // channel, if the device supports this feature.
 mChannel.setLightColor(Color.RED);

 mChannel.enableVibration(true);
 mChannel.setVibrationPattern(new long[]{100, 200, 300, 400, 500, 400, 300, 200, 400});

 mNotificationManager.createNotificationChannel(mChannel);
 }

 /**
 * Source: &lt;a href="https://stackoverflow.com/a/39589149/2848676"&gt;https://stackoverflow.com/a/39589149/2848676&lt;/a&gt;
 * @return true if the app is in the background, false otherwise
 */
 private boolean appIsInBackground() {
 ActivityManager.RunningAppProcessInfo myProcess = new ActivityManager.RunningAppProcessInfo();
 ActivityManager.getMyMemoryState(myProcess);
 boolean isInBackground = myProcess.importance != ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND;
 return isInBackground;
 }

 @Override
 public boolean onStopJob(JobParameters params) {
 // returning true schedules the job for retry (we're using it to implement periodicity since
 // JobInfo.Builder.setPeriodic() didn't work
 return true;
 }
}
</code></pre>

blocks|key|22297|text|首先，WorkManager用于可以推迟并需要保证执行的工作。考虑到向后兼容性，JobScheduler只能在23%2B接口上工作。为了避免必须处理向后兼容性，WorkManager会为您做这件事：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|22298|​|22299|📷|atomic|22300|22301|工作管理器的功能|22302|google+play保证，约束感知的execution|22303|Respect系统后台restriction|unordered-list-item|22304|
|22305|Quarreable，您可以检查状态，例如失败、成功、工作(例如etc|22306|22307|Chainable，-A依赖于工作)-B+google|22308|22309|+graph|22310|22311|Opportunistic，尝试在满足约束时立即执行，而实际上不需要作业调度程序进行干预，例如，如果您的进程正在运行且与running|22312|22313|Backward兼容，则唤醒应用程序或等待JobSheduler批处理您的工作，无论是否使用play|22314|+->+|22315|22316|22317|WorkManager提供了回到API14级的兼容性。WorkManager根据设备API级选择适当的方式来调度后台任务。它可以使用JobScheduler+(在API23和更高版本上)或AlarmManager和BroadcastReceiver的组合|22318|引擎盖下的扩展架构|22319|22320|22321|22322|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6b4064d53ee0575a2db9765e089f7156.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/b7c9db71ada131e277a8929844006842.png^0|3|B|14|C|0|0|0|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|L|B|0|0|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|20|8|@]|D|@$9|21|A|22|1|23]]|E|$]]|$1|K|3|G|5|6|7|24|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|25|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|26|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|27|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|28|8|@]|D|@]|E|$]]|$1|U|3|V|5|R|7|29|8|@]|D|@]|E|$]]|$1|W|3|T|5|6|7|2A|8|@]|D|@]|E|$]]|$1|X|3|Y|5|R|7|2B|8|@]|D|@]|E|$]]|$1|Z|3|T|5|6|7|2C|8|@]|D|@]|E|$]]|$1|10|3|11|5|R|7|2D|8|@]|D|@]|E|$]]|$1|12|3|T|5|6|7|2E|8|@]|D|@]|E|$]]|$1|13|3|14|5|R|7|2F|8|@]|D|@]|E|$]]|$1|15|3|T|5|6|7|2G|8|@]|D|@]|E|$]]|$1|16|3|17|5|R|7|2H|8|@$9|2I|A|2J|B|C]]|D|@]|E|$]]|$1|18|3|19|5|R|7|2K|8|@]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|2L|8|@]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|2M|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|2N|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|2O|8|@]|D|@]|E|$]]|$1|1G|3|G|5|6|7|2P|8|@]|D|@]|E|$]]|$1|1H|3|I|5|J|7|2Q|8|@]|D|@$9|2R|A|2S|1|2T]]|E|$]]|$1|1I|3|G|5|6|7|2U|8|@]|D|@]|E|$]]|$1|1J|3|-4|5|6|7|2V|8|@]|D|@]|E|$]]]|1K|$1L|$5|1M|1N|1O|E|$1P|1Q|1R|-4]]|1S|$5|1M|1N|1O|E|$1P|1T|1R|-4]]]]

First, <code>WorkManager</code> is used for work that can be deferrable and require guarantee execution. With backward compatibility in mind <code>JobScheduler</code> only works on API 23+. To avoid having to work on backward compatibility WorkManager does that for you:-

<a href="https://i.stack.imgur.com/PJtpb.png" rel="noreferrer"><img src="https://i.stack.imgur.com/PJtpb.png" alt="enter image description here"></a>

Features of work manager

<ul>
<li>Guaranteed, constraint aware execution</li>
<li>Respect system background restriction</li>
<li>Quarreable, you can check status i.e. failed, success, etc</li>
<li>Chainable, eg work-A depend on work-B -> Work graph</li>
<li>Opportunistic, try best to execute as soon as constraints are met, without actually need job scheduler to intervene i.e wakeup the app or wait for <code>JobSheduler</code> to batch your work if your process is up and running</li>
<li>Backward compatible, with or without google play service</li>
</ul>

WorkManager offers compatibility back to API level 14. WorkManager chooses an appropriate way to schedule a background task, depending on the device API level. It might use JobScheduler (on API 23 and higher) or a combination of AlarmManager and BroadcastReceiver

The extended under the hood architecture

<a href="https://i.stack.imgur.com/OSfP5.png" rel="noreferrer"><img src="https://i.stack.imgur.com/OSfP5.png" alt="enter image description here"></a>

blocks|key|20795|text|在谷歌文档中，WorkManger是之前所有后台任务的推荐位置，包括FirebaseJobDispatcher、GcmNetworkManager和作业调度器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|20796|请参阅：https://developer.android.com/topic/libraries/architecture/workmanager|offset|length|20797|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/topic/libraries/architecture/workmanager^0|0|4|1Y|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

In Google docs, WorkManger is a recommended placement for all previous background tasks, including FirebaseJobDispatcher, GcmNetworkManager, and Job Scheduler.

see: <a href="https://developer.android.com/topic/libraries/architecture/workmanager" rel="nofollow noreferrer">https://developer.android.com/topic/libraries/architecture/workmanager</a>

Why do we need the new Android <a href="https://developer.android.com/topic/libraries/architecture/workmanager" rel="noreferrer">WorkManager</a> if we already have a <a href="https://developer.android.com/reference/android/app/job/JobScheduler" rel="noreferrer">JobScheduler</a> along with a few nifty backports (<a href="https://github.com/evernote/android-job" rel="noreferrer">AndroidJob</a> and <a href="https://github.com/firebase/firebase-jobdispatcher-android" rel="noreferrer">FirebaseJobDispatcher</a>) with the same functionality? Does it have any killer-features or something? Because I don't see anything that makes me want to migrate to the yet another scheduler.

Android WorkManager vs JobScheduler

如果我们已经有了 和一些具有相同功能的漂亮的后端口(和)，为什么我们还需要新的Android 呢？它有什么杀手级的功能吗？因为我没有看到任何让我想要迁移到另一个调度器的。

问安卓WorkManager vs JobScheduler
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓WorkManager vs JobSchedulerEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓WorkManager vs JobScheduler
EN