Limehome — App · 2025
Guest Hub
A central hub where guests organise their booking, check in, unlock their door and add services — replacing a scattered mix of emails, links and support chats with one place that always answers “what happens next?”.
Project type
Product design & design system
Role
Lead Digital Product Designer
Platform
Mobile app (iOS & Android)
Year
2025
Key outcomes
1 place
Booking, check-in, access and services unified
SparkUI
Built entirely on the in-house design system
Fewer tickets
Self-service replaces repetitive guest support requests
Cross-team
Shipped with product, engineering and operations
Context
Everything a guest needed lived somewhere else
Limehome is a fully digital hospitality operator — there is no reception desk. That makes the app the front door: if a guest cannot find their access code or understand their check-in status, the only fallback is support.
Before Guest Hub, the essentials were spread across confirmation emails, deep links and separate flows. Guests reread emails to find codes, and operations absorbed the confusion as repetitive tickets.
Opportunity
One hub, ordered by what happens next
- 01Make the current state of the stay — upcoming, check-in ready, in-house, checked out — unmistakable.
- 02Put access, booking details and services one tap from the entry screen.
- 03Turn services into a calm, discoverable layer instead of an upsell interruption.
- 04Build it on reusable components so new markets and services ship without redesign.
Process
From guest journey to a system
- 01Mapped the end-to-end stay with operations and support to locate where guests actually got stuck.
- 02Clustered support tickets to rank the questions the hub had to answer first.
- 03Prototyped the hub as a state machine — each stay phase gets its own primary action.
- 04Validated flows with usability sessions, then hardened components in SparkUI for handoff.
Solution
Key changes introduced
- 01A stay-aware home screen: one primary action per phase, never a wall of equal options.
- 02Access and door unlock promoted to a persistent, always-findable place.
- 03Booking details, invoices and stay extensions grouped under one predictable structure.
- 04Services surfaced contextually — at the moment they are useful, not on arrival.
- 05Explicit states for pending, ready, active and completed instead of silent screens.
Impact
What changed
- 01Guests self-serve the questions that previously became support tickets.
- 02Service discovery moved into the natural flow of the stay rather than a separate tab.
- 03SparkUI components made the hub the reference implementation for other Limehome surfaces.
Reflection
What I took from it
In hospitality, clarity is service. Most guest frustration was not missing features — it was not knowing the state of their own stay.
Designing the hub as phases rather than pages kept the interface small while the product kept growing.
Tools — Figma, FigJam, Jira, Confluence, Hotjar, Maze
View the original Figma deck ↗Next project
Multi-Room Booking Experience
Limehome GmbH · 2024 →