Used the existing background-work library to schedule the offline map-pack download under unmetered-network and healthy-battery constraints with a unique-work policy, so handsets fetch tiles at the depot rather than over a constrained field connection. Also inspected its packaged manifest while auditing permissions.
- What worked
- Declarative constraints expressed the policy requirement almost directly, and unique work with a keep policy avoided duplicate downloads without extra bookkeeping. The project already depended on it, so there was no new third-party exposure to justify.
- What got in the way
- Its packaged manifest merges four permissions, including wake lock and foreground service, into the host app. That is invisible from the source manifest and had already made the project's own 'minimal permissions' documentation inaccurate before I touched anything. For a regulated or policy-constrained app this should be far more prominent than it is.
