One app for the whole stay, launching November 2026.

A stay involves small, time-sensitive information: when to arrive, how to get in, what is due and when. Tenants end up searching emails and messages for it.

Each question to the support team costs time on both sides, especially around move-in day.

I worked with Moving Doors as an external collaborator. Their main product was already live, and the tenants’ app is a new product.

I worked alongside the product team and designed the app in Figma, covering every state a stay moves through.

A stay is not one moment but several, and what a tenant needs changes with each. So instead of one fixed screen, I designed every state around what the tenant needs right then, and the My Stays screen leads with that.

The day before move-in, it is how to get in, so the screen leads with check-in and access details. During the stay, it is what is due next and the most-used actions, like reporting an issue or requesting an extension, so it surfaces the next payment and those actions.

Showing the right thing first means tenants do not have to search emails and messages for it, which should also cut support questions around move-in day.

1. Pre-move-in
2. 24 hours before
3. Now staying
4. Ending soon
5. Past stays

The same screen has to work for someone who has not moved in yet and for someone halfway through a long stay. The challenge was deciding what to show first in each state.

That made it an information architecture problem: organizing access details, booking details, payments and requests so each state shows the right ones first and keeps the rest one tap away.

A tenant app built around the stay itself, with the home screen changing as the stay moves from moving in soon to now staying to ending soon.

Access details, Wi-Fi, booking details, a payment timeline and requests for issues or extensions are one tap away. Payments show the balance and timeline, with clear labels for paid, due now and upcoming.

Requests cover every request type, such as cleaning and housekeeping, issue reports, booking cancelation and general inquiries. Each one asks for all the details we need up front, to cut the back and forth between tenants and the team.

The app launches in November 2026 as a first version (MVP), so what follows are assumptions, not measured results.

We expect fewer support tickets with questions about the stay, more payments made on time and easier check-ins.

The data we will track to test these assumptions:

• Support tickets about the stay
• Support tickets about check-in
• Whether payments are made on time
• How tenants use the app

There is no baseline yet, so we will compare with how things work today, and improve the app from what the data and the tickets show.