| Product | My role | Platform | Result |
|---|---|---|---|
| DSOL, the internal jobs + HRM app for Designing Solutions (telecom · GIS · survey) | Sole product designer: UI, UX and the full flow. Built by the in-house dev team. | iOS + Android, shipped | 110+ employees daily · 5 to 6× a day for office staff · 20+× a day for field crews |
I am Designing Solutions' designer. I had already designed and built their three websites (main site · IT site · marketing site), so I knew the company and how its field teams actually work. That is why the app's full UI, UX and flow came together in about two weeks.
<aside> 🖼️
Drop the app hero here: the sign-in screen or the home screen with the greeting.
</aside>
Designing Solutions is a 19-year telecom, GIS and survey company (fiber planning, mapping, CAD) with crews out on sites for clients like Airtel and Jio, plus office staff and management back at base. They wanted one internal app for all of it: survey jobs, attendance, leaves, expenses, company bikes, travel hotels, holidays, documents, events. The catch is that a field surveyor, an accountant and a manager barely use the same three screens. Build a tab for every module and everyone drowns. Build a separate app per role and you maintain several. The real problem was one app that fits every kind of employee at once.
The answer was not more tabs, it was fewer. The bottom bar holds four: Home, Jobs, Attendance, Profile. Everything else lives one tap away in a Quick Actions hub on the home screen (Attendance, Joint Visit, Jobs, Expenses, Bike, Leaves, Hotel, Gallery), with a grid or list toggle for preference. A surveyor lands on one screen and reaches anything in a tap, with no wall of navigation. The thing employees mention most is that it is very easy to navigate.
<aside> 🖼️
Drop the home screen here, ideally the grid and list versions of Quick Actions side by side.
</aside>
Different roles get different access. The obvious move is to hide what you cannot use, but that leaves a new intern staring at a near-empty app. So I did the opposite: routes you do not have access to still appear, greyed out and non-clickable. Everyone sees the whole map of the tool, and access simply lights up what is theirs. One app scales from an intern with only Leaves and Attendance to a manager with everything, and it never feels broken or empty.
The company's real worry was fake and proxy attendance from the field. So attendance is designed to make presence provable: it fetches your live GPS location first, then requires a selfie, both mandatory. You cannot clock in unless you are provably at the site and provably yourself. It turns a trust problem into a two-step nobody can game.
<aside> 🖼️
Drop the attendance screens here: clock-in and clock-out with the selfie + location.
</aside>
The modules that matter most are built around how survey crews actually work: