# Attendance App Without Barcode – Looking for Ideas to Avoid High Update Usage

**URL:** <https://community.glideapps.com/t/attendance-app-without-barcode-looking-for-ideas-to-avoid-high-update-usage/82208>\
**Category:** Ask for Help\
**Created:** [June 2, 2025, 10:43pm UTC](https://community.glideapps.com/t/attendance-app-without-barcode-looking-for-ideas-to-avoid-high-update-usage/82208 "2025-06-02T22:43:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 4, 2025, 12:12am UTC](https://community.glideapps.com/t/attendance-app-without-barcode-looking-for-ideas-to-avoid-high-update-usage/82208/3 "2025-06-04T00:12:55Z")

</div>

> [@Radar accuracy issues in Glide](https://community.glideapps.com/t/radar-accuracy-issues-in-glide/81589):
>
> Hi everyone! I’m developing an employee time-tracking app in Glide, where employees are only allowed to clock in if they are physically at their designated workplace. I’m using the native integration with Radar, setting up the Radar - Track Once action, and I have connected the API Key successfully. However, I’ve noticed that the location returned by both Glide and Radar is not precise enough — sometimes it deviates by several meters, or even kilometers, especially indoors. This makes it very…

This thread is related to your use case.

---

_[View the full topic](https://community.glideapps.com/t/attendance-app-without-barcode-looking-for-ideas-to-avoid-high-update-usage/82208)._
