ARSAtech

The app opens to a login screen. No guest mode. No demo account. You need credentials issued by ARSA Indonesia to get past the first page. This is not a public utility. It is a work tool built for a specific workforce — the 4,500 employees spread across nine provinces who manage facilities for 300+ clients. The moment you log in, the app asks for location access. That is the first real interaction. Not a tutorial. Not a welcome tour. Just a permission prompt for geo-tagging.

The geo-tag function is the core of this thing. It captures where you are, what you see in a photo, and the exact time you took it. That triple binding — location, image, timestamp — is what makes the reporting chain work. A cleaner in Jakarta takes a photo of a broken window. The app stamps it with GPS coordinates and a timecode. That report goes straight into the system. No manual entry of location. No guessing when the issue was spotted. The data is locked to the physical moment it was collected. That is the entire premise of ARSAtech.

The setup process is where the friction starts. Getting the app installed is straightforward — the APK is available from various mirrors, though the Play Store is the official source. But installation is only the beginning. The app requires Android 6.0 or higher, which covers most modern devices, but the real hurdle is the credentialing. Without an active employee ID and a matching password, the app is useless. This is not a tool you pick up and figure out. It is a system you are dropped into, and the onboarding assumes you already know the workflow.

How geo-tagging and e-forms work together in the field

Here is where the original analysis sits. The geo-tag feature does not exist in isolation. It feeds directly into the e-forms module. When a frontline worker captures a geo-tagged photo, that image becomes an attachment to a digital form. The form is not a free-text box. It is a structured template — likely tied to the specific service type: cleaning, pest control, access control, or landscape maintenance. The form fields change based on what the worker selects. A cleaning report has different checkboxes than a pest control report. But the geo-tag data stays the same across all forms. Location, photo, time. Those three pieces are non-negotiable.

The workflow looks like this: worker arrives at a site. Opens ARSAtech. Selects the service category. The app pulls up the relevant e-form. The worker fills in the required fields — maybe a checklist of tasks completed, maybe a free-text note about an issue. Then the worker taps the camera icon. The app captures a photo and automatically attaches the GPS coordinates and timestamp. The form is submitted. That submission triggers an action tracking entry. The service desk sees it. The Crowd Eye IoT system logs it. The client gets a real-time update if they have access to the client portal. That is the chain. Geo-tag -> e-form -> action tracking -> client visibility. Each link depends on the one before it.

What the Play Store description does not tell you is how rigid this chain is. If the geo-tag fails — poor GPS signal, no camera access — the e-form submission may be blocked. The changelog mentions fixing a "screen whitelist cart escm" issue, which suggests there have been problems with certain screens or permissions blocking the workflow. The app is built for reliability, but that reliability depends on the device working perfectly. A worker with a budget phone that has a weak GPS module is going to struggle. There is no offline fallback mentioned anywhere. No cached submissions that sync later. Everything requires real-time connectivity and functioning hardware.

What the version history reveals about the app's evolution

The version history shows a pattern of incremental fixes rather than feature drops. Version 0.4.5 was released in January 2025 by Mofis Indonesia. That version was 26.9 MB. By August 2026, version 0.8.21 was out at 29.9 MB. That is a 3 MB increase over 19 months. Not a massive size jump. The changelog for 0.8.2 mentions "ARSAtech Locator - Beacon ble integration is here!" That is a notable addition — Bluetooth Low Energy beacons for indoor positioning. The geo-tag system originally relied on GPS, which works outdoors but fails inside buildings. Beacon integration solves that. The app can now locate a worker inside a shopping mall or an office tower using BLE signals. That is a functional upgrade that directly addresses a real limitation.

The changelog for the current version, however, is thin. "Fix some screen whitelist cart escm" is all it says. That is not a detailed update note. It suggests a bug fix related to a whitelist screen — possibly a permissions screen or a device compatibility check. The developer has not published specific details about recent changes. This is common for enterprise apps, but it leaves external users guessing about what actually improved. The beacon integration was announced. Beyond that, the version history is mostly silent on new features.

Comparing the iOS version (40.4 MB) to the Android version (around 29 MB) shows a size difference. The iOS app is larger, which could mean more assets or a different codebase. Both platforms share the same core functionality: geo-tagging, reporting, and facility management integration. But the Android version has more version entries in the public record — 0.2.81, 0.3.46, 0.4.5, 0.6.6, 0.7.46, 0.8.2, 0.8.12, 0.8.21. That is a long tail of updates. Each one presumably fixed something or added a minor tweak. The beacon integration at 0.8.2 is the only major feature shift visible in the changelog.

The real-world performance of the app in the field

There are no public user reviews for this app. That is not a red flag — it is an enterprise app. The users are ARSA Indonesia employees, not general consumers. But the absence of public feedback means the only performance indicators are indirect. The company has 4,500 employees. They use ARSAtech daily. The app is integrated with ISO-certified management systems — ISO 9001, 14001, 45001, and SMK3. That suggests a level of reliability that meets international standards. But standards are about processes, not about app crashes or UI bugs.

The changelog entry "Fix some screen whitelist cart escm" is the closest thing to a bug report. It points to a specific screen issue. Whitelist screens are typically used for device compatibility or permission management. If that screen was broken, some workers may have been unable to proceed past a certain point. The fix would have unblocked them. That is the kind of maintenance work that keeps the app running in a large workforce. It is not glamorous. It is necessary.

The app requests location permissions. That is expected given the geo-tag function. It also shares location data, personal information, and two other data categories with third parties, according to the Play Store data safety section. Data is not encrypted. That is a notable detail. For a facility management app that handles worker locations and service reports, the lack of encryption is a potential concern. The developer states that data is not collected on iOS, but the Android version shares data with third parties. That discrepancy is worth noting.

One specific permission and what it actually does

The app requires location access. That is the only permission explicitly mentioned in the available data. The geo-tag function uses GPS, cell towers, and Wi-Fi to determine position. The app also uses the camera for photo capture. Those are the two core hardware interactions. No claims about battery drain, RAM usage, or network speed are verified in the research. The app runs on Android 6.0 and up, which covers a wide range of devices. The architecture is arm64-v8a, meaning it is optimized for 64-bit processors. The APK size varies by version — 8.46 MB for 0.2.81, 26.9 MB for 0.4.5, 29.9 MB for 0.8.21. The size growth reflects added features and assets. The beacon integration likely added to the size.