Office seat management sounds unglamorous. But spend a day in a mid-sized company without a system for it and you quickly realize how much invisible friction it creates. Who's sitting where? Is this meeting room free at 2pm? Where is the project team clustered today? These questions have real answers — they just need a tool that surfaces them clearly.
Huber Usha was that tool. I spent four months as part of the team building a React Native application that let staff plan project meetings, reserve seats, and manage office space without the usual back-and-forth.
What I Worked On
I led a significant part of the application interface design — thinking through how staff would actually use the app in a real workday. Speed matters in this context. Nobody wants to spend three minutes booking a seat. The interface had to be clear, fast, and require minimal learning curve regardless of how tech-savvy the user was.
The API integration connected the seat management system to the organisation's existing tools, keeping reservations, availability, and scheduling data consistent across platforms. A system like this only works if the data it shows is trustworthy — keeping that communication smooth and reliable was non-negotiable.
Shipping It
Like Fingo before it, Huber Usha made it to the Google Play Store — my third production deployment as part of a professional team. Each one taught me something slightly different. This one reinforced how important edge case handling is when real employees with real schedules are depending on the app to be accurate.
What Four Months Here Taught Me
Internal tools have a different design pressure than consumer apps. Your users didn't choose your app — it was chosen for them. That means the bar for clarity and reliability is actually higher, not lower. People will forgive a clunky consumer app. They won't forgive an internal tool that makes their workday harder.
This was a private company project — code and screenshots remain confidential.