# Live Location - not for production use **URL:** \ **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:** 24
**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 2, 2023, 3:47am UTC](https://community.glideapps.com/t/live-location-not-for-production-use/26227/24 "2023-04-02T03:47:35Z")
It was a fun challenge and I had it pretty accurate and able to dynamically move the 3 points, so the tri-lateration always kept up and I always had an accurate location because I would always be within the 3 points. The only problem is, I think glide has a bug somewhere where javascript crashes and can’t recover, so the app would halfway stop responding after a few minutes. I had put Try Catches in the code, but there would still be a hard crash somewhere. Now, the newer Location component in glide will dynamically track your live location, so my code isn’t really needed anymore. I’ve since created a new version that uses the new Glide Apps. It’s a lot simpler and more stable. I also have it calculating a bearing from target to destination and I’m close to having it accurately calculate live speed and compass bearing of the user. Some Glide limitations are getting in the way, but I think I have an idea to get past that. If I use this for anything, it will be geocaching, but other than that, it’s just a fun project to see what I can do with complex math. ![Screenshot_20230401-223559](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/9/499135c0b327a2238548bec6a1eeaa7b982a3c9e.jpeg) --- _[View the full topic](https://community.glideapps.com/t/live-location-not-for-production-use/26227)._