BENYIN🐇

Influencer storefront

Helping creators build simple and inspirational storefront experience

Overview

Timeline

January 2024 - February 2024 (1 month full-time )

My Role

UX designer: Ideation, Information architecture, Navigation design, Rapid Prototype, User flow, Happy Path, Design Collaboration, Scope & Plan

Context

Loudcrowd wants to enhance the influencer storefront by providing functionality that matches the capabilities found in Walmart, LTK, and Amazon programs. The storefront should allow creators curate and organize products into multiple collections. The hope is that once this feature is implemented, the creators can create personalized storefront to attract more customers for the brands they collaborate with.

Problem

It is challenging to do a universal design that serves a template for all brands, since many has their own website style. Besides, Loudcrowd needs to enable easy login, product picking and making the creators interested in associating UGC with products in the collections.

Goal

Brands seek to provide functionality for their ambassador programs that matches the capabilities found in Walmart, LTK, and Amazon programs. So Loudcrowd needs to enhance the ambassador storefront with the hope that it would increase sales conversions for brands. 

Solution&Impact

Version 0 (V0) has been implemented, although most of the design I have done are not included in this release due to time constraints. A demo showcasing how to add products to the ambassador storefront was presented during the end-of-month meeting following multiple rounds of testing.

So, how we got there?🧐

Strategy

Market Research

For the market research, we worked on gathering references for empty state, ambassador-controlled view, and buyer's view.

User Research & insights

Due to time constrain, we only conducted interview with Root Pretty's influencer. We want to have an idea what the influencer expects to experience creating their storefront.


  • Influencer believe that shoppable UGC (User-Generated Content) enhances the shopping experience for their followers. They find that integrating UGC makes the product discovery process more authentic and engaging, leading to a smoother path to purchase.

  • Influencer expressed a need for a simpler way to select products, such as a typeahead search feature or the ability to select products via a URL. This would streamline the product tagging process, saving time and effort.

  • There is a strong desire for UGC to be displayed immediately after the ambassador’s bio. Ambassadors feel this placement would ensure their followers can quickly access relevant content, improving the overall user flow.

  • Influencer want a clear prompt or guidance when landing on the product selection page. They noted that this would help reduce confusion and enable them to get started quickly.

  • When encountering an empty state, influencer wish for more guidance or direction on what to do next. This could involve tutorials, tips, or suggestions for how to proceed, ensuring they feel supported throughout the process.

User Story

We created the user story based on the user research so it can help us to see what influencer wants to achieve as their end goal.

As a influencer, I want to be told what to do 1st, 2nd and 3rd so that I can quickly set up my storefront without missing any key steps



1

As a influencer, I want to be to rearrange the products into categories of buyer interest (ex: specific occasions, recent order/purchase history, specific categories) so that my storefront visitors can get inspired and be more likely to shop some products





2

As a influencer, I want to a simple way to manage my collections, product & UGC so that I can save time maintaining relevance of my storefront to buyers





3

User Flow

With the user stories in mind, we created three user flows, each addressing the steps the user would go through. Throughout this process, we identified several logical issues that hindered our ability to establish a sustainable structure for both the interface and backend database.

Setup flow

Rearrange flow

Manage flow

Scope

Work distribution

My responsibilities are managing and rearranging the flow. While areas that are grayed out are primarily handled by another designer, I help with consolidating and organizing the files.

Star (*) indicates that bulk actions are possible

Structure

Sitemap

This sitemap illustrates the definitions of parent products, parent UGC, child products, and child UGC, along with their interrelationships and possible combinations within a collection. Rules designed to prevent loops and ensure system integrity in backend engineering are highlighted and explained in red.

1

2

3

4

5

5

  1. Product with 1 or more UGC attached is a parent; attached UGC becomes the child

  2. UGC with 1 or more products attached is a parent; attached product becomes the child


  • Only parent can be pinned and shared

  • Deleting parent will delete the child

  • Deleting a child will go through the parent

  1. you can create collections in all; "All" has all the collections; you can filter by UGC or product in "All"

  2. you can add media and products in collections; collection has UGCs & products

  3. Same product can exist in multiple collections (here is Y and Z); Deleting the copy from collection Y will have no impact on the copy in collection Z


  • Empty state: creators see "All" page populated by UGCs already approved by brand through the corresponding ambassador program.

  • Creator can also add new UGC that is not pre-approved to enhance the storefront.

Interface

Since I was only in charge of the rearrange and manage flow, I do not have to build everything from scratch. I was able to take the "All" page sketch from the other designer and work upon a basic layout structure.

Collection list iteration

  • Brainstorming:

    I got some inspirations from Pinterest for how to manage the collection list.

    Manage collection list

    Manage collection list mode

    In "All" page

    Feedback:

    I started with playing the layout of the " Template" button and its display form on the interfaces. Also need to consider what happens when the collection title is longer than the page title.

  • Changes

    In the mid fidelity mocks, I came up with 3 options for the manage collection list mode.

    Option 1

    In "All" page

    Collection list

    Option 2

    Option 3

    Feedback:

    Need to consider the edge case when there are more collection titles the height of the screen can handle. Option 1 has less clicks and prevents human error.

  • Changes

    I considered the edge case and made the page scrollable. Also made sure when the collection title is longer than the length can handle, use … to replace the rest of the title.

    Manage mode

    In "All" page

    Collection list

    Collection remove message

Collection management iteration

  • Brainstorming:

    Since I have to consider for the remove, move and pin action for one card and multiple cards, I decided to create a small menu for the actions.

    Manage mode

    Card selected

    Card removed

    Feedback:

    It's unclear how to proceed in manage mode and confusing why the buttons light up after selecting cards

  • Changes

    I updated the action menu so that there are tips on the top to tell creator what action can be performed.

    Feedback:

    This design is not consistent with conventional design and is not consistent with menu the other designer has created.

    Remove selected

    In "All" page

    Move selected

    Success toast

    Pin selected

  • Changes

    To make the design more consistent, I followed the side up menu action designed by the other designer. However, I proposed to change the icons in the pop-up menu to words, so it is clearly for the creator what to do. I also replaced icons with words to say done or cancel when the card is selected.

    Change collection bio

    In a collection

    Action menu

    Move selected

    Remove selected

Individual card iteration

  • Brainstorming:

    Instead of opening up a side menu with actions, I utilized the back of the card as the action menu.

    Manage product card

    In "All" page

    Manage UGC card

    Feedback:

    Need to show what happens when an action is performed.

  • Changes

    I included the page for what happens when an action is selected.

    Feedback:

    Needs to take some time to think which actions should show up at the back and which actions can combined with the manage mode menu.

    Attach UGC popup

    In "All" page

    Back of card

    Pinned card

    Double confirm

  • Changes

    Pin and remove action can also be handled by the manage mode menu so I removed them from the back menu. In the future, we do not need to show the 3 dots anymore since the creator can simply click onto the individual card which guides them to the detail view that can handle attach UGC and share.

    Future: card detail popup

    Future: remove attached UGC

    In "All" page

    Back of card

Final design - ambassador's view

In the very end, I combined my work with the other designer to create a complete flow. We documented details need for engineers to follow.

Final design - buyer's view

I also worked visitor's view we know what the storefront visitors will see on their end.

Usability Testing

After this mid-fi prototype was done, we showed it to the Root Pretty's influencer again to see how usable this design is by asking the influencer to 1) create a collection 2) add a product. Based on the insight we came up with recommendation for next revision.

Reflections

  • Less space: Mobile design restricts space, making it harder to fit the same amount of content as on desktop.

  • Different user, different experience: We need to set up the entire flow considering different viewing perspectives, such as the ambassador's and the buyers.

  • Collaboration is key: Each of us has a different structure, but we benefit from exchanging valuable advice.

  • Default logic: The most confusing aspect arises when product cards and UGC cards are mixed together. So, what determines how things are shown? (Most recent? Most relevant?)

  • Communication is key: Design updates need to be in sync for both designers to ensure right alignment.

  • Scalability: It is hard to build a foundation information architecture and structure with scalability in mind.

  • Feature prioritization: We removed many features that was presented in the final mockup simply because the project becomes too big for V0. Finding alternative ways ensured the "slimed "version still works logically is a lot of work.

  • Not every issue requires a solution: Some edge cases may be left for users to resolve themselves, especially if the problem isn't severe. Users often surprise us with their creative solutions.

Thanks for reading till the end :D

© 2024 by Benyin  (❁´◡`❁)

Create a free website with Framer, the website builder loved by startups, designers and agencies.