MyDukan is an app for mobile phone retailers that helps them run their business without the need for maintaining records by hand. The primary goals were to add features into the existing application that would allow the users to maintain a record of their stocks, sales and receive updates about price drops on different models in stock.
Mobile retailers have to maintain a record of their stocks and purchase from different brand distributors. Their profit on selling mobiles is twofold- first is the profit margin on selling to a customer and second is the activation amount which is given to the retailer by the mobile company, after showing the record of successful IMEI activation. So they also have to maintain a record of their sales and activation. Another factor is the drop in the prices of different models of mobiles. The price drop on old model stocks is given by the company to the retailer on showing the record of unsold models and their IMEI number.
To summarise, they need to maintain separate records for their stocks, sales, activations and then price drops. Now imagine maintaining all these records manually every day. It is difficult to manage so many records and at times leads to a loss in business due to missed price drop or activation.
I was part of a two-member design team including me and the lead product designer, collaborating with stakeholder and the team of developers. My responsibilities included conceptualising, designing and preparing assets for developer hand-off. There were few additional responsibilities like testing the developed app for design and functional inconsistencies and providing necessary feedback to the developers.
Field interviews were conducted with a few mobile phone retailers to understand different aspects of their business and the frustrations. The users were currently maintaining all records by hand. Based on the data, the feature set for the app was to be narrowed down.
From the research and understanding of the business, the primary feature set was defined along with a detailed list of sub-features.
- View stocks
- Manage purchase
- Manage sales
- Manage activations
- Manage price drop and claims
The ideas and flows were translated roughly on paper to get a direction in which the product was going to be shaped.
The sketches were then converted to low fidelity wireframes that help us put all the necessary information and flow without any visual design. The wireframes were validated with the design lead and the stakeholder before proceeding to the detail design stage.
Existing brand colours and typography were used for the entire project to maintain sync with the existing brand language.
I tested the low fidelity prototype with 3 users. The users had to perform 3 tasks-
Users were able to perform all tasks but had trouble in identifying the current appointment card as a clickable element with options to edit and cancel the appointment. So I decided to include a visual cue to improve discoverability of appointment options.
I went ahead to make the final screens choosing blue as the primary colour since blue is heavily associated with calmness.
I had prepared a Typeform for conducting a survey of doctors in NITR dispensary, but unfortunately, they did not cooperate. So I decided to move forward with my own observations and assumptions.
I started defining the list of features to bridge the link between patient’s app and doctor.
I started sketching out different ideas roughly to get a quick idea about how the app was going to be shaped. The initial idea was based around a dashboard layout but since doctors only have one primary action in the app so I decided to focus only on the appointment process and went ahead with option 3.
After that, I started making the low fidelity screens in the direction of the finalised concept.
Using the similar visual language of patients’ app I went ahead to make the final screens of the doctors’ app.
MyDukan app was launched in July 2019 on Google Play Store. Since then, the app has over 100,000+ downloads on Play Store with an average rating of 4.6/5. Users had very positive reviews about the app and were demanding additional features for their business management.
While coming up with iterations I made changes to the existing artboard, duplicating only a few of them. I should have preserved all my iterations to understand the thinking behind it while viewing later.
The views of the stakeholder were very important in shaping the app. He had better knowledge of the company's vision and the user base and getting feedback from him was a crucial step before proceeding further.
I learnt a lot while collaborating with the team of developers. We primarily used Zeplin and I learnt the proper way of preparing assets for developer hand-off. Also, I tested the developed modules in the app for design and functional flaws which in turn lead to a greater understanding of the development process and constraints.
