Blush is a make-up simulation app for make-up artists who are looking to optimize their work with their customers.
Blush is a make-up simulation app for make-up artists who are looking to optimize their work with their customers.
As a make-up artist in the past, one of the most challenging things was trying to balance providing a high-quality service that included trial make-up for customers, with the understanding that this service is ultimately not financially profitable (for a variety of reasons) and may also be done more efficiently and profitably. Consequently, I've decided to come up with a reasonable solution to this challenge and difficulty.
When estimating the time for a make-up session, it is important to consider the amount of time spent organizing, meeting, coming and returning, and additional work (such as editing and publishing to social media).
Make-up trials are not financially profitable, which creates a lot of frustration, and honestly, this service can be handled differently and more efficiently, for all parties.
Creating a simulation web app that will improve make-up artists' efficiency with their customers in terms of time optimization.
To better understand the needs and frustrations of the user, I used both interviews and questionnaires to 20 potential users between the ages of 20 and 50.
12 from 20 interviewees publish their works on social media and use several editing software for that purpose
15 from 20 interviewees reported that a trial make-up service is often not financially profitable
16 from 20 Interviewees spend between an hour and a half-two hours getting ready, arriving, and returning from a make-up session
Having completed these steps, I began to formulate the operational concept for the product. Typically, an editor screen has a lot of options, and each option may have several options to choose from.
In my case, I selected the palette canvas screen template, which is often used by graphic and text editors, and characterized by direct manipulation of content.
Based on the user research results, I identified the main features that might help the user (MVP):
After designing the first wireframes and thinking ahead, I have decided to expand the project in terms of features and user flows, as well as adding and refining existing features.
Several features that were added:
So, after creating the wireframes, I created a full flow prototype for user testing.
I conducted the user testing with 4 potential users, using the think aloud method, and providing instructions as needed.
The main things checked were:
For reviewing the main things that needed to be fixed, please come from your desktop
Orientation - good to very good
Effective speed - good to very good
Anxiety level - low
Task completion - 2 of 4 potential users needed help
Main things that needed to be fixed:
All the users marked the edit button in the upper panel instead of clicking the editor button in the side panel and starting the editing process there
To reduce friction, a tutorial pop-up is displayed immediately upon entering the editor screen, explaining that editing operations are performed through the editor button.
2 of the 4 users had difficulty understanding what to mark in the floating menu (containing only icons)
Resizing the font in the side panel menus and highlighting the top titles
Adding a Label under
each icon
Following all the changes that were made and after reviewing the project again in depth, I realized I needed to return to the users' main pain points, re-evaluate, and change the application in such a way that it would provide an accurate answer to the users' needs and focus only on individual features with an emphasis on user processes.
In this project, I have decided to focus only on the editing screen, since most of the action occurs on it.
My main focus was on the following features:
Having identified the main screens and processes, I created the information architecture below.
My inspiration at this point, and after the big change, came from editing platforms which have floating menus, a lighter, simpler design that corresponds with designs that are “younger” and less conservative.
The process of designing and characterizing the application was challenging, but I found it fascinating and ultimately enjoyable to watch the application go through changes and become more accurate as the user's desires and pains became clear.
For the future
Change the app into a management system for the user, the management system will include: