Better product base

TIMELINE

September 2021 - April 2022

TEAM

Product Designer (My role) Product Owner, Backend + iOS + Android Developers, Scrum Master

TOOLS

Figma, Protopie, Zeplin, Confluence

PlaTFORM

iOS + Android

Zdrowe Zakupy (eng. Healthy Shopping) is a mobile application which rates food and cosmetics products regarding their ingredients, nutrition values or additives. Our core feature is the barcode scanner and thousands of products are scanned daily. We decided to find a better way to always have actual database.

Context

When our users decide to scan product with our barcode scanner, they would like to get an instant information about it - like ingredients, nutrient values, and general scoring. But there are many new products in chain stores launched every week and it's really time-consuming to keep up with it. It would take hours to enter all these products every day by searching them in the stores. To simplify this process, we would like to ask our users to help with collecting all necessary information to score a given product.
Image presenting what users see on the mobile screen and what they would like to see

KEY RESEARCH FINDINGS

🙅 Every fifth scan is a product that we don't have in the database

💬 Most common negative reviews are about incomplete product base

Statistically, every user scans 6 products a day. That means they may see the "no product view" screen everyday.

We collected feedback from Google Play and App Store reviews. It was clear that our top complaint was about the database or adding new products - our users wants more products, but they don't want to add them by the existing feature.

Previous Solution

Our previous solution for adding products was found by interviewed users to be very time-consuming and laborious. About 70% of the application users scan and add products at the stores, so they waste their precious time entering very long compositions.

In addition, we couldn't verify the added ingredient list without physically having the product, so when someone entered the wrong composition, it caused frustration for other users.

Image with description what is wrong with current process of adding new products
↑ Above:  Old version of submitting the product with highlighed issues

1. Too many things to type

2. It takes too much time

3. There are a lot of mistakes or typos

4. Some of the reports are never approved

REVIEWS

We gathered some opinions and grouped them to understand more main reasons why users don't want to use our adding products feature:

👩

👨

👵

👱

"You need more products"

#1 most common answer

“It happens that I have time to submit a new product, but entering the ingredients takes forever. I would rather take a picture of the composition than enter it by hand”

"I used to add new things only when I wanted to know the score. But there were mistakes anyhow, so I stopped doing it."

“I don't add products anyway because they don't go straight to the application."

After collecting all the data, we concluded a problem statement:

Every day chain stores launch new products that we do not have in the database. How can we make the process of adding products more efficient and mistake proof? How our users can get the value as fast as possible?

SOLUTION

During user interviews, users often said that they would love to take a photo of a long ingredient's list than typing all by hand. We decided to try automate the whole flow, but we needed help from our users. As our community is really engaged to contribute to our app, we decided to ask them of taking 3 photos of unknown product - with 1. The product's front, 2. With the ingredient list 3. With nutrition values.

Lo-Fi Representation of mobile flow

3-step photo for identyfying product, composition and nutritional values

Immediate send to the database and connecting with OCR

Getting result product view with generated score and gathered info

↑ Above: Hi-fi Interactions

EASY PROCESS

↑ Above:  Whole process of submitting the product

The process of adding a new product is divided into three main steps, where the user is asked to take photos of the front, ingredients and nutritional values.

After submitting the report, it is sent to the panel where the ✨OCR Magic✨ happens - cropping the background of the primary photo and all the necessary information.

Notification

When all information is successfully processed, the user receives a notification about the added product.

↑ Above:  Push notification

You can go through all the feature by yourself in Figma prototype below.