Checking our usage metrics and using the CUPID system.
The objective was to find a feature with an interaction that will get used the most by asking, "Which steps are always required to complete this selling process?" With that in mind, we've spent more effort working on the seller flow, particularly this page.
We experimented with adding more information to the feed, including size, brand, and asking price. Other additions included users adding items to their favorites while browsing, which was previously only possible on the product page. We saw reduced detail page views by surfacing relevant content to the listing page but a stable purchase intent conversion.
Bottom sheets
Component documentation example

Bottom sheets slide up from the bottom of the screen to reveal more content. We needed to use them to introduce new contextually relevant content on a unique surface and to display content equal in value to the primary content.
Link to view all the design system on Invision App
Seller getting paid

Educating users on what's next using visual cues and setting user expectations when an order is placed, such as by using clear and concise language and using visual cues. I aimed to deliver a simple and short copy without focusing much on UI design.
The thumbs up/down feedback helps us to actively discover issues when completing a task with the current interface. Alongside doing first-look testing, this allowed us to save time and effort while providing a more comprehensive look at the overall effort required.

Buyer Journey

These are high-profile and high-risk pages to make adjustments on, as always. We rolled this out as an A/B testing experiment with an extensive control group. Analytics showed us that a significant traffic source toward the product page was from the user's profile page, which was complicated to navigate. We initially decided to make this page more profile-driven, including the user's number of followers, items for sale, and quick navigation to the other things the seller had listed.
The outcome drove more customers to purchase the product page with a stronger intent. As a result, more sellers and customers who viewed these sections were twice as likely to convert than any other DPV source.
Listing feed page to showcase all our pre-loved clothes

We experimented with adding more information to the feed, including size, brand, and asking price. Other additions also included users adding items to their favorites while browsing, which was previously only possible on the product page. We saw reduced detail page views by surfacing relevant content to the listing page but a stable purchase intent conversion.
Listings feed outcome: we saw a reduction in detail page views by surfacing relevant content to the listing page but a stable purchase intent conversion.
*WAU - Weekly Active User
Product page and outcomes

These are high-profile and high-risk pages to make adjustments on, as always. So, we rolled this out as an A/B testing experiment with an extensive control group. Analytics showed us that a significant traffic source toward the product page was from the user's profile page, which was complicated to navigate. So we initially decided to make this page more profile-driven, including the user's number of followers items for sale and quick navigation to the other things the seller had listed.
The outcome drove more customers with a stronger intent to purchase the product page. As a result, the 'More from this seller' and 'Customers who viewed this also viewed' sections were twice as likely to convert than any other DPV source.
The left graph shows replies per Active User and ad Shares per Active User. The new listing page promotes the sharing of ads and exploring through the "more from this user" section, driving better traffic and higher conversion.
The right graph shows the distribution of in-app traffic by Source (iOS) - 'Recommendations' and 'More from this seller are now twice as likely to convert compared to other listing page sources.
