Extra Projects
A few other impactful projects I worked on during my time at TWN
Cross-Platform Design
Design Systems
Highway Conditions
Redesigned the highway layer to match the new map system, making it easier to use and consistent across platforms
The Problem
Highway Conditions was one of those products that had evolved in different directions across platforms. The Android app had a redesigned beta from 2021 that used a bottom sheet to display road condition data when users tapped a road segment. Highway Conditions, however, was never released on iOS, it just wasn’t a priority for that team at the time. Meanwhile, the desktop version hadn’t been updated in years. It used older styling, non-interactive road lines, and a static table that sat below the map. Users had to rely on the legend to interpret road colours, with no way to interact with the roads themselves.
The redesign came as part of the broader effort to migrate our maps platform to React and unify the product experience across devices. It was also a chance to finally bring Highway Conditions into the core maps product, so that teams wouldn’t have to maintain separate implementations. The goal was to make it feel like a native part of the new maps experience… same design patterns, same visual language, same interaction model.
I designed a new interaction model where clicking or tapping on a road segment would trigger a floating popup, showing contextual information directly above the map. The design was consistent with other layers like wind and temperature and allowed new highway conditions to scale well across screen sizes.
Results
Redesigned highway conditions to ensure they are available on all platforms, not just Android
Reduced user confusion by replacing outdated, non-clickable map elements with contextual popups
Helped the team retire legacy versions by integrating highway conditions into the new unified maps system
Responsive Design
Accessibility
Information Architecture
Vacation
Cleaned up a cluttered layout with a more responsive, colour-coded design that helped users connect map pins to weather info faster
The Problem
Vacation was the first project I worked on at TWN. It was a small, focused feature that let users view historical weather data for vacation destinations, things like brief summary about the location, average temperatures and rainfall, based on the time of year. It also served as a seasonal opportunity for travel-related sponsorships to increase ad revenue.
When I joined, one of my first tasks was to improve how this data was displayed on the map. The original design, created by a previous designer, placed weather popups directly over each supported city location on the map. But this caused issues, when multiple cities were close together, the popups often overlapped, making the information hard to read. It also wasn’t responsive and created layout problems on smaller screens.
To fix that, I redesigned the layout so that the popups appeared below the map instead of on top of it. But detaching the data from the map introduced a new challenge: how would users know which popup corresponded to which pin?
I solved that by using colour-coded map markers, then matching those colours to the popups below. I also added a small interaction where clicking a drop pin would scroll to and highlight its corresponding popup, which helped reduce confusion and improve accessibility for users who might struggle with colour association. The result was a more flexible, responsive design that made it easier to understand historical weather at a glance.
Results
Redesigned cluttered, overlapping popups into a clean, responsive layout that worked across screen sizes
Made it easier for users to connect city data to map locations through colour-coded markers and smooth interactions
Turned a small UI fix into a clearer, more accessible feature that the team was genuinely excited about
Data Visualization
Interaction Design
Commute Report
Turned a data-heavy idea into a clear, visual feature that helped daily commuters plan ahead without digging through multiple forecasts
The Problem
The Commute Report module was a new feature designed to help users quickly understand what weather conditions to expect during their daily commute. It was built for people with regular routines like commuting to work or school, who might normally open the app -> check the hourly forecast -> scan through different weather modules -> head out. This feature aimed to save them time by offering a quick summary like “leave earlier” or “take precautions” based on the latest road conditions during their usual travel window.
When I joined the project, the high-level logic for the feature had already been defined, including the “leave earlier/later” text, but I was responsible for:
-
Designing the module layout and visualizing condition data
-
Defining the onboarding flow
-
Deciding how granular the forecast should be (e.g. 15-minute blocks vs. a continuous gradient)
-
Exploring ways to communicate shifting conditions without overwhelming users
We also needed to make onboarding as seamless as possible. The module only worked if users set it up, but asking for too much up front could cause drop-off. So I focused on keeping inputs minimal and familiar, using auto suggest for addresses, OS native date and time pickers, and a simple way to select commute days. The final module used a visual gradient to show shifting road conditions and a clear summary to let users know whether they were good to go or better off leaving a little earlier or later.
Results
Made it faster for users to get commute specific weather updates without digging through multiple weather forecasts
Helped reduce onboarding setup friction and frustration and bounce rate with a flow the team later used as a reference for other modules
Turned a technical, data-heavy idea into a feature that was simple to use and something users could understand at a glance
User Research
Concept Testing
Iterative Design
Concept Testing
Tested contextual modules and layout changes to understand user preferences and help guide future design decisions across platforms
Overview
As part of a broader effort to modernize the app’s weather experience, the product team wanted to test how users responded to contextual modules, features that would surface dynamically based on weather conditions. These included things like Storm Centre (for severe events like snowstorms), Weather Highlights, and changes to the module ordering on the overview screen. The goal was to figure out whether we could improve engagement by showing the most relevant weather content first, without disrupting what users were already familiar with.
My role was to design and prototype different versions of these modules to test them against the baseline/current version, and observe how users reacted to each iteration.
We wanted to know whether people noticed the new module at all, whether they understood its purpose, and how it fit into their overall journey. That meant not just building prototypes, but also actively participating in the research by:
-
Taking notes during interviews
-
Identifying patterns in user behaviour
-
Help synthesize feedback into next steps for the team
We also tested a reshuffling of the app’s overview page layout. On the TWN app, weather content often comes after the news and video, and ads modules, which feel out of step for a weather-focused product. So we ran tests to see how users felt when we moved key weather modules (like hourly forecasts or radar maps) higher up the page.
A big part of my job was to recreate the app experience at that time with high fidelity so nothing stood out as “test-like.” That way, we could observe natural reactions without guiding users toward the new designs. One of the biggest takeaways working with this team was how often users preferred the old design… not because it was great, but because it was familiar. That taught us and other designers to refine our concepts and designs in a way that built on what worked instead of trying to replace it outright.
Results
Confirmed that reordering modules impacted user flow more than expected, pushing the team to rethink how changes are introduced
Helped shift the team’s approach from replacing the old UI to building on it by focusing design updates around familiarity instead of change
The learnings were later used to inform contextual module behaviour in other redesigns, including the new TWN web platform rollout
