I built reusable Android components at Microsoft and worked on accessibility, UI testing, and releases for the Fluent library.
Explore the UI ↘Fluent is Microsoft’s design system. It gives teams shared components and patterns for building interfaces across products such as Word, Outlook, and Teams.
Fluent UI Android brings that language to mobile through reusable native components, working alongside Android’s Material controls.
These are examples of the broader Fluent ecosystem. I worked on the shared Android library. About Fluent ↗
My work spanned cards, lists, people selection, progress indicators, dialogs, and more. Explore a few of those patterns below.
Who’s joining the project?
I built PersonaChip and PeoplePicker, including selection, validation, and customization for different products.
Everything you need for the next step.
I implemented basic, file, and announcement cards with reusable layouts and styling tokens.
Your workspace is ready.
I built progress indicators, Shimmer, and ProgressText, and fixed rendering issues in loading states.
Readable content. Room to grow. A clear action.
Try the larger-text setting.
I fixed clipped text at larger font sizes, improved TalkBack announcements, and corrected how read-only fields were described to screen readers.
These web demos recreate patterns I worked on, using Fluent 2 styling. They are not screenshots of Microsoft products.
I gave teams components they could configure and reuse, with examples to help them integrate the library.
My fixes improved large-text layouts, screen-reader feedback, and right-to-left behavior in shared controls.
I integrated Hydra Lab UI testing, added regression coverage, and automated parts of localization and releases.
I enjoyed working on both the components and the tooling that helped other engineers use them.
A fix in a shared library can help several teams at once. That made accessibility and testing especially rewarding.
More of my work ↗