The role

One design system and five applications — three consoles and two field apps — designed for people who may not read fluently, on inexpensive handsets, in bright sunlight. The honest measure of your documentation is how many clarifying questions you receive.

Key responsibilities

Own the design system: components, tokens, type scale, spacing and states
Design the five applications, mobile-first for the field and dense for the consoles
Ship an interim icon and asset set first, so releases are never waiting on art
Own the rural-first interaction rules, fed by what the field engineers actually observe
Verify contrast and touch targets rather than assuming them, and check layouts on the real station tablet
Test with real farmers and pilots, and change your own work when somebody taps the wrong thing

Eligibility

Three to five years in product design,



with one design system shipped end to end and then maintained — created is not the same as adopted
Genuine mobile-first work rather than a shrunk desktop layout
Low-literacy or rural interfaces, or a demonstrable appetite for them
Qualified-standard tooling: variants, auto-layout, prototyping and developer handoff
Typography depth, including a non-Latin script

What you get

Five applications and the system beneath them, owned outright
Research access to the actual users, not personas

How the process runs

Fill in the short form on this page.
We read it ourselves. Every application is read.
If we want to meet you, we call you.

📌 UI/UX Product Designer (Chennai)
🏢 https://drone-port.in/
📍 Chennai