Resident - Governmental Social Media App
Resident - Governmental Social Media App
Created a civic engagement platform for governments, enabling 30k+ citizen requests and communications
Created a civic engagement platform for governments, enabling 30k+ citizen requests and communications
I led the UX and UI of Resident, a mobile platform that helps Canadian citizens reach their municipal, provincial and federal governments, and gives officials a structured way to respond. The platform went on to handle 30k+ citizen requests.
I led the UX and UI of Resident, a mobile platform that helps Canadian citizens reach their municipal, provincial and federal governments, and gives officials a structured way to respond. The platform went on to handle 30k+ citizen requests.
Mobile App
Mobile App
Civic Tech
Civic Tech
iOS & Android
iOS & Android
Accessibility
Accessibility

Overview
Overview
Role
Product Designer
Duration
1 year
Scope
Mobile App
Team
PM, Developers, Policy Experts & UX Researchers
Resident is a digital platform that helps Canadian citizens connect with their municipal, provincial and federal governments. People can submit requests, ask questions, share suggestions and get official updates, all in one place. On the other side, elected officials and city staff can respond, share news and propose new initiatives.
When I joined, an early MVP already existed. It had laid the groundwork, but people still couldn't do the basics with confidence: submit an issue easily, know whether anyone had seen it, and stay informed about what happened next.
I led the UX and UI from research to final design, turning that early version into a platform built for everyone, from residents of every age and tech level to the officials trying to keep up with their requests.
Layla is a B2B SaaS platform connected to IoT sensors, giving property managers real-time visibility into properties they can't always be physically present in. Its users manage anywhere from 10 to 50+ properties at once — global, distributed, and often under high operational load with mixed technical proficiency.
Over two years, I led UX research from the ground up, built the design system from scratch, and redesigned the mobile app end-to-end for both iOS and Android. Working with an IoT-based product also meant going deep into technical research — I read through extensive sensor documentation to fully understand device capabilities and unlock features that weren't yet being used in the product.
This required close, ongoing communication with both hardware and software engineering teams to translate technical constraints into a mobile experience that actually worked.
Impact
Impact
A platform people actually used to talk to their government.
A platform people actually used to talk to their government.
citizen requests and communications
faster request submission
higher user engagement
The Problem
The Problem
Most people only try to contact their government when something's wrong: a pothole on their street, roadwork nobody explained, a safety issue near their kid's school. And that's exactly when the system let them down.
They didn't know which department to contact. When they did send something, it often disappeared without a reply. And even if someone was working on it, there was no way to know. So people stopped trying, and the feeling that speaking up doesn't change anything only got stronger.
The other side wasn't doing much better. City staff and officials were dealing with a constant stream of inquiries coming in through scattered channels, with no structured way to organize them, respond, or show the public what was being done.
The MVP had started to close that gap, but it didn't go far enough. Submitting a request still felt complicated, status was hard to follow, and there was no real conversation between citizens and the people representing them. Resident needed to become a place where both sides could actually meet.
Most people only try to contact their government when something's wrong: a pothole on their street, roadwork nobody explained, a safety issue near their kid's school. And that's exactly when the system let them down.
They didn't know which department to contact. When they did send something, it often disappeared without a reply. And even if someone was working on it, there was no way to know. So people stopped trying, and the feeling that speaking up doesn't change anything only got stronger.
The other side wasn't doing much better. City staff and officials were dealing with a constant stream of inquiries coming in through scattered channels, with no structured way to organize them, respond, or show the public what was being done.
The MVP had started to close that gap, but it didn't go far enough. Submitting a request still felt complicated, status was hard to follow, and there was no real conversation between citizens and the people representing them. Resident needed to become a place where both sides could actually meet.

Before Resident: citizens stopped speaking up, and the city had no way to show it was listening
Research
Research
The MVP told me what the product did, but not what people actually needed from it. So I talked to both sides: citizens who had tried to reach their government, and local officials who were on the receiving end.
In 1:1 interviews, I asked people to walk me through the last time they reported an issue or answered one. Then I clustered everything I heard into pain points, needs and opportunities. The same frustrations kept coming back:
"I often struggle to find the right government department to address my concerns."
"Tracking my submitted requests is important to me. I want to see real-time updates and know if my issue is being addressed."
"Submitting a request feels complicated. The process should be more intuitive, with clear steps and automatic confirmations."
"A feature that allows me to suggest improvements to my community and see if others support them would make me feel more involved."
The MVP told me what the product did, but not what people actually needed from it. So I talked to both sides: citizens who had tried to reach their government, and local officials who were on the receiving end.
In 1:1 interviews, I asked people to walk me through the last time they reported an issue or answered one. Then I clustered everything I heard into pain points, needs and opportunities. The same frustrations kept coming back:
"I often struggle to find the right government department to address my concerns."
"Tracking my submitted requests is important to me. I want to see real-time updates and know if my issue is being addressed."
"Submitting a request feels complicated. The process should be more intuitive, with clear steps and automatic confirmations."
"A feature that allows me to suggest improvements to my community and see if others support them would make me feel more involved."

Research synthesis: interview quotes clustered into four themes, each mapped to a pain point, need and opportunity
What stood out was that people didn't just want faster answers. They wanted to know they'd been heard. Even a simple confirmation or a status change mattered more to them than I expected.
From these conversations, I built three personas to keep both sides of the product in view:
Emily, a concerned citizen, who reports road damage and safety issues and just wants to know someone saw them
Daniel, a small business owner, who needs clear, timely information on regulations that affect his business
Mark, a city manager, who faces a constant flow of inquiries and needs a structured way to handle them
What stood out was that people didn't just want faster answers. They wanted to know they'd been heard. Even a simple confirmation or a status change mattered more to them than I expected.
From these conversations, I built three personas to keep both sides of the product in view:
Emily, a concerned citizen, who reports road damage and safety issues and just wants to know someone saw them
Daniel, a small business owner, who needs clear, timely information on regulations that affect his business
Mark, a city manager, who faces a constant flow of inquiries and needs a structured way to handle them

Three personas covering both sides of the product: two citizens and the city manager who answers them
UX Priorities
Everything I heard boiled down to four principles. They became the foundation for every flow, UI decision and even the tone of the copy.
Clarity
People shouldn't have to figure out the government's structure before they can ask for help. Finding where and how to submit a request had to be effortless.
Trust
The biggest frustration wasn't slow answers, it was silence. Confirmation messages and visible feedback at every step would show people they'd been heard.
Transparency
Once a request was sent, people wanted to follow it. Real-time updates and clear statuses would replace the guessing.
Involvement
Residents didn't only want to report problems; they wanted a say in how their community changes. Suggestions, votes and even appreciation messages would give them a way to take part.
Everything I heard boiled down to four principles. They became the foundation for every flow, UI decision and even the tone of the copy.
Clarity
People shouldn't have to figure out the government's structure before they can ask for help. Finding where and how to submit a request had to be effortless.
Trust
The biggest frustration wasn't slow answers, it was silence. Confirmation messages and visible feedback at every step would show people they'd been heard.
Transparency
Once a request was sent, people wanted to follow it. Real-time updates and clear statuses would replace the guessing.
Involvement
Residents didn't only want to report problems; they wanted a say in how their community changes. Suggestions, votes and even appreciation messages would give them a way to take part.

Four UX principles that came out of research and shaped every flow, UI decision and line of copy
Information Architecture
Information Architecture
Before designing any screens, I mapped out the main flows and the core structure of the platform. My goal was simple: reduce cognitive load, so every key action, from submitting a request to following up on it, was easy to find without thinking about it.
That led to a navigation built around five places:
Home, a feed of what's happening in your community
Map, where you can see requests around you and their status
Create, a big central button, because submitting something is the most important action in the app
Chat, for direct conversations
More, for everything else
A few patterns kept showing up across every interview:
Users think in urgency, not in data.
Nobody wanted to browse metrics. They wanted to know whether something needed them right now.
Scale changes everything.
What feels manageable with 3 properties breaks completely at 30. The app had to work for the busiest manager, not the average one.
Context beats raw values.
"75 dB" means nothing on its own. Users needed to know if a reading was normal, rising, or a problem.
Confidence matters more than completeness.
Managers didn't need every data point. They needed to trust that sensors were online and the data was live.

Information architecture built around five tabs, with submitting a request as the central action
Starting on paper
Then I picked up a pen. Hand-drawn sketches let me explore ideas fast without getting distracted by visuals. On "My Government", I worked out how people would switch between city, province and country, and where the list of elected officials and the contact options should live. For creating a post, I explored how to make the different types, like a request, suggestion, appreciation or proposal, feel clear without turning the form into a maze.
Starting on paper
Then I picked up a pen. Hand-drawn sketches let me explore ideas fast without getting distracted by visuals. On "My Government", I worked out how people would switch between city, province and country, and where the list of elected officials and the contact options should live. For creating a post, I explored how to make the different types, like a request, suggestion, appreciation or proposal, feel clear without turning the form into a maze.
Testing the structure in low fidelity
Next, I moved to low-fidelity wireframes in Balsamiq for the three screens that mattered most: the feed, the "My Government" overview and the interactive map. Keeping them rough helped me validate hierarchy and flow before committing to any visual decisions.
Testing the structure in low fidelity
Next, I moved to low-fidelity wireframes in Balsamiq for the three screens that mattered most: the feed, the "My Government" overview and the interactive map. Keeping them rough helped me validate hierarchy and flow before committing to any visual decisions.

Hand-drawn sketches and low-fidelity wireframes created in Balsamiq
The Solution
The Solution
I wanted the final product to feel simple, human and trustworthy: easy enough for anyone to use, but serious enough for something connected to government. Each screen came straight out of the four principles.
Home feed - Involvement
The home screen brings the whole community into one place: requests, suggestions, appreciation posts and official updates. Every post is clearly labelled by type and status, so people can tell at a glance what something is and whether it's been addressed. And because appreciation is a post type too, the feed isn't just a list of complaints; people can also say when something went right.
A few patterns kept showing up across every interview:
Users think in urgency, not in data.
Nobody wanted to browse metrics. They wanted to know whether something needed them right now.
Scale changes everything.
What feels manageable with 3 properties breaks completely at 30. The app had to work for the busiest manager, not the average one.
Context beats raw values.
"75 dB" means nothing on its own. Users needed to know if a reading was normal, rising, or a problem.
Confidence matters more than completeness.
Managers didn't need every data point. They needed to trust that sensors were online and the data was live.

Home screen with newsfeed
My Government - Clarity
Not knowing who to contact was one of the most common frustrations. This screen lets people switch between city, province and country, and see who represents them, how active they are and what they've been talking about, all in one place.
My Government - Clarity
Not knowing who to contact was one of the most common frustrations. This screen lets people switch between city, province and country, and see who represents them, how active they are and what they've been talking about, all in one place.

My Government screen
Interactive map - Transparency
The map shows requests where they actually happen. Each one is marked as Open, In Progress or Resolved, so residents can see what's going on in their neighbourhood and follow progress without having to chase anyone for an update.
Interactive map - Transparency
The map shows requests where they actually happen. Each one is marked as Open, In Progress or Resolved, so residents can see what's going on in their neighbourhood and follow progress without having to chase anyone for an update.

Map Screen
Elected official profiles - Trust
Every official has a profile with key details, engagement and direct ways to follow or mention them. Instead of a one-way announcement channel, citizens get a real place to start a conversation, and see that officials are listening.
Elected official profiles - Trust
Every official has a profile with key details, engagement and direct ways to follow or mention them. Instead of a one-way announcement channel, citizens get a real place to start a conversation, and see that officials are listening.

Elected Official Screen
Create proposal - Involvement
Officials can share new initiatives in a structured way: choose the type, the audience and the timeline, and add images or documents. Residents can then vote and respond, which gives officials real input before decisions are made, and gives citizens a reason to stay involved.
Create proposal - Involvement
Officials can share new initiatives in a structured way: choose the type, the audience and the timeline, and add images or documents. Residents can then vote and respond, which gives officials real input before decisions are made, and gives citizens a reason to stay involved.

Create Proposal Screen
Designing for Everyone
When your users are an entire population, you don't get to design for the average person. Resident had to work for a retired resident with poor eyesight, a busy parent with one free hand and someone who rarely uses apps at all.
So accessibility wasn't a final checklist; it shaped decisions from the first sketch, following WCAG 2.1 Level AA wherever possible.
What that looked like in practice
Contrast you can actually read. Text and primary actions meet high contrast ratios, so key buttons, like voting on a proposal, stand out clearly.
Typography that scales. Text stays readable and the layout holds up when people increase their system font size.
Labels that say what they do. Buttons and fields use descriptive text instead of vague words like "OK" or "Submit".
Icons never stand alone. Every icon in the navigation has a text label, so nobody has to guess what it means.
Never color alone. Statuses and progress are shown with both color and text, so they still make sense for people with color blindness.
Room for every finger. Tap targets are large and well spaced, which matters for anyone using their phone on the go.
Consistency over cleverness. Familiar, repeating layouts reduce cognitive load, especially for people who aren't confident with technology.
The mobile app touched almost every team at Layla: product leadership, engineering, hardware and sales, each with different priorities. A big part of my job was getting them into the same conversation.
Learning the hardware first
I hadn't worked on a hardware-dependent product before, and I quickly realised I couldn't design good experiences without understanding how the sensor actually behaved in the real world: its limitations, failure modes and how reliable its data was.
So I went beyond the documentation:
I set up sessions with the hardware and engineering teams
I asked to see real sensor logs, error cases and edge conditions
I tested the sensor myself to feel the setup friction and failure states first-hand
That let me translate technical constraints into UX patterns and clear system feedback. A reading like "78 dB" tells a manager nothing. "Sounds like a loud party" tells them exactly what's happening. The same thinking shaped how I designed onboarding, alerts and troubleshooting flows.

Seven accessibility decisions, shown on a real screen
Learnings
Learnings
Design for both sides of the conversation.
It would have been easy to focus only on citizens. But Resident only works if officials can keep up with what comes in. Designing for Mark, the overwhelmed city manager, mattered just as much as designing for Emily, who wanted to be heard.
Trust is built in small moments.
I went in thinking speed would matter most. Research showed that what people really wanted was to know someone was listening. A confirmation message, a status that changes from Open to In Progress, a reply from an official. None of these are big features, but together they're what makes people come back.
Accessibility is the product, not a feature.
When your audience is everyone, designing for people at the edges makes the experience better for all. Clear labels, readable text and simple layouts didn't just help users with specific needs; they made Resident easier for everyone.
Design can be a tool for civic connection.
This project wasn't just about building an app. It was about giving people a way to take part in their community and see that their voice made a difference, and that's a mindset I bring to every product since.
Understand the system before designing the interface.
Working on an IoT product taught me that the most important design decisions often come from outside Figma: sensor logs, hardware limits, how data actually arrives. Learning the technical side early saved us from designing things that could never work reliably.
Start with what's broken, not with the brief.
"Redesign the app" could have meant a fresh coat of paint. Digging into tickets, reviews and interviews first turned it into a clear problem: people didn't know what needed their attention. Everything else followed from that.
Design is a shared language.
The biggest shifts happened when engineering, sales and product could see the same prototype and talk about the same scenario. Making decisions visible did more for alignment than any argument could.
What I'd do next
Toward the end of my time at Layla, the company started selling sensors directly to consumers on Amazon. That would change the app's biggest challenge: from helping managers prioritise many properties to helping a first-time homeowner set up a single device on their own. Self-serve onboarding and even clearer, plain-language data would be where I'd start