Taking the Project ERP to the Site: Designing a Field First Mobile Companion for Tasks, Attendance, and Site Communication on iOS and Android

ANJ Group is one of India's largest design and build firms, delivering workplaces for Accenture, Microsoft, Hitachi, and Allianz through integrated manufacturing, technology, and execution. The firm has transformed over 110 million sft across more than 3,000 projects in 60 cities, with a 2,500 strong workforce. Its project ERP ran on office desktops. The work ran at the site gate, on the floor, and at the factory dock.

As Product Designer, I designed the mobile companion that carries the ERP into the field: attendance, tasks, project tracking, documents, leads, and site chat in 1 application shipped identically to iOS and Android. The scope covered the full arc: flow map, information architecture, a design system at v1.0, and a completely tappable prototype running on real project data.

The organizing rule was set before any screen existed: a 5 slot bar carries the whole product, nothing sits deeper than 2 taps, and work commits where it happens.

22 screens, 6 flows, 1 design frame for 2 platforms.

How might we give site staff read and write access to the project ERP from where the work happens, so the system of record stops trailing the site by days?

Before the app, a clock-in was a phone call to the office. A closed snag was a photo in a chat thread that someone retyped into the ERP 2 days later. A dispatched truck was news the site heard when it arrived. The system of record ran behind the site, and the client, invited into that ERP for transparency, saw the lag first.

I delivered a complete mobile product definition: 22 screens across 6 flows, an information architecture with a 2 tap ceiling, a documented design system, and an interactive prototype on real project data, all from 1 design frame that ships unchanged to both platforms.

I led the work end to end, from the flow map through the interactive prototype, with the ERP team as the source of truth for entities, statuses, and permissions.

The sequence was deliberate: map every flow lo-fi first, fix the information architecture, write the design system, then assemble the high fidelity screens. Because the structure was settled early, the hi-fi phase was assembly rather than invention, and dead ends were caught while they were still cheap to fix.

From a desk bound record to a pocket sized one

The ERP already held the entities: projects, tasks, attendance records, documents, leads, and team roles. The app does not duplicate them. It exposes the 4 things field staff actually create, a task, a clock-in, a document, and a lead, and the reading surfaces they need to act: today's tasks, the live project, the site room, and the weekly numbers.

Every write is designed to land in the ERP in the same gesture. A checked task updates counts, the dashboard, and the reports. A clock-in carries the site and a geo tag. An uploaded drawing arrives versioned. The client invited into a project sees progress and milestones as they happen, not a week later.

Everything within 2 taps of the bar

1 five slot bar carries the whole application: 3 destination tabs, a task hub, and a raised create action in the center. Drill-ins push full screen over the bar; back is always 1 gesture. The create action feeds every branch: a task, a clock-in, a document, or a lead is 1 thumb away from any screen.

6 flows, mapped before a pixel of hi-fi

Every screen was wireframed and wired lo-fi first. The 6 flows below cover a field day end to end; the first 3 carry most of it.

1 language for 2 platforms

Purple acts, neutrals read, and semantic tints stay in chips and badges without ever becoming a surface. Native system type, SF Pro on iOS and Roboto on Android, keeps both platforms feeling at home in the same layout with 0 webfonts. The values below are the ones the prototype runs on, rendered live rather than screenshotted.

The screens, and why they are this way

4 decisions carry most of the product. Each one is annotated on the coded screen it lives on.

The rest of the system follows the same rules: a task's full record, the site room where a dispatch lands next to the work it belongs to, and the weekly review numbers.

Takeaways