Modern best practices for background task execution
summary
History of Android background APIs and concrete guidance for downloads and polling WorkManager remains the default down to Android 4 but Android 14 adds a dedicated user initiated data transfer JobScheduler job that requires the run_user_initiated_jobs permission and set_estimated_network_bytes, giving higher priority and reliable long transfers. Time‑sensitive alerts use expedited worker + FCM (high priority) to wake and fetch artwork. Debugging example shows a bug that exhausts quota and lands the app in app standby bucket 45 causing periodic workers to stop.
AI-written summary · about
chapters (11)
- 0:00Background task execution intro
- 1:25Android background APIs evolution
- 4:15Broadway app features
- 5:37Choosing API for downloads
- 10:09WorkManager vs JobScheduler
- 12:16User Initiated Data Transfer jobs
- 18:32Lottery alerts with FCM
- 27:41Tracking price drops and seats
- 29:28Debugging worker execution
- 36:07App standby bucket limits
- 38:14Summary & Q&A
related talks
28mBest practices for running background work on Android
23mUser Initiated Data Transfer Jobs
50mWTF with Android Background Restrictions
11mEffective background tasks on Android
36mBackground Work in Android: Strategies and Best Practices
37mA guide to using foreground services and background work in Android 14
31mAndroid Jetpack: Easy background processing with WorkManager
45mWorking background with WorkManager API
