OneTimeWorkRequest vs PeriodicWorkRequest and minimum repeat interval
Tests WorkManager scheduling constraints and battery tradeoffs. Contrast one-shot chaining with non-chained periodic work, cite the 15-minute minimum, and tie it to system batching under Doze and App Standby. Red flag: claiming exact intervals or no minimum.
Tests deep familiarity with WorkManager API boundaries and Android battery architecture. A strong answer distinguishes OneTimeWorkRequest as a single execution unit that supports dependent chains and retries, versus PeriodicWorkRequest as a repeating task that cannot be chained. It states the 15-minute minimum repeat interval and explains that the limit exists so the OS can batch background work across apps, aligning wakeups with Doze and App Standby windows rather than honoring exact alarm-style timing.
Read the original → developer.android.com
- #android
- #workmanager
- #background-work
- #battery-optimization
- #jetpack
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.