
Role:
UI Designer
Timeline:
3 Months
Team:
CEO, PM, 3 Engineers
Company:
Simbott Solutions Inc.
Overview:
Simbott solutions built a VR simulator with no platform to navigate before and after the simulator, no shared visual language and no structured way to build it within 3 months.
I built a token-and-component system the developers shipped directly from, designed focus-state-first for a TV-based platform.
My responsibilities:
Map the user flow of the platform
Built and maintained a design system using in Figma.
Collaborate with PM and Engineers to deliver project on time.
Design wireframes and final versions of the platform
Impact:
on development cycle of the platform.
The existing simulator was not centralized to be able to navigate easily.
There was no steady platform built which could hold the simulator.
Engineering team would take more than the allotted time to design and develop the platform from scratch.

Researched how 10-foot devices worked.
Analyzed common interaction patterns.
Mapped out design principles for TV-Screens


Login uses a QWERTY keyboard
Selecting a field auto-focuses the keyboard; Next moves field to field.
10-foot UI
Text and controls have to read from roughly
3 meters away.
D-pad navigation
Components favour a single clear decision, the cleanest way to lower D-pad cognitive load.
Colour means something
Grey and red carry fixed roles across the whole system. Colour is never decorative.
They're built for exactly this constraint: no cursor, no touch, just up, down, left, right, and select.
I checked that pattern against Android TV's own design guidelines rather than relying on it alone.



Colors run on a two-tier variable structure.
Every text size in it is set for legibility at 10 feet, per Android's "10-foot UI" guidance.
Every gap and every radius pulls from 8-point scale.



I organized the file in such a way that mentions the design rules along with the component and its states.
Elements with similar structure were kept together divided into its different states.











I organized the Figma file by component rather than by screen, with each component set showing every state next to its usage notes. Alongside it, I wrote a design-specific document covering when to use each element.


on development cycle of the platform.
Task completion on the sign-in-to-simulation flow, tested with 15 Army officers
See my other projects.


Enterprise
User Research
Redesigned and launched a feedback collection system for service desk employees
reducing workflow time by 67%


Retail
Onboarding UX
Redesign
Designed a new loyalty-program flow with 70% of the non-member shoppers agreeing to sign-up.



