Layla — Mobile App Redesign

Layla — Mobile App Redesign

Redesigned a property monitoring mobile app, increasing daily engagement by 112%

Redesigned a property monitoring mobile app, increasing daily engagement by 112%

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.

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

Mobile App

iOS & Android

iOS & Android

B2B SaaS

B2B SaaS

IoT

IoT

Overview
Impact
The Problem
UX Research
Key Insights
The Solution
Design System
XFN Collaboration
Prioritization
Trade-offs
Edge Cases
Learnings

Overview

Overview

Role

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.

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

Two years of redesign work translated into measurable outcomes.

Two years of redesign work translated into measurable outcomes.

+112+0

DAU

after relaunch

10,000+0+

new users since relaunch

500

% fewer

weekly support tickets

The Problem

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.

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

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.

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.

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?"

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

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.

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.

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.

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.

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: 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: 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: 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

Design System

Design System

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.

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.

Button component library: primary and secondary variants across sizes, icon placements and interaction states

Color system: primitive palettes mapped to semantic tokens for content and feedback states

Type scale: Work Sans hierarchy from H1 to Overline, with decoration variants and synced text styles

Core components: text fields, buttons, selection controls, stepper and toasts with all their states

XFN Collaboration

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.

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.

Prototyping before building


Words and static screens weren't enough to align three teams on how an IoT product should behave. So I built high-fidelity interactive prototypes [in Figma / ProtoPie] that showed exactly how the app would work before a single line of code was written: [how alerts arrive and escalate, how a manager moves from the property list to an incident, what happens when a sensor goes offline].

The prototypes became our shared reference point. Engineering could spot technical risks early, sales could demo the new experience to customers before launch, and we could test real scenarios with users [and iterate on them], all without spending development time on ideas that wouldn't hold up.

Prototyping before building

Words and static screens weren't enough to align three teams on how an IoT product should behave. So I built high-fidelity interactive prototypes [in Figma / ProtoPie] that showed exactly how the app would work before a single line of code was written: [how alerts arrive and escalate, how a manager moves from the property list to an incident, what happens when a sensor goes offline].

The prototypes became our shared reference point. Engineering could spot technical risks early, sales could demo the new experience to customers before launch, and we could test real scenarios with users [and iterate on them], all without spending development time on ideas that wouldn't hold up.

The prototype behind the redesign: every flow connected and clickable, so the team could test it before a line of code was written.

Prioritization

Prioritization

Research left us with a long list of problems, and a small team couldn't fix them all at once. I needed a clear way to decide what went into the first release and what could wait.


I scored every problem against three questions:


  • Does it block the core job? Anything that stopped managers from seeing which property needed attention came first.

  • How often does it come up? Issues that repeated across interviews, tickets and reviews ranked higher than one-off requests.

  • Can we build it now? Some ideas depended on data the sensors couldn't reliably provide yet, so engineering input shaped the order.


What went first


  • Incidents at the top of the dashboard

  • Online/offline status and the latest critical event on every property card

  • Metrics in plain language with context

  • Basic accessibility fixes: contrast, text size, tap targets


What moved to web
Research showed that deeper management tasks happened at a desk, not on the go. Instead of squeezing them into the mobile app, we deliberately moved them to the web platform [e.g. user management, detailed reports, configuration] and kept mobile focused on fast monitoring.

Research left us with a long list of problems, and a small team couldn't fix them all at once. I needed a clear way to decide what went into the first release and what could wait.

I scored every problem against three questions:

  • Does it block the core job? Anything that stopped managers from seeing which property needed attention came first.

  • How often does it come up? Issues that repeated across interviews, tickets and reviews ranked higher than one-off requests.

  • Can we build it now? Some ideas depended on data the sensors couldn't reliably provide yet, so engineering input shaped the order.


What went first

  • Incidents at the top of the dashboard

  • Online/offline status and the latest critical event on every property card

  • Metrics in plain language with context

  • Basic accessibility fixes: contrast, text size, tap targets


What moved to web
Research showed that deeper management tasks happened at a desk, not on the go. Instead of squeezing them into the mobile app, we deliberately moved them to the web platform [e.g. user management, detailed reports, configuration] and kept mobile focused on fast monitoring.

Roadmap brainstorm with product, engineering and sales: aligning priorities before committing to the next phase.

Trade-offs

Trade-offs

Every decision that made the app clearer for one group took something away from another. These were the ones that mattered most.


Urgency over savings
The old dashboard led with energy savings, CO₂ and trees saved: numbers the business was proud of and that supported Layla's eco positioning. Research showed managers didn't open the app for that. I moved incidents to the top and savings below. We gave up some brand storytelling on the main screen in exchange for a dashboard people could actually act on.


Plain language over precision
"Sounds like a loud party" is easier to act on than "78 dB", but it hides detail some users want. Instead of choosing one, I led with the human-readable status and kept the raw value as secondary information, one tap away.


One critical event, not all of them
Showing every event on a property card would have made the list complete, but unreadable at 30+ properties. I chose to show only the latest critical event per card. Managers get a fast overview; the full history lives inside the property.


Mobile for monitoring, web for management
Keeping mobile focused meant some power users couldn't do everything from their phone. We accepted that, because trying to fit every management task into mobile would have brought back the clutter we were removing.


"Last updated" instead of true real-time
Engineering flagged that live, second-by-second data wasn't realistic with the sensor's reporting intervals and performance limits. Rather than pretend otherwise, I designed clear "updated X min ago" timestamps and online/offline states. Less impressive than "live", but honest, and it built the trust managers told us they needed.

Every decision that made the app clearer for one group took something away from another. These were the ones that mattered most.

Urgency over savings
The old dashboard led with energy savings, CO₂ and trees saved: numbers the business was proud of and that supported Layla's eco positioning. Research showed managers didn't open the app for that. I moved incidents to the top and savings below. We gave up some brand storytelling on the main screen in exchange for a dashboard people could actually act on.

Plain language over precision
"Sounds like a loud party" is easier to act on than "78 dB", but it hides detail some users want. Instead of choosing one, I led with the human-readable status and kept the raw value as secondary information, one tap away.

One critical event, not all of them
Showing every event on a property card would have made the list complete, but unreadable at 30+ properties. I chose to show only the latest critical event per card. Managers get a fast overview; the full history lives inside the property.

Mobile for monitoring, web for management
Keeping mobile focused meant some power users couldn't do everything from their phone. We accepted that, because trying to fit every management task into mobile would have brought back the clutter we were removing.

"Last updated" instead of true real-time
Engineering flagged that live, second-by-second data wasn't realistic with the sensor's reporting intervals and performance limits. Rather than pretend otherwise, I designed clear "updated X min ago" timestamps and online/offline states. Less impressive than "live", but honest, and it built the trust managers told us they needed.

Edge Cases

Edge Cases

A dashboard that works when everything is fine is easy. The real test for an IoT product is what happens when things go wrong, and with physical sensors in real properties, something is always going wrong somewhere.


Testing the sensor myself and digging through real logs with engineering helped me map the states the app had to handle, not just the happy path.


When the sensor can't be trusted
Sensors go offline, lose power or sit on weak Wi-Fi. If the app kept showing the last reading as if nothing had happened, managers would make decisions based on stale data. So every property shows its connection status and when data was last updated, and the app flags problems like one sensor going offline, several going offline at once, or Wi-Fi quality dropping below 20%.


When an alert resolves itself
Noise spikes, then drops. Smoke is detected, then cleared. Without a "back to normal" state, managers were left wondering if they still needed to act. I designed a paired resolution state for every critical alert, so the latest event on a card always reflects the current situation, not just the last thing that went wrong.


When severity isn't obvious
Not every alert is equally urgent. Carbon monoxide needs action now; slightly high humidity can wait. Alerts use consistent color, icons and wording by severity, so managers can triage at a glance, from "Act now" to "Please check".


When there's nothing wrong
An empty state matters too. A property with no issues shouldn't feel like missing data, so calm states and positive signals (like the most eco-friendly property) make "all good" feel reassuring rather than blank.

A dashboard that works when everything is fine is easy. The real test for an IoT product is what happens when things go wrong, and with physical sensors in real properties, something is always going wrong somewhere.

Testing the sensor myself and digging through real logs with engineering helped me map the states the app had to handle, not just the happy path.

When the sensor can't be trusted
Sensors go offline, lose power or sit on weak Wi-Fi. If the app kept showing the last reading as if nothing had happened, managers would make decisions based on stale data. So every property shows its connection status and when data was last updated, and the app flags problems like one sensor going offline, several going offline at once, or Wi-Fi quality dropping below 20%.

When an alert resolves itself
Noise spikes, then drops. Smoke is detected, then cleared. Without a "back to normal" state, managers were left wondering if they still needed to act. I designed a paired resolution state for every critical alert, so the latest event on a card always reflects the current situation, not just the last thing that went wrong.

When severity isn't obvious
Not every alert is equally urgent. Carbon monoxide needs action now; slightly high humidity can wait. Alerts use consistent color, icons and wording by severity, so managers can triage at a glance, from "Act now" to "Please check".

When there's nothing wrong
An empty state matters too. A property with no issues shouldn't feel like missing data, so calm states and positive signals (like the most eco-friendly property) make "all good" feel reassuring rather than blank.

Learnings

Learnings

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

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

Key Learnings: What I learned in the this project

based in Barcelona, Spain

local time
Loading...

©2026

let's start creating together!

based in Barcelona, Spain

local time
Loading...

©2026

let's start

creating together!

based in Barcelona, Spain

local time
Loading...

©2026

let's start creating together!

Create a free website with Framer, the website builder loved by startups, designers and agencies.