# Live Location - not for production use

**URL:** <https://community.glideapps.com/t/live-location-not-for-production-use/26227>\
**Category:** Project Showcase\
**Created:** [April 30, 2021, 3:07pm UTC](https://community.glideapps.com/t/live-location-not-for-production-use/26227 "2021-04-30T15:07:02Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [April 30, 2021, 7:32pm UTC](https://community.glideapps.com/t/live-location-not-for-production-use/26227/7 "2021-04-30T19:32:13Z")

</div>

Hehe, no, I’m not going to ask. Purely based on the response below. If Glide wanted to allow us to obtain a user’s location unprompted, I’m sure they would have given us that option. Totally understandable too. It would be way to easy to hide a location grab within a custom action. Like I said above, it’s using my current location to obtain my current location, so it’s a bit pointless in theory, although it would be awesome to skip the location switch, it does start to get into some scary territory of user tracking.

> [@compass Location Component](https://community.glideapps.com/t/location-component/10976/9):
>
> I’m guessing the intention is to make the user aware that their location is being obtained, so it’s a switch as opposed to automatically obtaining the location behind the scenes like the special values do.

> [@compass Location Component](https://community.glideapps.com/t/location-component/10976/10):
>
> Correct.

---

_[View the full topic](https://community.glideapps.com/t/live-location-not-for-production-use/26227)._
