Re: [ServiceWorker] Expose GeoLocation to workers (#745)

Where would one badge this in the UI? The API would run in a service worker in the background, so the badge would be the only UI surface. Especially on mobile, screen space is limited. A permanent indicator like a notification might be too much. A tiny icon in the status bar (that cannot be interacted with and has no text) might be too little.

A list of possible UI requirements might be:
* The user can understand what it means
* It is discoverable
* It is not too distracting from other activities
* Attribution: it indicates which origin is using the API
* Permission revocation: the user has a path from the indicator to revoke the permission
* Battery blame (how much was used by this API)
* Does this UI pattern scale to work with other APIs? What if there's a dozen of them?

I don't want to solve the UX in this thread, but I do want to point out that this is tricky. It might not be worth the trouble unless we find more common use cases.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/745#issuecomment-140344440