I currently work on Windows, where our team focuses on making your PC experience more powerful and delightful with AI, while also scaling new tooling across the studio.
I'm a self-taught designer with an engineering background, specializing in simple and effortless experiences for both the devices we use today and the ones we'll use in the future. Crafting high-quality products that people love to use is my passion, and I work tirelessly to achieve that goal.
Using the medium of motion and rapid prototyping I bring these experiences to life, visualizing the smallest interactions to entire user journeys. I strongly believe in open design, and encourage co-creation that can help deliver a better solution for users.
Accessibility and inclusion sit at the center of my process — technology should empower everyone and nobody should be left with a subpar experience.
I'm currently a Senior Designer at Microsoft, where I currently work on Windows AI.
Previously a Design Intern at Microsoft, where I was involved with products used by millions of people around the world. Check them out: Surface Duo, SwiftKey, Fluent Icons. Before that, I worked independently on critically acclaimed concepts both by myself and friends.
BSc Computer Science graduate — First Class Honours.
Awarded 2018-19 Microsoft MVP (Most Valuable Professional) for Windows Design.
Surface Duo asked an unusual question of every team designing for it: what does your product become when there's a second screen?
I joined SwiftKey as a design intern in the lead-up to Duo's launch and worked on adapting the keyboard to a form factor where input conventions hadn't been established yet. Input is one of the most consequential surfaces on a phone. When it's wrong, the rest of the device feels broken. And a dual-screen device gives a keyboard more places to live than it knows what to do with.
Surface Duo is the result of years of Surface design and research. Pictured with Surface Slim Pen and Surface Earbuds.
The modes
The team designed for three primary states:
Single-screen, tailored. The keyboard runs on one screen as a regular Android keyboard would, but anchored to the side the user's hand is on. The keys sit under the thumb without forcing a reach across the whole panel.
Split. A single keyboard spread across both screens, with each half landing under each thumb when the device is held in dual-screen portrait.
Compose. When the device rotates, one screen becomes a full-bleed typing surface with a much larger key area, while the active app sits on the other screen above.
Each mode is a layout problem and a transition problem. The keyboard has to know which mode it should be in given how the user is holding the device, and it has to switch between them without disrupting the typing flow.
SwiftKey in compose mode on Surface Duo.
Compose mode
Compose mode raised two problems worth working through.
The first was layout. With that much real estate, key positions can't be a function of the screen geometry alone. They have to land where the user's fingers actually settle at typing speed. A larger key array isn't automatically better; keys can sit too far apart, or fall outside the natural reach envelope, in ways that hurt typing speed compared to the standard layout it replaces. Our human factors partners helped drive positioning decisions here, and we iterated against their findings.
The second was technical. Compose mode covers an entire screen with the keyboard and Android needed to handle that gracefully. The app the user is typing into is on the other screen, and the layout below the keyboard had to keep working without anything breaking when one of the screens was effectively occluded by the input surface.
SwiftKey on Surface Duo being used to reply to a message.
Research
The team invested heavily in understanding how people actually held and used Duo: internal selfhosting across Microsoft, human factors studies, and other research sessions. Every layout call traced back to it: where the keyboard anchors in single-screen mode, the geometry of the split layout, the key positions in compose. The form factor was novel enough that design intuition alone couldn't be trusted.
Beyond the keyboard
I used the internship as a chance to go further than the keyboard and sketch what other software on this hardware could feel like, such as a weather app that treats the second screen as a deliberate surface for context the user wants to keep visible rather than just a wider canvas.
Two apps on Surface Duo, one on each screen — Spotify and Outlook.
Working alongside the Surface design team taught me how much of the feel of a new device comes from the seam between hardware and software being designed in the same room, not handed across one.
2020
SwiftKey Design System
Rebuilding SwiftKey's Figma libraries after the Surface Duo redesign.
I joined Microsoft SwiftKey just as the Android app was going through a significant redesign in the lead-up to Surface Duo with a more minimal UI direction, and a new set of components and layouts that would ship on regular Android too. The Figma library hadn't kept up.
Components were visually wrong against the new design, structurally missing the Duo additions, and scattered across multiple files. The base widths were also an arbitrary number that didn't match the 360px standard the rest of Fluent mobile was working to, which made cross-team reuse painful.
Duo was the forcing function. We had just done all the redesign work; now was the moment to centralize it.
I led the rebuild on the Android side, working alongside the designer who owned iOS. Together we also scaffolded the cross-platform foundations: color, typography, and the shared primitives each platform library consumed. This let us move on the platform-specific libraries in parallel without stepping on each other.
Rebuilding against the product
Keyboard panel buttons from the Android component library.
The Android library covers the keyboard surface itself and the settings app around it. Both needed rebuilding from scratch to match what was actually shipping, including the new layouts and controls Duo had introduced.
The library scales to hundreds of components and styles.
The rebuild was also a chance to adopt the Figma features that hadn't existed when the team first set the library up. Auto Layout was the biggest shift: components hold their visual correctness automatically as content changes, so designers stop manually nudging headers and icons to keep a screen looking right. The cost is the up-front rigor of structuring every component properly. The payoff is screens that stay aligned to the source of truth without constant tending.
Theming as a system
The keyboard's whole identity is themable, and the library had to make that fast.
Color styles, typography ramp and components are all neatly organized to make it quick and easy for our designers to get going.
Every keyboard component is built off a small set of core variables: surface colors, accent colors, key shapes. Updating a theme is a matter of changing those in one place rather than touching every component on every screen. By duplicating the library, a designer can scaffold an entirely new theme in minutes and iterate inside Figma before committing to building it in our internal theming tool to see it on device.
Iconography
Our design language contains all of the Fluent Icons needed for SwiftKey.
As part of the alignment work, SwiftKey adopted a custom thin weight of Fluent Icons, drawn specifically for the keyboard's lighter visual register. That work is covered in more depth on the Fluent Icons page.
Fluent Icons are Microsoft's monoline icon set. They're built from the metaphors of the older MDL2 family the Windows team had used for years, but with rounded corners, end-caps, and a hand-tuned ramp from 16 to 48 units. They complement the broader Fluent Design System and the full-color app icon work happening in parallel across Office, Windows, and other product teams.
I was part of a team spanning designers from across the company that laid the groundwork for this icon system. We were able to quickly scale the system from a handful of icons to thousands over a few months. Using an agile approach we were able to release new icons every week, prioritizing icons for teams that needed them immediately.
Why thin
The default Fluent stroke is 1.5px at 24×24. That weight clashed for Microsoft SwiftKey. Our themes used a much lighter visual register, and the typography across the keyboard was tuned to match. Dropping 1.5px icons directly into the keyboard looked visually off; they were heavier than the surface they sat on.
Solving that locally inside SwiftKey would have meant a much broader redesign across themes, type, and component density. But we could approach the problem from upstream instead, with a new weight in the icon system itself sitting alongside outline and filled, and also available to any team facing the same problem.
Drawing the system
Working with the rest of the Fluent Icons team and the central Design System Studio, we set the rules for the new weight: naming, modifier behavior, the relationship between thin and the heavier weights. I drew a lot of the lightweight glyphs across the size ramp through to the end of my internship, rebuilding strokes from the existing outline geometry to 1px and re-tuning corners and end-caps for the lighter register. I also helped with drawing icons at the regular and filled weights.
The size ramp and outline vs. filled states.
The hard part wasn't any single glyph, but instead holding pixel-grid alignment at 1px while staying harmonious with the heavier weights and making sure that outline → filled transitions still felt continuous. Fluent uses the filled state to indicate selection in some surfaces, so a jarring weight change on tap could have broken the interaction.
A small subset of the available modifiers.
The modifier system — affixes like a plus or close mark in a consistent corner of the parent glyph — had to survive at thin too. A 1px modifier reads very differently from a 1.5px one at small sizes, and the rules for how the parent glyph cedes space needed to adapt without breaking the spatial conventions users had already learned.
Where it ended up
Thin started as a SwiftKey-shaped problem. It didn't stay one. Other teams began to pick up the lighter glyphs at certain sizes for the same reason. Their interface needed a lighter register than the default weight allowed. And from there thin became part of the standard system, available to anyone who needed it.
Examples of Fluent Icons in Yammer on iOS and Outlook on Android.
The broader system scaled the same way. What began as a mobile icon set picked up desktop adopters with Microsoft Edge among the first, and later Windows 11. A new 20px size was hand-drawn specifically so the icons could replace existing 16px MDL2 assets in dense desktop UI without losing legibility at the swap.
One-handed navigation and feature parity with Edge on desktop.
Not affiliated with Microsoft
Microsoft Edge for iOS redesign isn't affiliated with Microsoft. Concepts and mockups shown do not represent any product plans past, present, or future.
2019
Cortana OS
A gestural, assistant-first alternative to what Windows Lite could be.
Not affiliated with Microsoft
Cortana OS isn't affiliated with Microsoft. Concepts and mockups shown do not represent any product plans past, present, or future.
2018
Microsoft Store Content
Reimagining the Microsoft Store with a new featured apps layout and improved editorial content.
Feature completeness and tighter integration with the Windows surfaces around it.
Not affiliated with Microsoft
Your Phone redesign isn't affiliated with Microsoft. Concepts and mockups shown do not represent any product plans past, present, or future.
2018
Podcasts app concept
A Fluent-native first-party podcasts app for Windows.
Not affiliated with Microsoft
Podcasts app concept isn't affiliated with Microsoft. Concepts and mockups shown do not represent any product plans past, present, or future.
2018
Redesigning navigation for Windows 10
Designing the navigation and management patterns that make Sets a system.
Not affiliated with Microsoft
Redesigning navigation for Windows 10 isn't affiliated with Microsoft. Concepts and mockups shown do not represent any product plans past, present, or future.
2018
Fluid Desktop
Redefining the Windows desktop experience with a new look, refined apps, and improved Cortana intelligence.