flutter-background-executionlisted

# Flutter Background Execution Treat background execution as an operating-system contract, not a Dart timer that is guaranteed to keep running. Preserve the project's scheduler or plugin when it satisfies the requirement; inspect `pubspec.yaml`, SDK constraints, target platforms, native capabilities, and existing registration before changing it. ## Define the job Record the trigger, acceptable delay, maximum duration, survival across process death or reboot, network/power constraints, user visibility, cancellation, and what should happen after sign-out or data deletion. Separate “must eventually run” from “must run at an exact time”; mobile schedulers are commonly opportunistic. ## Choose the owner - Keep work in `dart-concurrency` when it only needs to run while the app process is alive. - Use an OS-backed scheduler for deferrable work that must survive the visible app. - Use a user-visible foreground or continued-processing mode only when the platform permits the use case and its disclosure, permissions, and limits are satisfied. - Route exact user reminders and notification delivery to `flutter-notifications`. - Route a custom native scheduler bridge or reusable plugin implementation to `flutter-platform-integration`. Do not add a scheduling package by default. Verify platform coverage, maintenance, target SDK support, callback model, and the repository's existing dependencies first. ## Load details conditionally - Read [Android scheduling and services](references/