UX Design Process

1. We set a task and formulated a hypothesis.

2. The product designer had a brainstorm with a mini-discovery team that has knowledge of the current implementation of Private Messages: frontend developer, backend developer, designer, QA engineer.

2. The designer formulated a design hypothesis, which we tested on qualitative research.

4. Brought user scripts and made a design.

5. The design passed the quality control of the tech lead and design manager.

6. Submitted the design for development, then for design review and testing.

7. Release.

8. We monitor the indicators and the work of the new functionality.

Result

1. The number of dialogues between users has doubled.

2. The average response time on Android decreased by 2.24 times, on iOS - by 2.2 times.

3. Bonus - slightly increased the share of messages read (+1 percentage point).

Ux design case

 Problem

Preparing for a big update, we switched the Market.kz application to SPA (single page application) technology. There was a problem - the application considers that the user is "online" for a long time after he has logged out. Hence the inconvenience:

1. Push notifications about new messages come when the user is online, although they are not needed at that moment. And vice versa - they don’t come when a person has closed the application, but we believe that he is “online”.

2. The buyer does not write to the seller, mistakenly believing that there will be no answer for a long time. Or vice versa - waiting for a quick reaction from the seller, although he has already left.

Task

Improve user experience and prevent users from missing important notifications further.

Solution

We decided to make internal notifications in SPA and write the logic:

1) "Do not send push notifications to the active dialog, in other cases - send even "online" to the user."

2) When the application is minimized, we change the user's status to "offline", and now he receives regular push notifications.