Case Study
I´ve led the end-to-end mobile app redesign for Layla, an IoT-powered SaaS platform for property managers, scaling the product from 100 to 10,000+ users.
Mobile App
iOS & Android
B2B SaaS
IoT
Overview
Role
Lead Product Designer
Duration
2 years
Scope
Mobile App
Team
Product, Engineering & Marketing
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
Two years of redesign work translated into measurable outcomes.
+112% DAU
after relaunch
10,000+
new users since relaunch
50% fewer
weekly support tickets
The Problem
When I joined the Layla team, the brief was simple: redesign the mobile app. But "redesign" felt like the wrong place to start if I didn't actually know what was broken.
So before I opened Figma, I went digging: support tickets, emails users had sent directly, App Store and Google Play reviews. Anything that told me what people were actually dealing with.
The same handful of frustrations kept showing up, no matter where I looked.
Nobody was confused about how to use the app.
They were frustrated it never told them what actually mattered:
Which property needed attention right now
How the data fit together, instead of scattered numbers across screens
What the metrics actually meant, since they appeared with zero context
On top of that, basic accessibility issues made the app harder to use than it needed to be, especially for less tech-savvy managers.
That dig through real user pain became the foundation for a proper UX audit of the legacy app, and everything I designed after started from there.
A sample of the feedback that kept repeating across reviews, support tickets and emails.
UX Research
The tickets and reviews told me what was broken, but not why, or what to actually do about it.
I started with a UX audit of the legacy app, walking through every core flow the way a property manager would. Three issues stood out: weak visual hierarchy, metrics with no clear value, and low accessibility.
Annotated audit screens of the legacy mobile app
The audit showed me what the interface was doing wrong. To understand how people actually worked, I ran 5 semi-structured interviews with existing Layla customers: property managers running short- and long-term rentals, recruited through the Operations team. Each session was 45–60 minutes and scenario-based, digging into how they worked day to day, not just what they clicked on.
Annotated audit screens of the legacy mobile app
One quote stuck with me the whole project:
"I need one place that shows me which property needs attention right now."
Property manager, 15–40 short-term rentals
That became the core of the primary persona I built: someone juggling multiple high-turnover properties, expected to catch problems before they escalate, constantly weighing "is this actually urgent?"
Primary user persona
Key Insights
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.
Recurring patterns across user interviews
I translated these patterns into Jobs to be Done, so every design decision could be traced back to something a real user was trying to get done.
JTBD (Jobs to Be Done)
One more finding reshaped a core assumption going in. The original plan was "mobile-first for everything." Research made it clear that wasn't right: managers used their phones to check in on the go, while deeper management tasks happened at a desk. Mobile needed to be about fast monitoring; management belonged on web.
Product decisions before → after research
The Solution
Every screen in the redesign was built around one question from research: what needs my attention right now?
Instead of redesigning screen by screen, I focused on the three places where managers spent most of their time and made each one answer that question faster.
Dashboard: from metrics to incidents
Goal: Help property managers quickly understand what needs attention right now, across all their properties.
The old dashboard led with savings, kWh and CO₂: numbers that looked impressive but didn't help anyone act.
I flipped the hierarchy: incidents come first, grouped by type, with savings moved below as secondary context.
Surfaced incidents first, grouped by type (noise, activity, CO, temperature)
Replaced unused property-type filters with time-based views
Reduced time-to-decision with glanceable summaries
Dashboard screen
Property List: see what's wrong without opening anything
Goal: Help managers scan their portfolio and instantly tell which properties need action and which ones are fine.
The legacy list showed identical cards with the same row of numbers, so managers had to open every property to find a problem.
Online/offline status on every property, with "online first" sorting
Sensor types shown as a consistent, scannable row
Designed to stay readable at 30+ properties, not just 3
Property List Screen
Property Overview: is everything okay here?
Goal: Answer one question instantly: is everything okay in this property right now, and if not, what needs my attention?
Clear separation between real-time data and historical stats (tabs)
Status visibility: online/offline and "updated 1 min ago"
Metrics reframed in user language with visual cues
Progressive disclosure to reduce cognitive load
Property Overview Screen
The Solution
Every screen in the redesign was built around one question from research: what needs my attention right now?
Instead of redesigning screen by screen, I focused on the three places where managers spent most of their time and made each one answer that question faster.
Dashboard: from metrics to incidents
Goal: Help property managers quickly understand what needs attention right now, across all their properties.
The old dashboard led with savings, kWh and CO₂: numbers that looked impressive but didn't help anyone act.
I flipped the hierarchy: incidents come first, grouped by type, with savings moved below as secondary context.
Surfaced incidents first, grouped by type (noise, activity, CO, temperature)
Replaced unused property-type filters with time-based views
Reduced time-to-decision with glanceable summaries
Dashboard screen
XFN Collaboration
Designing for an IoT product meant the interface was only as good as my understanding of the hardware behind it. So early on, I went beyond the product specs and read through the sensor documentation in detail: what each device could measure, how often it reported, and what it could actually control.
Screen
More case studies
The branding and website design for the same company.









