Mobile ERP — Private Workforce Management App

Overview

Mobile ERP was built for a private client, so I do not publish the full client context or a public store link. What I can talk about is the product problem: making attendance, leave, shifts, and payroll access work cleanly on mobile without turning location-based check-ins into something easy to spoof or abuse.

The app was designed for day-to-day workforce operations. Employees needed a simple mobile flow to check in, view schedules, request leave, and access payroll information. On the other side, the business needed stronger trust in attendance records, especially because it operated across multiple branch stores. Each branch had its own employees and its own attendance point, so the app needed to allow check-ins only when someone was physically within the allowed radius of their assigned branch, for example within 50 meters of a store location.

My Role

I worked on the Flutter mobile app and focused on the parts where workforce operations and mobile constraints meet.

My work included:

Building the mobile attendance and workforce flows for employees
Handling geofenced check-ins, location validation, and proof-of-attendance UX
Supporting shift visibility, leave requests, and payroll-related access from the same app
Shaping the mobile structure so the operational flows stayed consistent instead of becoming a set of disconnected forms

This was less about flashy product behavior and more about reliability. The app had to hold up in real usage, where bad check-in logic or confusing employee flows would create operational problems immediately.

What Mobile ERP Does

The app gives employees mobile access to the main workforce actions they need during regular work operations.

They can sign in, check in and out, see their assigned shifts, request leave, upload supporting documents when needed, and access payroll information from their phone. The goal was to reduce the friction around everyday HR operations without making the app feel heavy or difficult to use.

Attendance was the most sensitive part. Check-ins were tied to geofenced locations, and the app also needed to support selfie-based proof so presence could be validated more credibly than a simple button tap.

Key Decisions

A few decisions shaped the app.

First, I treated attendance integrity as the core product concern. A workforce app can have useful secondary features, but if check-ins are unreliable, the whole product loses trust quickly. That is why geofencing, location handling, and spoofing resistance mattered more than cosmetic complexity.

Second, I kept the mobile flow straightforward for employees even when the rules underneath were stricter. The app needed to enforce location boundaries and proof requirements without making basic actions like check-in, leave requests, or shift visibility feel burdensome.

Third, I treated the app as an operational tool rather than a consumer-style experience. The right measure of success here was not novelty. It was whether the app reduced confusion, supported attendance rules more credibly, and gave employees a clear mobile path for routine administrative work.

Challenges

The hardest part of the project was balancing usability with enforcement.

Location-based attendance sounds simple until it becomes real. In this case, the client had many branch stores, and attendance had to be blocked outside the allowed radius of each branch. That meant the app could not treat location as a soft suggestion. It had to determine whether an employee was inside a valid attendance zone, such as within 50 meters of Branch A, and reject the action outside that boundary.

Once that becomes the rule, a lot of edge cases appear. GPS can drift, users can arrive near the edge of the radius, and the business still wants stronger confidence that a check-in actually reflects presence. That meant the app had to combine geofencing, device/location checks, and proof flows without making the experience feel brittle.

There was also a broader operational challenge: this was not one isolated attendance screen. Check in, shifts, leave, and payroll all had to feel like parts of one employee tool. If the app solved only the attendance problem but left the rest of the workforce flow fragmented, it would still feel unfinished in practice.

Impact

Mobile ERP is meaningful because it addressed a real business workflow, not a showcase feature set.

The app gave employees a more direct mobile path for attendance, shift visibility, leave requests, and payroll access. It also gave the client a stronger structure around mobile check-ins by tying them to branch-specific location rules and proof-of-attendance expectations instead of relying on a looser manual process.

Because this was a private deployment, I do not frame the result in public growth metrics. The stronger claim is simpler: it was a real operational app, built around everyday workforce needs, and the engineering work mattered most where trust and routine usage intersected.

What I Learned

This project reinforced that enterprise mobile work often looks simpler than it really is.

On the surface, attendance, leave, and payroll access can sound like standard admin features. In practice, the difficulty is in making those flows trustworthy enough for the business while keeping them clear enough for employees to use every day without friction.

It also reminded me that private-client products need a different kind of case study. The most important part is not public proof or launch optics. It is showing the operational problem clearly, explaining the constraints honestly, and being precise about where the mobile app had to carry real responsibility.