High-fidelity prototypes and Interaction Design for Mersal Beauty App
Our task was to develop prototypes based on client materials with a detailed study of the interaction. Since the app is essentially a test of the hypothesis it was necessary to design a product MVP: to study the basic, most essential scenarios and make them comfortable.
At the input from the client, we received several wireframes that briefly describe the application. This is very convenient when you do not need to describe the interaction with text - wireframes act as technical specifications more clearly.
In the application, ordinary users register for various cosmetic services (haircut, nail painting, etc), and specialists publish their proposals and manage incoming applications. We distinguished three persons - a regular user, a specialist and an administrator.
Onboarding is an important part of any application. The scenario of the first launch is important to work out because it directly affects the conversion.
Many leave only phone and password fields in the registration to reduce registration time and increase conversion. We decided to leave a name field, since the services offered in the application are closely related to communication.
Interaction with the map is one of the most interesting and complex scenarios in applications, so it requires a special approach. Using HTML and JS, we developed an interactive prototype that worked through hypotheses and improved user experience.
We used MapboxGL as a map engine, since it easily repaints maps from the box and has all the necessary methods for interacting with the map and animation. Designing interaction with the map, especially on the phone, is not an easy task due to the huge number of scenarios tied to geolocation: whether it is on or off, whether it is enabled or not, it catches the connection well or not. All these options must be processed, otherwise the user will be dissatisfied and bring less money.
If you distract from the card, then booking services is a classic task in the field of interfaces, which has dozens, or even hundreds of solutions. We broke the booking into three screens - additional services, the choice of a specialist and the choice of time. There are minimal controls on the screen - so far we are only working on MVP.
In services related to cutting, painting of nails and others, there are a lot of optional parameters. Plus, inside the application there are salons in which several specialists can be. Separately, it is worth mentioning the fields for entering time and date. Free time management is a separate task.
We also developed prototypes of web interfaces for CRM. The principle is nothing special, just all the necessary interaction for managing content within the application, a small time manager - that is, only the most necessary for MVP.
Visit our site for more:
