Apartment Laundry Service App

User Research / Prototyping / Visual Design
Laundry room
client
Washio
project type
User Research / Prototyping / Visual Design
project year
2023

Background

In the city life, where time is always running short for many, tasks like laundry often become inconvenient task for apartment dwellers. The existing laundry facilities in many apartment complexes lack streamlined user experiences, leading to frustrations over machine availability, cleanliness, and payment processes.

Discover

Problem

The laundry services are plagued with many inconveniences, and some of them are listed below:  

i. Uncertainty about availability: Residents often face the frustration of arriving at the laundry room only to find all machines in use, resulting in wasted time and disrupted schedules.

ii. Maintenance issues: Residents may encounter issues like broken machines, leading to dissatisfaction and complaints.

iii. Reservation Hassles: Without a reservation system, residents are left without a way to plan their laundry tasks, which can be problematic during weekends.

iv. Payment Inefficiencies: Outdated or complicated payment methods can cause frustration and delays in getting laundry done.

Goal

The goal for this project is to implement a laundry service app taking care of the following factors:

i. Improve Availability Transparency: Implement a system that provides real-time updates on machine availability, allowing users to plan their laundry tasks effectively.

ii. Efficient Reservation System: Integrate a reservation feature that enables users to book specific machines for designated time slots, reducing wait times and ensuring availability.

iii. Maintenance Alerts: Establish a notification system for maintenance schedules and alerts in case of machine malfunctions.

iv. Streamlined Payment Process: Develop a seamless and secure payment gateway for easy loading of credits, ensuring a hassle-free transaction experience.

Business requirements

i. User Authentication: Registration and login functionality for residents to create and access their accounts.

ii. Dashboard: Overview of available machines and their status (available, in use, out of order).Upcoming reservations (if applicable). Notifications and alerts.

iii. Machine Availability: Real-time status updates of all laundry machines. Filter options by machine type (washer, dryer) and availability.

iv. Reservation System (MVP): View with available timeslots for each machine. Ability to select a time slot for a specific machine. Basic reservation management (make, edit, cancel reservations).

v. Payment Integration (MVP): Secure payment gateway for adding credits to the app wallet. Basic transaction history.

vi. Notifications and Alerts (MVP): Push notifications for reservation confirmations and cycle completion. In-app alerts for important updates.

vii. Profile Management: User profile with name, contact information. Change password, update profile picture, edit information.

viii. Support and Help Center (MVP): Contact form for customer support.

Identifying Users & their needs

The target audience primarily consists of apartment residents who rely on shared laundry facilities. These users come from diverse backgrounds, ranging from young professionals and students to families and seniors. Their expectations revolve around efficiency, convenience, and hygiene.

i. Unpredictable Availability: Residents are frustrated when they cannot find available laundry machines when they need them, leading to inconvenient wait times.

ii. Lack of Transparency: They have no real-time visibility into machine availability, or maintenance schedules.

iii. Inefficient Scheduling: Coordinating laundry schedules can be challenging, especially in larger apartment complexes.

Research Plan creation

The goal of this UX research plan is to gain deep insights into the needs, preferences, and pain points of apartment residents when it comes to using communal laundry facilities. This research will inform the design and development of the app to ensure it addresses the specific requirements of the target audience.

1. Key Research Questions

A.  Understanding User Needs and Pain Points:

i. What are the biggest challenges or pain points residents face when using the communal laundry facilities in their apartments?

ii. How frequently do residents use the laundry facilities? What are their typical laundry habits?

B. Current Behavior and Practices:

i. How do residents currently manage their laundry tasks? Are there specific times or days that are preferred for doing laundry?

ii. Do residents tend to wait for machines to become available, or do they plan their laundry tasks ahead of time?

C. Expectations from App:

i. What features or functionalities do residents expect from a laundry services app to enhance their laundry experience?

ii. How important is real-time machine availability information to residents?

D. Reservation Preferences:

i. Would residents prefer the option to reserve specific machines and time slots in advance? Why or why not?

ii. What level of flexibility do residents desire in terms of rescheduling or cancelling reservations?

E. Payment Process and Preferences:

i. How do residents prefer to make payments for laundry services? Are they comfortable with digital payment methods or do they prefer other options?

ii. Are residents open to using a wallet system for laundry payments?

F. Feedback and Reporting Mechanisms:

i. Would residents be willing to provide feedback on their laundry experiences, such as machine cleanliness or functionality?

ii. How would residents prefer to report issues or maintenance needs related to the laundry facilities?

G. Notification Preferences:

i. How do residents prefer to receive notifications about their laundry activities (e.g., push notifications, email alerts)?

ii. What level of customization would residents like in terms of notification settings?

2. Research Methods

A. User Surveys: Conduct online surveys targeting apartment residents to gather quantitative data on their laundry habits, preferences, and pain points.

Based on the survey, following results were concluded –

- All respondents have no idea on machine availability from home and often have to wait for getting their turn.

- 60% respondents prefer doing laundry on weekends but machine availability is a concern.

- All respondents have specified they need to recharge laundry card to use the machine, no other payment option available.

- 70% of respondents are reluctant to raise service request for faulty machines as only option is to inform building admin and there is no communication back if the machine is repaired or not.

Click here to go to user survey link

B. User Interviews:

Conduct semi-structured interviews with a diverse group of apartment residents to delve deeper into their experiences and gather qualitative insights.

Click here to view the questions prepared for the interview

C. SWOT Analysis:

Analyze existing laundry services apps to identify best practices, popular features, and areas for improvement. The competitors analyzed are Coinamatic, Commercial Laundries Inc., Advantage Equipment Inc., Wash App,

Here’s the SWOT analysis report

Persona

Based on the feedback & responses received from the initial research, the following personas were developed to focus on.

Photo of persona for the project

Click here to view persona in Figma

Define

1. Develop the User Stories

Personas hold the lights for developing the user stories. Initial focus is to develop as many user stories possible to identify every possible use case.

Here’s the list of user stories developed from the persona to work on:

Story 1 :

As a User, I want to create an account so that I can access the laundry services app.

Story 2 :

As a User, I want to log in to my account to start using the app.

Story 3 :

As a User, I want to view the available laundry machines and their current status (available, in use, out of order).

Story 4 :

As a User, I want to reserve a specific machine for a selected time slot.

Story 5 :

As a User, I want to receive notifications about my laundry status.

Story 6 :

As a User, I want to make secure payments for laundry services through the app.

Story 7 :

As a User, I want to view my past laundry reservations and transactions.

Story 8 :

As a User, I want to report any issues or maintenance needs related to the laundry machines.

Story 9 :

As a User, I want to customize my notification preferences(e.g., push notifications, email alerts).

Story 10 :

As a User, I want to easily contact customer support for any questions or concerns.

 

2. Prioritize the User Stories

Once all the possible user stories are crafted, the task of prioritization of stories begin. Here, the Pareto principle (80-20 rule) is considered to select the stories keeping in mind that 80% of time users use 20%of features.

Going ahead with this thinking, following user stories are prioritized for building the app.

Story 1 :

As a User, I want to view the available laundry machines and their current status.

Story 2 :

As a User, I want to reserve a specific machine for a selected time slot.

Story 3 :

As a User, I want to receive notifications about my laundry status.

Story 4 :

As a User, I want to make secure payments for laundry services through the app.

Story 5 :

As a User, I want to report any issues or maintenance needs related to the laundry machines.

Story 6 :

As a User, I want to customize my notification preferences(e.g., push notifications, email alerts).

3. Crazy 8s

Crazy 8s helps me to push beyond my first idea, which is often the least innovative, and to generate a wide variety of solutions to the challenge.

Here’s my crazy 8 for the project-

Photo of hand written Crazy 8's for the project

4. User Flows- By Hand

Once Crazy 8s are done, I have created user flow to take care of all the focus areas discovered in the ideation phase. User flows are first done by hand, to generate more possible potential flows. Sketching by hand provides me more flexibility and fluidity to rearrange the flows.

Here’s my sketched user flow for the project –

Photo of hand written user flow for the project

5. User Flows- in Figma

The finalized user flow is been done in Figma.

Here’s my finalized user flow for the project.

Image of user flow designed in Figma

 

Click here to view user flow in Figma

6. Site Maps

The site maps are next created to show the overall hierarchy of the application and also depicts the relation between subsequent pages.

Here’s my site map for the project.

Image of site map designed in Figma

Click here to view the site map in Figma

7. Wireframe

As a design deliverable, I have next developed the wireframe to ensure that features, scope, and product intention are clearly understood by all stakeholders before anyone starts creating visual assets or writing code.

8. Lo-Fi Prototype

With wireframes done, I have now converted them to lo-fi prototypes for testing and stakeholder feedback.

Here’s my lo-fi prototype for the project.

Image of low fidelity prototype designed in Figma

Click here to view the Lo-Fi prototype in Figma

9. User Testing

The lo-fi prototype is being now tested with the interested participants from research phase to collect feedback and check if the concerns and requirements have been addressed or not.

Here’s the feedback that has been received about the lo-fi prototype

  • User should be able to book both washer & dryer in one flow rather than booking separately.

10. Incorporate the Feedback

The feedbacks are being incorporated into wireframes to align the design as per the client requirements.

Develop

1. Create the Mood Board

Mood boards are inspirational and directional, so I make sure to includes anything that will help me establish a foundational look and feel for visual design.

Here’s the mood board for the project -

Image of mood board designed in Figma

Click here to view the mood board in Figma

2. Finalize the Typography

I have selected Roboto due to availability of several font weights and variables. It will help to present the design and content as clearly as possible.

Here’s the view of fonts for display, headings and others

Image of typography designed in Figma

Click to view the typography in Figma

3. Color Palette

I have decided to use dynamic color based on the logo of the app.

Here’s the color palette based on logo for the app –

Image of color palette designed in Figma

Click here to view the color palette in Figma

4. Hi-Fi Prototype

After setting up the typography, color palette and mood board, it’s the time to work on hi-fi prototype

Here’s the hi-fi prototype for the project –

Image of high fidelity prototype designed in Figma

Click here to view the hi-fi prototype in Figma

Deliver

1. Usability Test

The hi-fi prototype is being now tested with the interested participants to collect feedback and check if the concerns and requirements have been addressed or not.

Here’s the feedback that has been received about the hi-fi prototype -

  • The user should be able to modify or cancel the bookings.
  • User should be able to report any payment or wallet issues in the service section.

2. Incorporate Feedback

The feedbacks are being incorporated into hi-fi mock-up to align the design as per the feedback.

Conclusion

What I learnt

The righter questions that I can ask will give a clear path to develop the product.

Once the product developed its also important to have usability tests so that so important user-friendly features which might have been previously missed gets incorporated.

Simplicity is the key, the designs that are simple and easy to use are more intuitive.

Other projects

Have a question about my work? Let's chat!

Connect with me to bring your ideas to life through compelling design and seamless user experiences. Let's collaborate and create something extraordinary together.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.