Mission Report · MapMyIndia [Gtropy]Project case study
Hermes
Internal tools get judged by the people who have no choice but to use them. That is a harder audience, not an easier one.
- Status
- Shipped
- Owned
- Frontend · design system
- Audience
- Internal
- Stack
- React
- TypeScript
ResultsNot yet measured
- Time per data task
- Errors per batch
An internal logistics and data management tool.
An internal logistics and data management tool. Its users could not choose another product, which makes them the most honest audience there is.
Internal operations staff.
Internal tools accumulate inconsistency, with every screen built by whoever needed it that week. The first job was a component library, so that the next screen would look and behave like the last.
A modular, consistent, accessible interface for daily internal operations and data management.
If the components are consistent and accessible by default, every new screen inherits both, and the tool stops needing a redesign each year.
A reusable component library in React with Tailwind CSS, designed in Figma first, with accessibility and responsive behaviour built into the base components.
The components used on every screen first, then the workflows operations staff run most often, then data visualisation.
Accessibility was treated as a requirement, not a pass at the end.
Modular, component-driven UI.
React, Next.js and Tailwind CSS; Figma for the design system source.
Component-driven UI, consistent design patterns, accessibility standards maintained throughout.
A consistent, accessible internal interface built on a reusable component library.
Internal tools are where a design system pays for itself fastest: the audience is small, the screens are many, and nobody forgives inconsistency they have to live in every day.