Responsive Web Design

Dashboard and E-Commerce Store for a Web3 Loyalty Rewards Program

The rewards dashboard and the e-commerce storefront, two of the primary pages for the new loyalty rewards program.

The Problem

A Market Downturn Called for Innovation to Stay Competitive

After launching a new product in 2022, Bored Box struggled to sell its luxury-priced NFT gaming items due to a sharp downturn in the NFT market.

What's at Stake

Without Action, Revenue Would Decline

To remain competitive in the market downturn, the team introduced Boredom, a loyalty rewards program designed to diversify product offerings, attract new customers, and retain the existing community by offering products at varied price points.

My Role

I Designed an End-to-End Experience to Support a Loyalty Rewards Program

As the sole designer, I transformed the Boredom concept to reality within just two months. Collaborating closely with the Founder, Head of Product, and development team, I designed user flows and responsive interfaces. My work ensured that users could easily track points, explore rewards, and make purchases while supporting the client’s goals of engagement and retention.

When

2023

2 Months

Client

Bored Box was a curator and seller of NFTs for Web3 games.

Team

  • Founder
  • Head of Product
  • Front-end Developer
  • Back-end Developer
  • Product Designer (myself)

Project Outcome

We Launched the Rewards Program on Time and Boosted the Business

2 Months

From concept to code, we launched the project in a short timeline

5x

Increase in website traffic and sales

And We Received Praise from the Community

My Process

I Started by Mapping the Loyalty Program into User Flows and Updated the Site Structure

Users could earn points by purchasing Bored Box NFTs or creating a boredbox.io user account, which could then be used to buy Web3 game items. I mapped these actions into user flows and integrated them into the existing site map. This step ensured team alignment and provided a clear framework for wireframing and development decisions.

Next, I Focused on the Design of the Dashboard

Our vision of an intuitive experience included designing a central space that would educate users about how to earn and keep track of points, as well as nudge users towards additional purchases. For this nexus of user needs and business goals, I used an iterative approach to find the right balance.

From Big Picture to Fine Details—My Iterative Design Process

I started with wireframes, testing them against the project requirements. After weighing pros and cons, I explored alternatives and refined the design. While much of this work was independent, I regularly checked in with my team for feedback. Once we landed on a strong solution, I fine-tuned the visuals for clarity and usability.

Having Decided on a Table Layout I Explored Visual Styling that would Sit  within the Existing System

With the team in agreement that the table was the best approach. I explored the use of iconography, typography, spacing, and other styling details to visually communicate the connection between ownership of items and earning points.

An annotated close up of details I sought to refine during the visual design exploration phase. Click an image to view the details.

The Final Dashboard was Launched in February 2023

The dashboard was key to the success of the rewards program. In this space users could track their points and access CTAs that would lead to earning more points.

Along with the Dashboard, the E-Commerce Storefront was Another Key Deliverable

The storefront is where customers could discover items that could be purchased for points. The design was also designed for responsive displays.

A community member on X scrolling through the mobile version of the storefront.

A Quick Purchase Feature Streamlined Revenue-Generating Actions

An advantage of blockchain e-commerce is that website visitors connect a wallet, which is readily available to make a purchase. Taking advantage of this, we designed and built a dynamic card that contained all of the necessary actions for purchasing an NFT from the store.

Demonstration from the live site of the dynamic card design. Here users could complete the blockchain equivalent of "Add to Cart" and confirm purchase while remaining on the same screen.

Lessons Learned

Cross-functional Collaboration was Essential for Meeting Our Tight Deadline

Clear alignment was crucial for success on a project with such a tight timeline. Strong leadership from the Product Manager, daily stand-ups, and iterative working sessions are what kept us moving forward.

Some of my greatest learning moments occurred during 1:1 brainstorming with the Front-End Developer. These sessions deepened my understanding of HTML, CSS, and React as we refined visual details together. Experiencing this highly-collaborative project has reinforced my desire to work on similar teams going forward.

If Time Allowed, I Would Have Incorporated Testing into the Process

Throughout the process, I relied on my teammates’ perspectives to evaluate whether the designs effectively conveyed interactivity and the reward program’s rules. In hindsight, incorporating A/B and preference testing would have provided valuable insights from our fanbase—both strengthening their connection to the product and validating our approach. Fortunately, our dashboard design had a meaningful impact on the business and was well received by the community. I believe this success is a testament to the Founder’s deep understanding of the web3 gaming industry and their fanbase.

View the Next Case Study

A Mobile App Feature to Support a Leadership Training Program

From information architecture to high-fidelity design, I ran with a product concept and designed a holistic system that integrates with the existing iOS & Android app.

Read Case Study ->

A New Workflow to Improve Admin and Customer Experiences of Events

Improved productivity by 6% and increased event production capacity–scaling from 6 to 33 events in the first year–by conducting interviews, journey mapping, and designing optimized workflows.

Read Case Study ->