top of page
top

Arbit

The design of a new app that transforms the sneaker resale market space through transparent price verification and community building.

Frame 9_edited.jpg

Project Overview

Role: UX Researcher Lead   Duration:  2 Weeks   Tools: Figma, Miro, Optimal Sort, Asana

Problem

Goals

Results

  • Finding prices of sneakers across various platforms is time-consuming

  • Users want one platform to verify prices, connect to others and organize their collections.

  • The community aspect of sneaker culture is very important to users that sometimes gets lost

  • Design an app that allows users easy access to data on sneakers 

  • Design an app that fosters community and connection between users

  • Provide users with a place to organize their collection of sneakers and products they want to track

  • Ease of use in finding data related to price history, quantity of sales, etc.

  • 100% of users were able to connect to others in the community

  • 100% of users were able to scan shoes they owned and upload to site

  • Access to search at all times

  • Comparison feature incorporated for users to be able to compare sneakers for data

Frame 14.png

The resale sneaker market has grown exponentially in the last decade with an estimated 10 billion dollars in market value. But there is a lack of transparency in prices in the sneaker resale market, a problem that Arbit aims to solve. Arbit is a new platform where users are able to find accurate data on their phones before making an investment in sneakers. Users will have insights into the market with proven, trustworthy data and a place where the community could connect. 

The Process

Discover

Discover

As the Research lead, I conducted the research in 3 phases:
 
1. User Survey
2. User Interviews
3. Competitive and Comparative Analysis

User Survey

We conducted a user survey that accrued 81 participants, mostly between the ages of 18 and 35. The majority of the participants were male.

Here are some main takeaways:

1. 82% of users thought sneakers defined someone’s character and personality. 

 

2. 91.4% of users bought and sold sneakers online. 

3. 80.8% of our participants indicated that they used some combination of websites to verify prices before they sold or bought sneakers. While they used different websites, this highlighted the need for pricing authentication platforms

4. For many, sneakers are much more than a pair of shoes. They are a marker of personality & style and indicate being  part of a group of trend-setters and a unique community. 

Untitled presentation_edited.jpg
Untitled presentation (1)_edited.jpg

In order to gain more in-depth insight into how the users felt about the resale market and their main needs, the team conducted user interviews. 

User Interviews

We interviewed 14 potential users. The data was placed in an affinity map that helped us determine the user's main pain points and needs.

Our main takeaways were:

  • 71% (10/14) of users wished they could have access to more data to reduce pain point in buying/selling sneakers

  • 64% (9/14) of users need to see price data across various platforms before they buy/sell sneakers

  • 50% (7/14) of users expressed frustration with how long it takes them to research the market

  • 57% (8/14) of users felt they belong to a community through sneakers

Arbit Deliverables.png

Competitive & Comparative Analysis

To expand our research, I looked at some competitors who provided similar services.

I studies two competitors, StockX and Sole Collector, who provide information on pricing of sneakers.

Additionally, I conducted a comparative analysis with AirDNA and Moody’s- two platforms that provide data unrelated to sneakers but relevant to the experience. 

In addition of taking note of shared and most common features, I also took note of features that seemed to be working for these platforms, and those which caused frustrations. 

Our takeaway from this study was as follows:

  • Most of these competitors are selective in the amount of data they display to users, which can lead to frustrations. 

  • User account, a search bar, and a primary navigation that allows users to quickly find products were positive features

  • Some platforms use filters to let users control the amount of data/information they want to see

Competitive Analysis Template (updated).jpg

Define

The next phase in the process was to define the problem based off of the research I had conducted:

1. Persona
2. Problem and Solution Statements 

Persona

In order to better understand the users, the team developed two persona types, based off of the research that we had done.

Persona One

 

Alex is a part time fashion photographer and full time sneakerhead. He has found his path in buying and selling sneakers for a profit. Alex loves his business but he wishes there was an easy way to see the price and demand forecast for sneakers before buying or selling a pair. 

Goals:

  • Needs a quick and convenient way to track the sneaker market

  • Honest valuations on sneakers so he can fairly price the shoes he resells

  • A trustworthy resource that will save him time on researching

Pain points:

  • There is no clear answer on what the price of a pair of sneakers should be when reselling them

  • Alex feels that there is not a good breakdown of the sneaker market and where a specific shoe may fall in that market

  • It is difficult to trust the platforms pricing on product because of how many different resources there are.

UX Persona.png

Persona Two

 

Dan is a DJ from Florida who collects sneakers because of the love he has for the culture itself. Since the sneaker market has exploded in the last few years, Dan's collection is now a very important investment that can supplement his dwindling income which took a big hit during Covid. He needs a platform where he not only can check prices but where he can also organize his own collection and keep track of its total value.

Goals:

  • Platform to save his own collection to compare price trends

  • Give and receive advice about new drops, trends, and prices

  • Follow up with the market to determine if it’s worth selling his sneakers or trade them for the ones he wants

Pain points:

  • Hard time finding the right price to buy new additions to his already existing collection

  • Misinformation on new drops & old trends since the sneakers market has too many new comers who have no idea about the culture itself

  • Lack of a platform where his sneaker collection and their market value is well organized and easily accessible

Group 79.png

Based on the research and the needs of our target users, we could could now define the main problems and brainstorm on solutions. 

Problem Statements

1. Alex is a sneaker enthusiast who needs a platform he can trust to track the pricing of sneakers easily because he wants to determine their projected long-term and short value.

2. Dan is a sneaker collector who needs an app that provides him easy access to his collections and the data analytics of each item, because he wants to better manage his collection and investment.

Solution Statement

Design an app that provides reliable data analytics, easy organization of sneaker collection and a space for community members to connect.

Define

Develop

Now that the main problems were defined, the team needed to brainstorm and ideate. But research is an ongoing process, so I ran a card sorting exercise to understand what features most users wished for on the app. Card sorting is a tool in the service of information architecture.
 

Card Sorting

In order to determine the global navigations in the app, I turned to users again for card sorting. 

14 Participants completed a hybrid card sorting exercise in which they were tasked with categorizing the different tasks and features of the app into groups.

  

After synthesizing the data, there emerged some clear preferences for the global navigation and how users preferred to flow throw the app:

  • Profile

  • Notifications

  • Search  

  • Data Analytics

  • Chat/Community option

This table shows categories formed by users, with the blue boxes highlighting the top categories made. 

Arbit-Cardsorting.png

Site Map

Using the data from the card sorting method as well as information architecture best practices and data from the competitive analyses, I created a new site map for the app that provided a user-friendly navigation through the app. 

Arbit site map_edited.jpg

All the data from the research and information architecture provided us with a foundation to begin the design phase. 
 

Sketches

Sketches helped us visualize the app and ideate our different ideas.

Develop

Design & Test

The sketches were then turned into low-fidelity wireframes in Figma. After the first round of usability testing and reiteration, the team created high-fidelity wireframes. Another round of usability testing provided important feedback for the app.  

Wireframes & Usability Testing

Our design went through two rounds of usability testing at different stages.

In the first round, 13 users were asked to accomplish the following tasks:

Task 1. Login and scan a pair of shoes they had recently acquired in order to view its data analytics. Then they were asked to add the shoes to their watchlist.

Task 2. The second task was for users to find a recently dropped pair of shoes and compare its data analytics to a similar item. 

Iteration 1

Arbit Group Presentation. P5_edited.jpg

Positive Takeaways:

In the first usability test, we had some positive results:

  • 92% of users were able to accomplish all tasks

  • All users were able to scan a pair to check data on that certain pair

  • All users were able to view data for their collections

Arbit Group Presentation. P5_edited.jpg

Room for Growth:

However, there was room for improvement on the design.

  • 77% of our users questioned why notifications were under the fire sign instead of their own watchlist

  • Users were not clear on what the comments sections did

  • 92% of our users had difficulty finding the scan button

After consulting with our client who encouraged us to highlight the community aspect of the app per user needs, we added a third task for the user:

Task 3. User joins the community called Sneakersarereal, and follows to participate in a conversation between other users about a new drop. 

Iteration 2

Arbit Group Presentation. P5_edited.jpg

Based on feedback from our testing, the team made adjustments to the design and created high-fidelity wireframes.

 

Adjustments:

  • The user’s Watchlist and Notifications were combined under the fire icon 

  • A community feature was added as a bottom navigation tab and the comments section under the profile was removed

  • The search was utilized more throughout the app to make searches easier for users

  • The scanning icon on the bottom navigation bar was changed to make its function clearer.

Design & Test

Deliver

Below is the prototype for Arbit.

Delivr
Prototype

Next Steps 

Next Steps

There is more to be done for this project. 
Here are some initial thoughts for next steps:

 

  • Test hierarchy of information on Home screen with users 

  • Add text to bottom navigation to clarify icons’ functions

  • Re-work the icon (notifications and camera) to make more clear

  • Adjust the Comparison button, to make more visible to users use

What I learned...

This project was so rewarding to work on and I learnt so much from interacting with my team and the client.The process of working with a client who was in the midst of raising money to start this project was pretty illuminating. There were some misconceptions about UX Research v. Market Research initially, that our team had to clarify for the client, but once those kinks had been ironed out, the work became so fulfilling.

Overall, the experience of working with a client who had a clear vision of what they wished for from the project, helped me understand so much about the stakeholder-designer relationship and was a wonderful growth experience.

Here is some of what I learned:

  • Communication is key. Whether between team members or the design team and stakeholder, being on the same page about goals and objectives and paths forward is very important. 

  • Working in teams can be so rewarding and we learn so much from each other. 

  • Research should be ongoing throughout the project, since at every step we need data from users. 



 

Anchor 1
bottom of page