Loy's portfolio

Challenge

In all the aspects of shopping it has been shown that people prefer to compare prices between products and even specifications to be able to determine what product best suits them in and is best for them putting their finances into consideration.

‍

Process

Empathize - Define problem and goals - Discover needs - Design solutions - Deploy and test

‍

Identifying pain points

Problem

Interactions with people have shown that they want products and goods that fit within their budgets. They want to save money on every item they purchase.

‍

To find the best deal or lowest price, consider comparing prices from different sellers.
To save money on a purchase.
To ensure they are getting the most value for their money.
To compare the different features and options of similar products.
To find a product that fits within their budget.
To make sure they are not overpaying for a product.
To compare prices across different retailers.
To take advantage of sales and discounts.
To find coupons or promotional codes.
To make an informed decision on a purchase.

‍

Understanding the problem

‍

The questions…

‍

What do users need to compare prices? - Discover pain points.
How often do they need to compare prices?
How do they currently compare prices? This is a test to evaluate the cognitive load of the standard interface for comparing prices between online shops. It is assumed that the comparison is made by checking the prices of items across different online stores.
How would a comparison flow and system look to them? - If you had a magic wand, what would it do?
What are the most sought-after features and specifications to compare? - Information architecture of the system: What should be more obvious, assuming they use online stores for this.
Do they find it difficult to compare? - Do we need to innovate a flow to make it more seamless?
What features do they need that they don't know they need? For example, the Lens feature - the ability to scan physical products.
Show them a curated flow and ask them to identify which functions they find valuable. This will help us determine which functions to keep or remove for our prototype.

Important considerations

User control and freedom: How easy is it for a user to perform actions and revert back?
Consistency and standard: Does the platform adhere to heuristic standards and recognizable patterns?
Flexibility and efficiency of use: Can users perform the key actions of this platform quickly and efficiently?

‍

Discovery Phase

Existing platforms

‍

Survey

conversation with a user

‍

💡 Question: Tell me about how you currently compare prices of clothes.

Answer: I just browse through different stores I know online and check If I can find any

💡 Question: What are the reasons you try to compare prices?

Answer: Cos somewhere someplace there is always a lower and better price

💡 Question: Do you use an app to compare prices?

Answer: I use online stores; I have not seen an app that can work pretty well

💡 Question: From your perspective, what is the most important functionality of a Price compare app

Answer: Ability to see different prices of the same product

💡 Question: Do you find the current way you compare prices easy to use?

Answer: Not really. There are times when it takes me time to get the same exact type of product.

💡 Question: What improvements would you like to see

Answer: More compare options for more products

💡 Question: Is there anything missing that you would like to see?

Answer: A place to probably track the best price for a particular product

💡 Question: What do you not like about this?

Answer: Not being able to compare other products asides from clothes

‍

Key Takeaways

Reduce the steps to achieve their goals.
Ensure Accessibility standards are met. likeAAA color Contrast
Functional tips not hidden.
Clear warning labels, to avoid confusion.
Clear feedback on user action
Avoid functions that could be accidentally used.

NICE TO HAVE

Voice search
Assistant voice command
Image search

DON’T

Use ambiguous icons.
Remove important functionalities.

‍

‍

Features Strategizing

‍

Journey Storyboard

‍

Ideation

‍

‍

Fleshing out the flow

‍

‍

Ideated solution

‍

Feature Highlights

‍

Ease of use Features

‍

High fidelity

Low fidelity

MockUp

Interactive prototype

Check interactive prototype here

Reflection and Takeaways

Working on this project made me think outside the box as there are not many simple and user friendly ways for users to compare fashion products, it's easier with gadgets and electronics which have specs and other features but with clothing the challenge is there with describing the product and getting an easy way to cross reference it and bring it up if it is present in the database. Working on this project made me think of ways the solution can be achieved and what technology can aid the process and make it happen.

Checkr