I’m implementing an app widget which contains some text and a button, the text needs to be updated whenever a button is pressed. The data for the text comes from a weather api, so I need to perform the update action in a service. 

My current flow is as follows:

1. In onUpdate of the WidgerProvider I set the OnClickPendingIntent
2. This pending intent is handled in the onReceive method of the same WidgetProvider and calls enqueueWork of the service.

My questions are, 

1. Do you think that this flow is acceptable? Given that widget provider is handling the pending intent, which also means that enqueue work is called when the widget is first added.
2. Is JobIntentService a good choice in this case? Given that it does not guarantee that the job is executed straight away. I know that a simple service or IntentService is not an option, I also considered a WorkManager, but then read your article about it producing an infinite loop….

/**
 * A {@link DataSource} that reads and writes a {@link Cache}. Requests are fulfilled from the cache
 * when possible. When data is not cached it is requested from an upstream {@link DataSource} and
 * written into the cache.
 *
 * <p>By default requests whose length can not be resolved are not cached. This is to prevent
 * caching of progressive live streams, which should usually not be cached. Caching of this kind of
 * requests can be enabled per request with {@link DataSpec#FLAG_ALLOW_CACHING_UNKNOWN_LENGTH}.
 */